5 ms·
My impression is that it's simply harder to get promoted as an engineer in the industry by using boring, sustainable, unexciting solutions that have been used b
by 8f2ab37a-ed6c 3y ago
My impression is that it's simply harder to get promoted as an engineer in the industry by using boring, sustainable, unexciting solutions that have been used by everybody else and their dog. How do you even stand out that way? Looks bad on the resume, like you didn't even try. Great for the business, but maybe terrible for one's career?
You could turn that one Rails app into a complex microservices architecture and do a conference talk about it, and get a promotion. Then you can undo the microservices architecture, write a blog post about returning to the majestic monolith, and do another conference talk about it, maybe get another promotion. Abstract, de-abstract, bundle, unbundle, rinse and repeat.
It feels like a tragic situation that's nobody's fault, just the reality of human psychology being wired to reward the wrong things.
- ankitrgadiya 3y agoI absolutely agree with this. I sometimes use the phrase optimising for the resume.
- 000ooo000 3y agoI like to think I coined 'Resume Driven Development' but chances are I'm dev #3747 to say that phrase
- stuxnet79 3y ago> optimising for the resume. Otherwise known as RDD (Resume Driven Development) - https://rdd.io https://rdd.io We value: - Specific technologies over working solutions - Hiring buzzwords over proven track records - Creative job titles over technical experience - Reacting to trends over more pragmatic options
- deleted 3y ago[deleted]
- threeseed 3y agoMicroservices is 20 years old. The only thing boring are the people on HN who are still having this played out monolith versus micro-service argument. Whereas actual developers in the real world have moved on and realised that both are useful in different situations.
- block_dagger 3y agoProgress!