yeah, I’m a generalists. I can code, but generally don’t, I can administer users, hardware, security, audit, interpret logs, run share point farms… that sort of stuff - to my relatives “I fix computers” and they always call me when their printer doesn’t work.
- Rewriting perfectly functional code in the hip-and-trendy language of the moment.
- Breaking monolithic code into microservices so that the maintenance overhead moves from the core code itself to the ipc mechanism, while introducing ever-increasing opportunities to exercise your debug skills there.
- Smiling weakly at greybeards volunteering that 'You could easily do all of this in Pascal'.
- Reading published APIs and then spending ages figuring how they *actually* work.
...is writing a function that sends an email based on a conditional which (because you're tired) evaluates to while(1) {send email();} Testing said function, and realising within about half a second what you've done. Killing the test run and deleting the odd 5 or 6 thousand emails that have just landed in your test inbox...
It’s also “staring endlessly at the screen for hours and hours on end trying and failing to fix that one bug”. The longer it takes, the more inane and obvious (in hindsight) the solution is.
Blaming the person who wrote this code and realizing it was me, happens once a month at least 😆
Which launches the journey of "why on Earth did I do this like X when I should have just done Y?", which ends several hours later when I re-discover the far upstream disaster that made doing Y impossible which is why I had to duct tape solution X together in the first place...
Struggling desperately to understand and fix your client code when the server you don't control makes an arbitrary undocumented change to the API with no warning.
Neil E. Hodges
in reply to nixCraft 🐧 • •Pedro Fonseca
in reply to nixCraft 🐧 • • •Christer
in reply to nixCraft 🐧 • • •Charlie
in reply to nixCraft 🐧 • • •Linker3000
in reply to nixCraft 🐧 • • •- Rewriting perfectly functional code in the hip-and-trendy language of the moment.
- Breaking monolithic code into microservices so that the maintenance overhead moves from the core code itself to the ipc mechanism, while introducing ever-increasing opportunities to exercise your debug skills there.
- Smiling weakly at greybeards volunteering that 'You could easily do all of this in Pascal'.
- Reading published APIs and then spending ages figuring how they *actually* work.
MaybeMyMonkeys
in reply to nixCraft 🐧 • • •Liz
in reply to nixCraft 🐧 • • •Testing said function, and realising within about half a second what you've done.
Killing the test run and deleting the odd 5 or 6 thousand emails that have just landed in your test inbox...
Same84
in reply to nixCraft 🐧 • • •Q. Edwards
in reply to nixCraft 🐧 • • •enoch_exe_inc
in reply to nixCraft 🐧 • • •🇺🇸 🇺🇦 🇮🇱 🐧 🥦
in reply to nixCraft 🐧 • • •I've seriously played with the idea of having my headstone say
"Works on my machine".
AndThisIsMrsPeacock 🏳🌈
in reply to nixCraft 🐧 • • •Blaming the person who wrote this code and realizing it was me, happens once a month at least 😆
Which launches the journey of "why on Earth did I do this like X when I should have just done Y?", which ends several hours later when I re-discover the far upstream disaster that made doing Y impossible which is why I had to duct tape solution X together in the first place...
#IT #Dev #SysAdmin #DatacenterLife
Veviser
in reply to nixCraft 🐧 • • •lemgandi
in reply to nixCraft 🐧 • • •