For a snack I have a can of Chicken Vienna Sausage and almonds sitting on my desk.

coworker: What are you eating?
me: weenies and nuts
coworker: <pause>
coworker: I always knew you were gay.
coworker: <laughing>
me: How dare you?!
me: <laughing>

I think most devs have burnout. I do. lol

TL;DR : I did not read the fucking manual.

Story :

We have a particular kind of setup with Blazor Server-side. And it does not use any SQL, bbut calls APIs.

The class to call APIs was scoped to create one new HTTP connection per new tab (even if the user opens a new tab, it's a new HttpClient).

We were fine. I read that we have 65k ports and disposal takes around 2 minutes, and we have around 1000 users. So it went into the "backlog, where things go to die."

Hard core duiscovery in the past 2 days.

Azure service plan for webapps only allows you 128 outbound connections!

System, we reboot it manually every 4 hours, while I'm working to make HttpClient unique lol

I just needed a break and vent. And "Hey kids, know that Azure service plan is only 128 sockets, not 65536."

fixing the 5th bug this week that stems from liberal use of First() on enumerables that are unlikely but not in any way guaranteed to be non-empty.

Made tortilla pizzas today!

tortilla
pizza sauce
cheddar/Colby shredded cheese
pepperoni
sausage
Parmesan

Baked 7 minutes at 420 F.

Gave me a reason to speak with a Mexican accent and hold my finger likes this 🤌.

My kid who didn't want to try them said it was good. Thumbs up!

My colleague is so annoying! Whenever she found an issue with the site or app (as I newly handle this project. The guy before this wrote redundant code overload.)

she tags everyone in the company just to point out the issue, demanding Me to fix it. Like "it is your project yoi should know better "

I check the git. That's wasn't my code at all. Some guy (idk wtf )in 2024 wrote it.

From now on, your phone might connect to the car when you get in, but will randomly disconnect after a few minutes. Your headset will connect to your laptop but the mic won't work. Your other headset will connect but the sound will cut out for half a second every few minutes.

Why? You ask. It all worked fine a week ago.

Because Bluetooth. Also because fuck you.

Fuck you, Bluetooth. Right in the fucking mouth.

Took a chance at telling my bosses how burned out I am and had a really great discussion with them.

Turns out they want me to lead the front end team, because I'm good at it and can make them do higher quality work. Agreed with me that there's something wrong with the code if you have to use a different IDE lmao.

And I can use my 30+ days of sick leave (which I've never used because I don't get sick) to take time off when I need to. Burn out is a disease.

Not all bosses are shitty.

Usually I come here to share rants/negativity but this time I wanna share an happy moment I had yesterday as a programmer.

In lots of instances I struggled to work on personal projects: I feel the desire to code cool stuff but I've often self-sabotaged myself by doing stuff like:

- self-enforcing "one man agile methodologies" with tasks, issue boards and lately time tracking
- forcing myself to do long study/research periods about the language/technologies I wanna use before writing the first line of code (and when I was able to actually end my research and get to code most of the stuff I researched was forgotten since cramming information is not effective on the long run)
- forcing myself to stick with all the "best practices" under the sun and to setup countless tools (linters, CI, unit testing...) before even getting a working POC

Usually all these stupid self imposed rules ended up in me procrastinating or pushing trough stuff struggling with headache after headache when coding actually used to feel a mostly fun pursuit to me.

Took lots of time to recognize this monster I created into my head but finally yesterday I did and I gave myself permission to:

- Start programming with just the very basics of the language (while reading a book on said language on the side at a relaxed pace, I can always come back later to improve my code as I learn more)
- Add stuff (unit testing, complex frameworks, CI/CD...) only when I need it
- Do a very basic planning (like a text files listing "must have" features and "nice to have features") and avoid issue boards and stuff, I'm working on a hobby project not on a company or a big OSS projects

It's been so long since the last time I had a programming session where I spent most time actually writing code and not researching and overthinking stuff and it felt great.

"It's just a button! Why's it taking so long to build it?"

In 2025, only at Apple can you spend $3,268 on a smartphone + laptop combo and get a laptop with 16 GB of ram and a phone with USB 2.0.

it will be fast, I said
it will be clean, I said

it was neither of those things

I don't know if I'm one of the only ones who struggles performing at their job.

I have a good foundation in Computer Science and a few degrees, yet I somehow always struggle, especially in Business Analysis. I know it's partially my specific situation since I need to catch up on some studying.

I want Software Development to be comfortable, not agony where 80% of the time I'm pulling my hair out trying to understand how something works. It just makes the job unpleasant. I currently hate algorithms, databases and custom client logic.

For me, Software Development is either fun solving a problem, or dealing with a convoluted, annoying business problem that has to be solved in a very custom way, coupled with tons of headaches about how to engineer things. I don't want that. I want fun and discovery, not agony and wishing I weren't in this industry.

That moment in the morning you realise today is going to be a shit day

How can something called SOAP be such filthy shit. No wonder people wanted to build local-only software back then.

Burnout 3... my third burnout. No, not the game.

In other news: reading commits of the BASIC programming language is like watching a tennis match.

15 LOVE 30 LOVE
GAME
SET MATCH

What in the Anus?

Mmmmm drunk food 🐓🦃🧀🥯🍳

Managers decided that the support contract with one of our most important third party servers is not worth the money.

Take a guess which server caused an outage for all customers twice already :D

CEO is blaming a frontend bug for a backend outage. The server simply did not scale with new active clients ))))))