3 ms·
The whole piece has a slightly annoying flippant tone to it. We were drunk! Computers just.. do this stuff sometimes! Better to sound contrite and boring in suc
by cranekam 6y ago
The whole piece has a slightly annoying flippant tone to it. We were drunk! Computers just.. do this stuff sometimes! Better to sound contrite and boring in such a situation IMO.
Also I agree with other comments: doing some work after a glass or two should be fine because you should have other defences in place. “Not being drunk” shouldn’t be the only protection you have against disaster.
- danjac 6y agoThe Exxon Valdez comes to mind - the company blamed the drunk captain, but this was just part of huge systemic failures and negligence.
- Aeolun 6y agoIf your captain feels the need to be drunk, you’ve probably made a few mistakes before it got to that point.
- caspii 6y agoYeah, I agree I'm being slightly flippant. But it's just a side-project and I will continue late night coding with a glass of wine. I find it hugely enjoyable. I would have a different mind-set if I was writing software for power stations as a professional.
- alistairSH 6y agoBut it's just a side-project and I will continue late night coding with a glass of wine. Normally, this would be fine. But, it appears the site has paying members. Presumably, it's not "just a side-project" to them. You owe them better than tinkering with prod while tipsy.
- hnlmorg 6y agoI don't think that's fair. We've all had occasions from time to time when we've had a drink at lunch time or even had to do emergency work in the evening after having a drink. The bigger issue is the lack of guardrails to protect against accidental damage. This is also a common trait for hobby projects (after all, it's more fun to hack stuff together) but hopefully the maintainer will use this experience as a sobering reminder (pun intended) to put some guardrails in place now.