3 ms·
Where do you want to end up in your career? What do you want to be doing with your time? Different stages of a project's lifecycle require very different engi
by nostrademons 10y ago
Where do you want to end up in your career? What do you want to be doing with your time?
Different stages of a project's lifecycle require very different engineering tactics, and micro-optimizing for one has an opportunity cost for the others. It sounds like you've been working at a startup (presumably before product/market fit), where an ability to crank out features quickly is necessary. Working at a fast-grower that's already attained product/market fit requires a different skillset, largely centered around being able to scale quickly and make wise technology choices. Working at a big company requires still other skillsets, mostly around reading and understanding legacy code and learning how to write maintainable, easily-understood code.
Most of the discourse around "being a good engineer" actually comes from consultants, whose business model is to find companies with failing software projects (there are many of these), say "I can do this the right way", and get them to pay out handsomely for this privilege. Most of the blog articles you read hyping new development practices are sales pitches; their goal is to make you feel insecure about your development team's prowess, and so hire someone who clearly knows better or buy a product that will fix everything. It works on a lot of companies, which is why these consultants continue to get business, but unless your goal is to become one of these consultants, you should take them with the appropriately-sized grain of salt.
Personally, I gave up my first startup because I wanted to be a "good engineer" more than I wanted to build that company, and joined Google. (Usually, opportunities for "good engineering" are more common at big established companies like Google or Facebook.) And then after 5 years there, my desires changed, and I wanted to innovate more than to be a good engineer. The type of programs I write now, and the coding style I use, are dramatically different from what I did at Google, because my goals are different. It's worth clarifying what your goal is before you invest time in developing the skillset for it.