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

You must be “that person” who joins a team, creates IMPACT!!!, reaps the review-time award, and fucks off to some other new team to do it all again before any of the difficult maintenance issues arise. I've spent far too much time cleaning up after people like that to ever tolerate it again.


See I thought how nuanced my argument was towards both sides, and calling out worst cases like:

> Not that a noob developer great at selling has never landed 0 to 1 work, crapped out a half working mess and left with a newly padded resume...

Would be enough to smooth over the minor complex that some career maintainers pick up: "I'm doing the cleanup to make their crap piles work and they're the ones getting treated like they make the industry go round?!"

But I guess for some that feeling goes really deep, and at that point you're just chomping at a chance to pattern match... so the fact my career spans from app agencies boringly maintaining top app store listings to safety critical HMI work for AVs wouldn't sway you that I've been on both sides: since I am now working on a startup! :D

There's your side and there's the other side, and no one who doesn't unilaterally deride the other must be against yours. Tough way to live to be honest.


"Build one to throw away" comes to mind.

You'll figure out what you should have built after it's been used in prod for a while. Possibly years.


I have only met one company that was willing to do this in my career and it was a company that had a massive monopoly in the space with little regulation. Most of the time, what gets done stays this way until the project gets abandoned completely, it's a luxury that the vasty majority of companies will ever have.


I've been at several places that did it. Usually it coincided with a move to the cloud or swapping out the underlying database.




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

Search: