3 ms·
Resume driven development. And on the flipside - One of the funniest justifications I have heard for companies using new fangled untried tech is to attract tal
by hawk_ 3y ago
Resume driven development.
And on the flipside - One of the funniest justifications I have heard for companies using new fangled untried tech is to attract talent - no one wants to work on boring tech apparently for the fear of being outdated.
- beabetterdev 3y agoSome call it "Promotion Driven Development" :)
- 6510 3y agoI'm coining Self Driving Development. You read it here first! If you like big words Autonomous Development is also fine.
- Silhouette 3y agoOne of the funniest justifications I have heard for companies using new fangled untried tech is to attract talent - no one wants to work on boring tech apparently for the fear of being outdated. I sometimes worry for the future of our industry because of exactly this. The culture of buzzword driven development has become enshrined in the recruitment process - often from both sides - because of this kind of vicious circle effect. Now anyone - again from either side - who tries to escape it and instead advocates using sensible, robust tech to build useful, good quality products risks becoming a pariah and seriously damaging their career as a candidate or their ability to recruit strong candidates as an employer. Of course this assumes we are judging career progress by level of seniority reached or compensation paid instead of more indirect achievements like producing something that provided real value to those who used it. But if we're being honest most people obviously will.
- deleted 3y ago[deleted]
- vhcr 3y agoThe worst thing is that it works, I've been rejected at interviews because I didn't have micro-service experience.
- greenbeard 3y agoProbably because they need someone to get them out of the mess they have created.
- peteradio 3y agoThen they'd want de-micro-service experience!
- s__s 3y agoI was job hunting about a year ago and got rejected several times for this reason. The worst part? Each one was a small startup just trying to get a new product off the ground. In one interview the engineer interviewing me explained how they didn’t have any paying customers, and then went on to describe an elaborate over-engineered micro-service based architecture he was working on. The real kicker was that instead of asking me about my 20 years building products, or our infrastructure at my last gig that handled millions of customers across the globe, he instead wanted to watch me code some goofy coding quiz he had prepared.
- hhanda788 3y agoThat's because hiring managers and team leads genuinely care about this stuff. Your last job had you working in a giant monstrous horrible Java EE thing from 2005, and you refactored 500k lines and saved the company $10 million? Sorry, we are only looking to hire somebody who is good enough to know they need to always be learning and keeping up to date with modern standards". It's horseshit but at least half of the people in charge of hiring think exactly that way and so I end up leaving the work I'm the most proud of off my resume a lot of the time.