I have a mention in forward with a note being “the only documention left was a series of desperate sounding emails that the documentation was still on the now quarenteened work computers and something about a README”
THIS HAS HAPPENED TWICE TO ME, like I appreciate my bosses and PMs being chill and not wanting to overwork me on my way out but seriously guys I needed to hand this off to someone and put it somewhere. shrug
I asked people to take handover for a full month before I left and nobody cared. On my last day they kept asking if they could call me with questions. I said only if they had their credit cards ready because I wasn’t going to work for free.
can AI replace the job of a real programmer, or a team of software engineers? Probably not for a long time.
can manager abuse the fantasy that they could get rid of those pesky engineers that dare telling them something is impossible? Yes totally. If they believe adding an AI tool to a team justifies a 200% increase in productivity. Some managers will fire people against all metrics and evidence. Calling that move a success. Same occurred when they try to outsource code to cheaper teams.
The one thing scrum has succeeded in is creating an industry of people that get paid to do little work, which is fine as long as they don’t take themselves seriously enough to get in the way. Bullshit jobs are a needed feature of a well run economy.
The whole one size fits all approach to projects is such a waste of time. You spend just as much maintaining it as you do actual work. Hive and those apps can kiss my derriere.
this happens with so many scripts I’ve tried to debug with strace because strace requires to run as root or sudo which elevates the niceness of process which prevents certain errors from occuring when the script is run with root permissions and so it runs flawlessly without bugs and you sit wondering wtf
Heisenbug. Nasty buggers, especially in my domain: Embedded Engineering. When you are in the debugger, the whole processor is stopped, missing tons of data coming in, missing interrupts, getting network timeouts, etc. More often than not, resuming makes no sense, and you have to get straight to reboot.
Yeah but you get a nice ramp-up period where you’re allowed to be bewildered and unproductive. In that time, you can probably pick out two or three grandiose changes (ideally with hot new technologies) to throw on the pile before that period ends, and use them as resume padding and interview stories for the next job.
Unlike the old developers, you aren’t complicit in the mess until a few years go by.
I’m on a project where we original had three devs, but two of them did exactly what is depicted in this image, so now there’s only me. There’s a proper god damn mountain of tech debt that keeps growing. At this point it’d take me probably a solid couple of months to sort it out, but of course the customer doesn’t want to pay for anything, because “what’s the problem, it’s still running”. All I can really do is glance at it every now and then, like that gif with richard ayoade and the fire from IT crowd. It’s a pretty big and widely used system too, so it’s gonna be a real biblical clusterfuck when it finally shits the bed.
This is the curse of working in tech. As long as things are working smoothly from customer perspective then the pleas to spend the time to deal with the tech debt are ignored. Yet, when enough debt piles up and things start breaking then it’s the people who’ve been warning about the problems the whole time who get blamed.
programmerhumor
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.