I've been programming for almost three decades now and have learned it and done it solo.
But recently I started working as a software engineer and others in the team have pointed out that there are a lot of things I am apparently doing wrong. Which surprised me because so far my programs have always worked and worked efficiently. I was surprised to learn that a program working does not constitute a good program, and that it matters how you make it work, not just that it works.
So I learned about principles and design patterns because that's what colleagues pointed me towards. I then thought about what more can I learn to actually be a top software engineer.
Is there somewhere I can find a list of everything there is to learn to become a top software engineer?
To be honest my goal is to program as perfectly as humanly possible so as to avoid criticism during pull requests. If the answer to that question is that it cannot be done then it would prove my suspicions about code reviews being subjective. In which case why bother with them at all? Which in that case goes back to the idea that the program working effeciently is what ultimately matters.
submitted by /u/sentientlob0029
[link] [comments]
from Software Development – methodologies, techniques, and tools. Covering Agile, RUP, Waterfall + more! https://ift.tt/S9X0J2m