3 ms·

Disappointed to not see "Developer(s) rebuilding something that works perfectly fine because they want to try HotNewTech and pad their resume"

pragmatic 4y ago
frAgile and Scum have really cut down on this stuff but I’m sure it’s still out there.
hakfoo 4y ago
I really want the phrase "Resume-driven Development" to catch on. Oh, you replaced the entirely server-side system with the UI of Craigslist with a hot mess of React that takes 5Mb of download to deliver 5kb of content? RDD. Built an ML-powered recommendation engine when you only have three products and could put them all in a single grid for the customer to view? RDD.
- another_story 4y ago
  This is something which is quite common in teaching (especially in international schools with higher turnover) and I'd wager other professions as well. I've suffered through three heads of school and another leader who have used schoolwide initiatives to build up data for their masters or PhD thesis. Wasting my time and the students time with so much useless paperwork.
mrkeen 4y ago
It's pretty rare to see software that works perfectly fine.
justin_oaks 4y ago
Good point. It does happen, but perhaps not as often as the other BS reasons. This is because developers are mostly at the bottom of the hierarchy. They don't often get to choose what BS they get to work on. That said, I have seen a company try, mostly unsuccessfully, to switch to a service-oriented architecture when it didn't make any sense to do so. I also saw a greenfield project that the lead developer used to try out some hot new tech. So it wasn't something that already worked fine, but it was resume-driven development or at least chosen because the tech was new and interesting.
Viliam1234 4y ago
Similarly, "Developers rebuilding something that works perfectly fine because producing a new solution looks better than maintaining the existing one on their manager's resume." Rebuilding it using HotNewTech is a win/win solution.

pragmatic 4y ago

frAgile and Scum have really cut down on this stuff but I’m sure it’s still out there.

hakfoo 4y ago

I really want the phrase "Resume-driven Development" to catch on. Oh, you replaced the entirely server-side system with the UI of Craigslist with a hot mess of React that takes 5Mb of download to deliver 5kb of content? RDD. Built an ML-powered recommendation engine when you only have three products and could put them all in a single grid for the customer to view? RDD.

another_story 4y ago
This is something which is quite common in teaching (especially in international schools with higher turnover) and I'd wager other professions as well. I've suffered through three heads of school and another leader who have used schoolwide initiatives to build up data for their masters or PhD thesis. Wasting my time and the students time with so much useless paperwork.

mrkeen 4y ago

It's pretty rare to see software that works perfectly fine.

justin_oaks 4y ago

Good point. It does happen, but perhaps not as often as the other BS reasons. This is because developers are mostly at the bottom of the hierarchy. They don't often get to choose what BS they get to work on. That said, I have seen a company try, mostly unsuccessfully, to switch to a service-oriented architecture when it didn't make any sense to do so. I also saw a greenfield project that the lead developer used to try out some hot new tech. So it wasn't something that already worked fine, but it was resume-driven development or at least chosen because the tech was new and interesting.

Viliam1234 4y ago

Similarly, "Developers rebuilding something that works perfectly fine because producing a new solution looks better than maintaining the existing one on their manager's resume." Rebuilding it using HotNewTech is a win/win solution.