if you make a PR, do you sometimes just fix the minor error yourself and push it and then approve it?

for example: like a typo in a variable or a wrong translation

Cars 1 was NOT released 19 years ago. No, it just wasn't. Fuck you, it wasnt. I dont care about your facts. It's all fake. You're litearlly just lying. No it cannot have come out 19 years ago. It just couldn't have, thats way to long ago. You're just weird. Calenders are just wrong

Yesterday I left an open bag of fried chicken flavourd chips in the office. This morning the entire office smelled like Colonel Sanders had paid a visit.

Got this message from my CEO: "When are we going to have a perfect working version? 100% sure without bugs? "

How do I even respond to this? "We are wondering the same"?

(for context, he requested an early alpha build of a certain feature)

My workplace just lost a contract that would bring us a €20000 revenue because the CEO refused to spend €5.

I had to make a reverse-geocode Service in C#.
I made a new empty .cs file, copy-pasted the API OpenStreetMaps endpoint as a comment for reference

Pressed enter.

n BAM. Copilot (in Visual Studio) autosuggests the ENTIRETY of the class with accurate JSON-POCO conversion ._.
I dislike AI but can't deny its usefulness in this kinda manual work. I'd take this over some low-tier junior dev anyday

So my wife picked up some gyro meat (double entendre?). Anyway, she forgot feta and pitas. So we substituted parmesan and tortillas. I said we are eating Grexican tonight. Not sure if parmesan is Italian or not. So maybe we are eating Grexican🤌 tonight.

My daughter had her gyro, but the tortilla had ripped a bit. She said she had the ripped burrito. I said the burrito must have been working out, because it was ripped.

It is kind of sad though. We had a really good gyro place in town. But the owner died and so did the business. There are no other gyro places. Not all gyro heros wear capes. RIP

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

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.

We rolled out yesterday a new update out to our Desktop application. The goal was to do it last weekend but we failed for reasons. The update is a success and now we (devs, project manager, QA, COO, support) got an angry email from our CEO, he mentioned:
- He is very disappointed in the whole process
- we released it without a coordinated marketing campaign
- That the devs should have communicated to the customers
- That the devs should have communicated internally more
- That support is getting a lot of new support tickets. I asked support, they counted 0 for this product in the last 7 days.
- Asked us to self-reflect how we can improve.

My project manager (who is currently on paternity leave) responded with an angry email to defend the dev team and pointed out that the CEO fired the marketing guy (again). The deadline is here for months, that the CEO literally ran the update locally and sold the update to new customers. He also called the CEO "lack of self awareness" and "not understanding the update process" and "disappointed in this approach". He also said that he asked the developers not to respond to the email.

Love me some drama between higher-ups

if you have mice problem, you don't get rat poison that leaks into the environment… you get a cat! 🐈

Oracle sucks. Try to do something quickly. 1000 restrictions.

My manager is complaining I'm committing broken, incomplete stuff.

Before my manager was complaining I didn't commit enough.

My manager is an asshole.

Update on my shitty manager.

He's been in HR training and leaving me the fuck alone. So it's a win so far.

got this hilarious phishing email today. check the sender's email

I'm the only one who loves programming and computers but hate most of the culture around it? The tropes (caffeine addiction, programming socks...), the YouTube "gurus" who makes clickbait titles and usually screams while reading other peoples blogs, the [hyperSpecificWebFramework]Conf where hours are wasted in which seems an infomercial for "yet another way to update an HTML page basing on a series of properties", the hackathons...

More I distance myself from this mountain of BS more my enthusiasm for tech grows

Well, my boss is officially unhinged.

He threatened me in a call. He thinks I ratted him out to HR for living over seas. Funny thing is I don't give a rats ass, he's got the wrong guy.

Going to HR now though, see if I can move teams to minimize the damage he can afflict on me.

Client: We're already behind schedule and over estimate

Also client: *keeps asking for more changes*

Why are civilians like this

Our projet's system architect posted in our chat that me returning to the team next week will be the best b-day gift for him.

I was OOO for 3 months

what am I returning into....?

TeamLeader2: Mister IHateForALiving, client is reporting a bug, we need you to check out what is happening
IHateForALiving: I'm on it, anything I should know before I start?
TeamLeader2: just check the logs, they should tell you pretty much everything you need to know

The logs:

Jira has its own query language called JQL. Also, Jira is Turing-complete.
Have a nice day!

I'm a sick to fucking death of reading 'documentation' by developers who assume you know everything they did at the time of writing and so leave out 90% of the context that would make the documentation make any sense.

Listen to me. If you are writing instructions on how to do something you have 2 options.

1. Write steps that are so detailed a person who has never touched the system could do them
2. Give enough information for a person who has never touched the system to work it out for themselves.

NOT. LET ME REPEAT MYSELF. NOT: 3. Give some half assed info that assumes you had already been working on the system and practically knew everything anyway.

If I had already been working in this area I WOULDNT NEED THE FUCKING DOCUMENTATION TO BEGIN WITH.

Visual Studio in the recent releases got some updates where it "accelerates build time" by caching DLLs or something
Good in theory? sure.
In practice? So very often, a "hot reload" now doesn't trigger a DLL swap. VS says that changes have been updated but you see stale code and you've to turn off the program and re-run it

I'm sure there's a way to turn this acceleration off and will do that after this rant, but I don't get how such retarded features get green-lit and make it to production :v

I understand that for biiiig solutions with minutes of build-time, this would be god-sent, but if it's this unreliable in my 8-Project Solution, I wonder how unreliable it'd be in bigger Solutions

at least turn it off by default if you know it's shit ffs.

Told you I'll be back

It's 2025.
We still have MSSQL with compatibility level set to 100 (matches the version from 2008).
We still have random downtime or issues with timeouts thanks to parameter sniffing.

Update? No that's expensive and doesn't provide more cashflow (ecommerce-ish).
'I just have to make better code'.

Screw you, NuGet.

gonna try working from the hospital while my youngest brother is in surgery from a car accident yay american work culture forcing productivity in difficult times

A software developer's experience life cycle:

0 - 5 years: attempt to replicate what your current senior is preaching, assuming that's the right way. Reading "Clean code" and preach it as gospel, even though you don't practice any of it.

6-12 years: gained the belief that you are better off coming up with solutions yourself, usually "sophisticated" and "elegant" which to everyone else (and also yourself a few years later) is an over-complicated inheritance ridden shit show. You have realised the "Clean code" movement is actually a cult but still believe code reuse is the holy grail.

13+ years: finally realized that simplicity and pragmatism is the most sensible way for most software development. Code is now readable, maintainable and functional. You took the few good bits from "Clean code" and ignored the extremism. These are the golden years.

The problem is most developers jump ship and stop developing before reaching the golden years, thus resulting in most software projects looking like shit.

Unpopular opinion, but it doesn't make it untrue.

MSAL, Microsoft's absolute dumpster fire of an authentication library. Who in their right mind designed this overcomplicated mess? The documentation reads like it was written by a committee of drunk orangutans throwing darts at a keyboard.
Want to do a simple login? HAHAHA GOOD LUCK! Here's 47 different configuration options you need to set up, three different flow types that are basically the same thing with slightly different names, and error messages that might as well be written in hieroglyphics. "AADSTS700054" yeah that's SUPER helpful, thanks Microsoft!
And don't even get me started on token caching. Oh, you thought your tokens would just... work? NOPE! Hope you enjoy debugging why your perfectly valid token is being treated like a expired coupon at a grocery store. The refresh token flow is about as reliable as a chocolate teapot.

I worked on a great project that was later axed and part of that was because of Msal issues. We literally only dealt with Msal issues. The app was otherwise stable. There were always issues with SSO, login, token validation...
It just couldn't work, like, at all.
I could see the clients getting fed up of the constant issues, yet, they couldn't move away from Microsoft since they'd already invested into their entreprise ecosystem. AzureAD, Office 365, you name it.

Shit like this is why I laugh whenever someone suggests that AGI will take over the world. Like, bro, we still haven't figured out how to make an auth library that actually works, and you think we're close to making a machine capable of thinking like a human?
Yeah right!

It's a new year. so everything stops working because tables don't exist for year 2025 in the database.