[strken]

It's an almost exact copy of my last few months, right down to the 10am start.

Except that all our other senior engineers got laid off and there's nobody to pair with, I don't give two fucks about bullying because at this point the entire company knows I'll quit on the spot if they try, and our problems are mostly that the remaining team cannot understand the terrifying eldritch decision making process that led to fun little patterns like "wrap every API call in a try/catch and then ignore the errors".

I am seriously considering doing a TAFE course and becoming an electrician.

[Buttons840]

They took inspiration from the error steamroller: https://github.com/ajalt/fuckitpy

[CSSer]

Perhaps if one coupled this with a multimodal LLM we could achieve a singularity

[GreenWatermelon]

> wrap every API call in a try/catch and then ignore the errors

This describes the project I'm working on at $job with eerie accuracy :sob:

Dare I ask, was that project written in Java?

[strken]

Unfortunately my personal hell is written in Node.js.

I am so very sorry, both that you are suffering through this too and that the infection has spread.

[392]

Will you feel better looking at a wiring job that seems guaranteed to burn down the building if you don't fix it? And will Management agree?

[strken]

I wish the abominations software engineers create were as regulated and fixable as a bad wiring job. I would feel absolutely chuffed to work in an industry with licensed inspectors and standards bodies.

I am currently dealing with a system involving four separate serverless functions that call each other. There's no reason whatsoever why any of them need to be network calls. The fourth function just calls the first function again. One is in a different region for no discernible reason.

[hmaxdml]

Would be nice if there was a serverless library that lets you do in-process orchestration so you don't need abominations like Step Functions ;)

e.g., https://github.com/dbos-inc/durable-swarm