4 ms·
I also disagree, coding is the easy part. When you are junior not everyone requires from you to be know-it-all person nor providing super-good quality code, esp
by piotrkubisa 8y ago
I also disagree, coding is the easy part. When you are junior not everyone requires from you to be know-it-all person nor providing super-good quality code, especially in your first months of journey in the company codebase. However, almost anyone wants to notice a "fresh air" and a person who shares his/her commitment in various form starting from the day one.
Edit: Hey, it is easy to implement code having bugs (shortly: implement bugs) and do many fixes further. It is hard to understand the problem and write code once, which won't need any bugfix. Think about the Apollo-11 code [0] - one tiny bug and astronauts might be dead.
[0]: https://github.com/chrislgarry/Apollo-11 https://github.com/chrislgarry/Apollo-11
- yakshaving_jgt 8y agoDo you think they hired juniors to work on the Apollo 11 code?
- piotrkubisa 8y agoNo, definitely not. I took that example to provide you a real life example of software which cannot be "fixed in production" what is very known type of fixing code these days. If you do understand the problem you really can bring that quality of code which does not need any bugfix during it's run-time. As I written in second sentence: almost nobody wants from you providing that quality of code starting at day one.