7 ms·
> a job where 95% of the time is spent waiting for an emergency to react to. this describes quite accurately the work of many people maintaining computer syste
by enriquto 8y ago
> a job where 95% of the time is spent waiting for an emergency to react to.
this describes quite accurately the work of many people maintaining computer systems
- craftyguy 8y agoI must be maintaining the wrong systems, because over here 95% of the time is reacting to emergencies (some technical, but most fabricated by management)
- qop 8y agoFirst thing that came to my mind too! I've had two "Please call me, it's broke" calls just this morning!
- WJW 8y agoWhy does your manager know this before you do though?
- rurp 8y agoIt could be the case that nothing is actually broken. I have unfortunately received a number of similar calls on systems that were working exactly as specified. Random nonsense "disasters" can happen a lot in dysfunctional companies.
- sli 8y agoI would never in a million years, as a developer, give my personal phone number to a client. That's probably why. I get the same issue where I work. The client states that "everything is broken," but it often turns out that their own servers are down (or sometimes our API guys made a breaking change and I wasn't informed, but that's not common anymore). I find this stuff out when I get to work in the morning, because they certainly aren't calling me directly.
- lostcolony 8y agoI think the implication is that the system should alert you directly. Though if you are building systems for clients to run, you obviously would want the system alerting them, not you.
- qop 8y agoIt's actually the opposite way around for me, but I fill a senior role that intersects directly with high-value vendors. I'm basically on-call 24/7 and I am in the office whenever I feel like it or when I need to work on code. I log my interactions with my supervisor, he will occasionally check with me to follow up but I can fix 99% of what they call me about on my own. If I need help, it's usually just expert knowledge that I can ask around the office for. But of course other devs have different roles and workflows.
- hnal943 8y agoYou're assuming 1) there's a legitimate technical problem and 2) the person calling is management and not a user
- bognition 8y agoI doubt you're working on the wrong systems, but working for the wrong people.
- some_account 8y agoI had it like that at my last job. It was technical issues every day. The teams were spending at least half their time just troubleshooting. Nobody wanted to rip out the old problematic systems and start over. So I left. You should do the same. Plenty of jobs out there where you can grow and actually build high quality solutions.
- megaman22 8y agoI've spent a couple hours every morning the last eight Tuesdays explaining to a customer that the software that they purchased from us, and installed on their servers, goes down for a few minutes at 1:00 AM because their server team is rebooting those servers to apply updates. Every week, same time, same issue, same cause, same review and root cause analysis demanded. Fixing broken processes in broken companies is 1000 times harder than anything else in software.
- mc32 8y agoMaybe but don’t tell their managers who would then layoff the 95% thinking they’re making the team 100% efficient and then wonder why things went to hell in hand basket.
- HillaryBriss 8y agoa retired police officer once told me that the quantity of officers citywide goes through a repeated cycle from low to high to low again. when the number of officers is too low and there's too much crime, the people demand that the government hire more. so government does that. and crime goes down. then the public notices all these police officers "doing nothing" and complains about wasted government resources. so, naturally, they demand a reduction in the number of officers. and so it goes...
- frandroid 8y agoBecause crime is directly caused by the lack of police officers there to "prevent" it. &eyeroll&
- HillaryBriss 8y agohere's a little supporting evidence, but, I freely admit, it's from a mostly rural country many people consider barbaric: http://www.cbc.ca/archives/entry/1969-montreals-night-of-terror http://www.cbc.ca/archives/entry/1969-montreals-night-of-ter...
- sbov 8y agoThis is a common phenomena, and I'm not sure if there's a general term for it. E.g. people prematurely stop taking antibiotics because they feel better, or people go off their meds because they feel fine, etc.
- maxerickson 8y agoNot finishing the course of antibiotics is the spicy-hot take: https://www.bmj.com/content/358/bmj.j3418 https://www.bmj.com/content/358/bmj.j3418
- toomuchtodo 8y agoI have yet to ever meet a bored sysadmin/DevOps/systems engineer. There is never, ever enough time in the day for those roles.
- maxxxxx 8y agoI have heard the same about anesthesiologists. 99% boring routine and 1% sheer terror.
- freehunter 8y agoThis was me working as an information security analyst. Just waiting for a security incident. Then my manager realized I had a lot of downtime and put me to work doing compliance reports as well, then wondered why when a security incident happened the compliance reports stopped being generated.