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

At the very least have a two deploys - actually removing the old code that relies on it and then repurposing it. Giant foot gun to do it all in one especially without any automated deploys.


Good point. Actually I think I'll treat this as a best practice in general when there's a transition


That assumes that you have a stable, reliable, quick process to roll out updates. Sounds like they didn't, so maybe they worked on the "oh better add this feature, it's our only chance this month" pattern.




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

Search: