3 ms·
Just as there are people who'd leave if the stack is "boring" there are people who'd leave if the tech stack is insane. Personally I wouldn't want to work in a
by weatherlite 5y ago
Just as there are people who'd leave if the stack is "boring" there are people who'd leave if the tech stack is insane. Personally I wouldn't want to work in a team that prioritizes resume driven development. It's usually teams that care very little about the company or product, their only motivation is tinkering with shiny tech. That's not for me.
- AA-BA-94-2A-56 5y agoMeans to an end. I'd work in a team that prioritises resume-driven development for about a year, to brush myself up on all the new stuff. I think it'd be foolish not to, honestly. It comes down to whether you see the software you write or yourself as the important product of writing software. Paradoxically, I see myself as the most important product. Usually my work is a tradeoff between being productive and teaching myself. If I'm being too productive, I back off and experiment more and teach myself concepts.
- weatherlite 5y ago> being productive and teaching myself You can learn Kafka, Map Reduce, Elixir, DynamoDB and shiny new JS framework X like Meteor or whatever, or you can just go deeper on the fundamentals and the traditional tech you already know (learning SQL to a deeper level, becoming really good in Java/.NET/PHP/vanilla JS etc etc). I think the job market has room for both; and to me the second path is more enjoyable and sustainable but to each his own.