News for hackers. Stuff that matters.
Re:Ask HN: Have you ever worked on a product that was killed... by TheCoreh on Tuesday January 17, 2017 @12:54PM (#13419541)
If I had to guess, I'd say it's probably an issue with the build/deploy system. Perhaps someone deployed a broken build, then tried to revert/rollback, and realized that the previous version didn't build "cleanly" anymore.

This could happen if you have a lot of dependencies, switched compiler versions but left the binaries "in place" and deployed changes incrementally.

Re:Ask HN: Have you ever worked on a product that was killed... by RangerScience on Tuesday January 17, 2017 @01:06PM (#13419656)
Yet another reason I swear by Heroku - you can rollback to the actual prior release, not rollback the code and try to rebuild.
Re:Ask HN: Have you ever worked on a product that was killed... by ardivekar on Tuesday January 17, 2017 @01:28PM (#13419818)
Doesn't AWS do this too?
Re:Ask HN: Have you ever worked on a product that was killed... by RangerScience on Tuesday January 17, 2017 @01:50PM (#13420001)
Which service? EC2 doesn't - at least not inherently, there might be a way to snapshot the machine's state; I'm not sure.
Re:Ask HN: Have you ever worked on a product that was killed... by luhn on Tuesday January 17, 2017 @01:36PM (#13419885)
Depends on which of their 150 services you're talking about. You can't do it on CodeDeploy.