Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

FWIW, I am in a project like this where we a re given free will to use whatever it takes to deliver quickly and ignore the company internal procedures etc - we're using agile as it should be done (principles not just verbiage) so for example we don't have meetings unless needed etc. Needless to say we've shipped our first product a few months back and now it's v2 and now some of the team is moving on to other areas. Disruption can be good you know....


Probably a case where you don't understand what it is you broke.

Seen this too much to have any other sort of reaction. People come in without fully understanding what the existing solution does. They get overconfident that they can solve it better. They throw out the thing that is fulfilling the needs of many people. Their rewrite breaks a bunch of stuff they don't know about. But they also set the metrics for success so they've judged themselves to be successful.

If the people affected by their breakage ever manage to get back in touch, the guy that broke them is already long gone.




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

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

Search: