4 ms·
An experienced programmer may not be able to write a lot of code faster than an intermediate programmer, but will know to NOT write code or waste time on things
by brabel 3y ago
An experienced programmer may not be able to write a lot of code faster than an intermediate programmer, but will know to NOT write code or waste time on things they know (from experience) are not required, or desirable... and focus on those things that really matter. This is worth so much for a company. Developers in the middle of their careers are dangerous: they can achieve a lot, but they can easily veer off on a tangent and spend months on some interesting challenge instead of on what the business needs.
If every developer moved "up" to management after a few years, only mediocre programmers would be actually writing code (which is partly true). I've become chief engineer recently, but I had already been leading other developers for a while... but I keep writing lots of code, despite frequent interruptions to assist others... I can see how others often go in undesired directions if not guided back to focus on what is important. I am very glad my company has recognized that I can do that but knows me well enough to understand my strong point is coding, not managing. I am sure Apple and many other companies are also aware that a very experienced developer still writing code with others is worth a lot more than in some miserable (for them) management position.
- SOLAR_FIELDS 3y agoOne of my mantras that I picked up as I moved into a more senior level is “the fastest and easiest to maintain code is the code you don’t have to write at all”. Knowing when and what to write is as much a skill as writing the code in the first place. Also, Apple, presumably being a very siloed organization, probably benefits more from tribal knowledge of the elders more than your typical organization.
- wing-_-nuts 3y agoThere's also the pragmatic flip side to this coin. 'Bad' code that does something is infinitely faster than the perfect implementation that was never written.
- Ensorceled 3y ago> I can see how others often go in undesired directions if not guided back to focus on what is important. This is the role of the senior engineer in a nutshell: herding the cats, but from the technical side.
- pradn 3y agoExecs can waste years by investing in the wrong projects, tech leads can waste quarters of time by picking the wrong architecture/ecosystem, junior engineers can waste days by picking the wrong approach to a ticket. And benefit goes the same way.