Hacker News new | past | comments | ask | show | jobs | submit login

I think the point wasn't against upgrading or refactoring to something better, it was about the youthful inclination to do that for its own sake.

Us older heads know how often it goes wrong, and know that without a tangible user benefit or commercially positive outcome... It's just busy work.




What's fascinating, and probably points to how young&naive IT org management also tends to be is ... how many let themselves be sold on these solutions.

Oh you are going to rewrite established solution X in Y in 2 years with 5 devs, and it's going to solve all of the problems we have in X, awesome!

Ignoring that solution Y is so new that the guy proposing it has never actually delivered an enterprise solution in it. And since they just got hired, they have no idea what the user facing problems X is actually exhibiting. Often the problems with X are organizational, managerial, and prioritizing. Switching tech doesn't magically change the decision makers.

Invariably hiring a guy who has a string of 18-24 month jobs on his resume, which, uncannily, is the typical runway of a Greenfield re-write project before heads roll.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: