My skill as a programmer is measured as the sum of these abilities. While I may specialize on specific projects, I always contribute to the entire spectrum of programming activities. I need to keep up with this fast-moving field. Remaining static would relegate me to becoming a relic of the past.
That is not the hallmark of a good programmer.
A good programmer makes good programs, and don't follow hypes unless these hypes actually solve problems instead of causing them. Good programmers will actually avoid learning some hype stuff just to prevent pollution and brainwashing of that hype.
Good programmers will also avoid people skills. People skills means that they will turn you into something you don't want, like a coach, a manager or even worse a SCRUM coach. Having people skills means that in a year or so you have lost all your programming skills because your were more in meetings than actually developing code.
Good programmers work more efficient what they work alone but can pair when needed for short times like hours.Work alone, less communication, less discussions, less emails, less meetings and 100% pure productivity.
Good programmers don't need to code review each others code. That is pure waste of productivity. Good programmers trust other good programmers to do their job and they will do theirs. Only when an issue appears will they dig into the other code to see where it goes wrong.
I need to keep up with this fast-moving field.
It is not a fast moving field. It is fast but not that fast. It only appears to move fast because failing programmers jump to the next programming hype to hide their failure yet again. Last methodology was bad but we have this new methodology that this time will guarantee success (NOT).
1 comment
0 u/roznak 07 Jul 2017 19:37
That is not the hallmark of a good programmer.
A good programmer makes good programs, and don't follow hypes unless these hypes actually solve problems instead of causing them. Good programmers will actually avoid learning some hype stuff just to prevent pollution and brainwashing of that hype.
Good programmers will also avoid people skills. People skills means that they will turn you into something you don't want, like a coach, a manager or even worse a SCRUM coach. Having people skills means that in a year or so you have lost all your programming skills because your were more in meetings than actually developing code.
Good programmers work more efficient what they work alone but can pair when needed for short times like hours.Work alone, less communication, less discussions, less emails, less meetings and 100% pure productivity.
Good programmers don't need to code review each others code. That is pure waste of productivity. Good programmers trust other good programmers to do their job and they will do theirs. Only when an issue appears will they dig into the other code to see where it goes wrong.
It is not a fast moving field. It is fast but not that fast. It only appears to move fast because failing programmers jump to the next programming hype to hide their failure yet again. Last methodology was bad but we have this new methodology that this time will guarantee success (NOT).