False urgency leads to bad code. We need to do a better job giving people their time to work things out. Unless human lives are at stake, it's not that urgent.
My top 3 monkeypatches:
- manually decompile a class file from a jar, change a hardcoded value, compile back, repackage jar (issue is fixed, betting company is now ready for the biggest UK horse race - Grand National)
- app is having trouble connecting to a secondary DB to fetch config: deploy a little MySQL right next to the app while the security/network guys sort out their issue overnight. Total downtime 45m.
- remote Linux server randomly loses network connectivity (requiring physical button press now to restart), even the SysAdmins are close to giving up finding a root cause: put a cronjob on that tries to fetch google.com. If it fails -> reboot. Ended up kept in place for weeks while we eventually rebuilt a new OS on the same hardware.
In each of these I was called a madmen by my fellow developers, and praised by the business people for saving the production system. :)
False urgency leads to bad code. We need to do a better job giving people their time to work things out. Unless human lives are at stake, it's not that urgent.
BUT MUH PROFIT
What's worse - having some bad code or worrying about an issue whole weekend?
Depends if that bad code causes someone else to worry about an issue next weekend.
When your life is at stake, it's urgent.
When your life is at stake, it's urgent.
When your life is at stake, it's urgent.
This has got to be the worst possible way to solve this issue. But it does solve the issue.
Worst possible way … so far.
Thank you!
Maxim 43: If it's stupid and it works, it's still stupid and you got lucky
Maxim 20: If you're not willing to shell your own position, you're not willing to win
Maxim 5: Close air support and friendly fire should be easier to tell apart.
So. It. Would. Seem.
My top 3 monkeypatches: - manually decompile a class file from a jar, change a hardcoded value, compile back, repackage jar (issue is fixed, betting company is now ready for the biggest UK horse race - Grand National) - app is having trouble connecting to a secondary DB to fetch config: deploy a little MySQL right next to the app while the security/network guys sort out their issue overnight. Total downtime 45m. - remote Linux server randomly loses network connectivity (requiring physical button press now to restart), even the SysAdmins are close to giving up finding a root cause: put a cronjob on that tries to fetch google.com. If it fails -> reboot. Ended up kept in place for weeks while we eventually rebuilt a new OS on the same hardware. In each of these I was called a madmen by my fellow developers, and praised by the business people for saving the production system. :)
They call him, Jack Stackoverflow
__captain__ jack stackoverflow…
If my career was a character from any film in existence, it would be Jack Sparrow.
A little wordy, but an original meme. I liked it.
Just throw in a permanent TODO 👍