4 ms·
Then again, this broke a package that, by its very nature, isn't running in production. And the problem was solved within three hours. So I'm not sure how much
by IAmEveryone 7y ago
Then again, this broke a package that, by its very nature, isn't running in production. And the problem was solved within three hours.
So I'm not sure how much everything-used-to-be-great-nostalgia is justified here.
- throwanem 7y agoOnly as much as it ever is. That's why I'm making fun of it.
- wutwutwutwut 6y agoMy development environment is my production environment.
- cerved 6y agoF
- wutwutwutwut 6y agoI think you missed my point so let me clarify: If your job is to develop software, then your computer is your production environment. It's where you run your production - your development. This is hopefully separate from where your customers runs development.
- papito 6y agoSomeone rolls out code where a serious bug fell through QA cracks, and appears to be breaking a mission-critical path. Your biggest client is on the phone screaming FIX IT NOW. Three hours is an eternity.
- jiofih 6y agoYou roll back one version. Problem is fixed in thirty seconds.
- erulabs 6y agoScreaming "FIX IT NOW" because bootstrapping a new React app isn't working? Who, what, when, where?!
- rad_gruchalski 6y agoLet’s add: appears to be breaking mission critical path that also slipped through cracks in QA. Mistakes happen, run CI/CD before getting to the mission critical path.