Fucking Bureaucracy

I checked out a mining technology course at the college. It was a boring class.

s3 storage sucks. Requires you to implement special stuff in software. The s3fs is a terrible thing not supporting many native file operations. For example, i can't cp * /to-target. It can't do nothing.

So, that was a short adventure. Now i found: https://interserver.net/r/1035270/ (affiliate link, why not). 3,- 1tb storage WITH complete vps. 1gb / 1 core but it does great as sshfs drive. It works so fast, i gonna host complete projects on it like https://devrant.molodetz.nl. sshfs drives really have the comfort of a native drive. Boarded just uploaded 600Mb to snek in two minutes. That movie was completely streamable in the snek web interface, you could comfortably click trough the video.

So, time to make a custom script to push all data from s3bucket (blegh!) to this beautiful drive.

Stop calling non-engineers engineers.

Do you enjoy pain? Love being mistreated while paying $100 a year for it? Welcome to Apple Developer Enrollment!
You'd think for a company that claims to provide "seamless" experiences, their enrollment process would be super straightforward, but no, get ready to waste incredible time with generic error messages.
"Enrollment through the developer app is not possible for this account".
Great! Just great. My peasant app wasn't worthy of being on the almight App Store anyway. Forgive me for trying, my lord.

WTF.

First, they make you prove your existence with endless verifications. Need a D-U-N-S number? Good luck because it's a nightmare. Support? Barely helpful. And if anything goes wrong? Expect weeks of waiting with zero urgency from Apple.

And that $100? You pay it every single year, just to keep your apps measly alive. Meanwhile, Google charges a one-time $25. Fair? Not in Apple land.

And if they randomly decide your app has an issue? Boom, it'll be gone. No warning, no clear answers, just frustration.

So yeah, if you're a masochist who adores pain, jumping through hoops and paying for the privilege, Apple’s got you covered!

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

it was neither of those things

When you think about it.. we, DevOps, are the Mario Bros of the tech world.

We do the building, maintenance and pipelining so that whatever shit developers produce, it would end up in the right place w/o getting stuck

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.

The Q&A section on https://learn.microsoft.com/ is freaking USELESS!

Every question is answered with a wall of text that is 100% irrelevant and I'm pretty sure it's AI-generated

Triggered by a spelling error in a backend API endpoint.

Must resist urge to change it.

It says "respondants" instead of "respondent".

A new deployment is planned tomorrow. Fourth try is the charm 🙃

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?"

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>

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.

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.