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

Part of the problem is when you are in that position it’s also easy to move to other interesting projects internally.

Then the real choice is between doing boring maintenance or useful new things at same pay.




Not everyone wants to chase the new shiny. There are many folks out there who enjoy the challenge of working in a legacy database. Blue sky folks see a rats nest of wires, maintenance engineers see cable porn in potentia.


Maintenance doesn’t need to be boring, and I also don’t see how you wouldn’t add interesting new features and improvements to existing products.

The basic issue, it seems, is that the higher-ups simply don’t care about the products themselves, other than for them to serve as a profit center.


Those projects have real difficulties to retain enough developers even to keep lights on. And even higher-ups want, they can’t force allocate developers (in Google’s current power structure) other than providing some incentives including promotion.

The end result is a doom loop that if the team can’t retain enough staffing, developers will be overwhelmed by the boring maintenance work, which leads to more team transfers. They do use contractors to mitigate the issue but IMO it doesn’t work in every case.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

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

Search: