Priorities.

Sometimes it's better to burn a bridge so you don't even think about crossing it in the future.

See, I left a company some years ago because I didn't see my future in it and all management combined had a collective intelligence of a chicken.
However, I got a call from them a couple of months ago asking me if I could return. The salary was double and the working arrangement seemed fine. On paper. WFH. Flexibile hours...
Since I actually liked the project itself for its technical challenge, I accepted the return offer. What a bad idea that was.

Of course, the things that made me leave for the first time had only gotten worse. Bad leadership, idiot developers in team leader positions. Tech debt higher than Mount Everest. Bad infra that makes you want to off yourself every time you work on it. The whole circus.
Seriously, the "senior" team leader will happily merge code that includes assert(true == true), but hold up a well written MR because he has a personal vendetta with the developer.
Personally, I always check him whenever he starts being an ass. But the poor juniors are in hell. They're terrified.
Now I'm leaving again, but this time I've made sure I can't come back.

Man, this guy really hates the nano editor:

https://github.com/rwxrob/nano

There is no more space in my server.

Monitoring is buggy.

Am I really unlucky, or are juniors these days all lazy af and such pampered babies that need hand holding all the time?
So back when I was a junior, when I wanted to learn something new, I would ask for some pointers from my seniors, could be an article, a video or even a book. From there I would look up further knowledge, play with the idea in my machine. If I couldn't understand something, or if I needed a better explanation of something, I would go back to my senior, but it was really rare.
Then comes this modern day, I'm the senior now and I'm in charge of mentoring a bunch of kids, who would treat me like their personal chatgpt. "Hey Junior #0, this is something you may want to read to help your next ticket, let me know if you have difficulty". Next day junior #0 would come back and say "I don't understand, the article mentioned X but I don't know how to do X. Can you show me how to do X?". Bro, no one knows how to do X after being born, just google "how to do X" and it gives you the fucking answer. Why the fuck do you have to circle back to me because of this. Junior #1 would refuse to read any articles longer than 250 words, and require constant 1-1 meetings to give him personal lectures. Dude this is not a class room, grow the fuck up! Junior #3 would write the messiest code possible despite my efforts to introduce tons of resources, then complain "why I'm still junior, how do I grow". Bro maybe if you learned half of what I sent you, you would have gotten promote by now. Fucking lazy kids these days!
Oh I can't fire these juniors. Top management was very clear that "we don't have budget to hire other devs for you, it's your responsibility to train them better".

Them: "What can we do to fix this?"

Me: Contact the vendor

Them: Ok, but from our side?

Me: Wait for the vendor to reply

Them: And what can we do to prevent this from happening again?

Me: get better vendors, include I.T on the process when the org decides to purchase shitty third party software.

Them: Ok but besides that?

Me: Drink?

Seriously tho, tf you expect me to do?

Not only do I write software, but now I help the managers view and understand our analytics, just like in kindergarten.

Now I'm forced to help them essentially fake data so investors are satisfied 🤡🔫

"Delete metrics X, Y, and Z for now, we don't want anyone to see them!"

"Change the label of this metric to 'unique user' views! (not total!)"

"Set all charts to cumulative so it looks like they are all up and to the right!"

Sigh.

This isn't what I signed up for.

Some serious request

Absolutely humongous

Oh the joy...

Whatsapp, Instagram, and Facebook down.

It's happening finally.

The "backend developer" has to know everything.

Error Code: 1117. Too many columns

That must be one hell of a database design!

I got the offer!!!!!!

Not well these days 🥵

User: We have been dealing with this bug for a month now! How come nobody has fixed it?

Dev: Who did notify about this issue?

User: You’re not listening we have been dealing with this for a MONTH!

Dev: When this issue first occurred did you tell anyone?

User: Yes!

Dev: Who?

User: …. Ok I don’t remember but I know I said something to someone. Anyway it doesn’t matter, your job is IT so how come this isn’t fixed?

Dev: Did you have an email? Ticket number? Teams message? Any record of where this was dropped?

User: I think you’re missing the point. We haven’t been able to do out jobs for A MONTH. We’ve just been sitting around completely helpless. We’ve been trying to figure a system using paper and pencil to replace the electronic one but it’s too complicated. How come this wasn’t fixed the second it happened?

Dev: It’s hard to respond to an issue if it’s not brought to out attention.

User: Ok but we are too busy to create a ticket! We have a million things to do and we can’t do any of them because your app doesn’t work! We’ve been sitting here telling each other how terrible this system is AND IT HAS BEEN A MONTH.

Dev: …. Yeah I got that

so true and funny
(i found this on linkedin )

dear linux, ❤️
dear windows, 🤬

An Hour ago , this happened. I wondered what happened.

Product: Hey, this screwdriver feature I never requested isn’t there. Why? Can you fix it? It’s kinda urgent.

Product: @Root please jump on the ticket above … fairly urgent.

Root: It’s Friday, I’m out next week, and I’m working on finishing <urgent comma ticket> right now.

Boss: Work on the screwdriver instead. But make sure you finish the comma ticket too!

Boss: By the way, I volunteered you for eight security reviews next month!

Security: You’re on call for AWS audits next month, too!

How do you steal a coat? You jacket.

Its getting dangerous

Manager: *taps dev on shoulder* Hey I noticed a minor bug I think

Dev: Sigh…. So then create a ticket for it

Manager: Can’t you just fix it right now?

Dev: I can but I’m currently working on that other issue you told everyone was “top priority” at the morning status meeting. Should I switch to actioning this minor bug instead?

Manager: Don’t switch just multitask and work faster!

Dev: …

Router firmware is literally always the shittiest php hackjob asscode you'll ever see

!Dev

A bit random but I'm just really anrgy

Why the fuck. Why do mosquitoes have to exist. Fucking go outside in certain places for 5 minutes and these spawns of Satan suck me dry.

I swear these things have all come through a portal straight from hell.

And then its gotta itch like fucking mad for the next days, driving me straight up insane.

I'll be glad when I get back to my place. Climate might be cold and raining a large part of the year but fuck that's so much better than fucking getting poked by these fuckers this much again.

Abraham Lincoln showed how one can rule. John Kennedy showed how one should rule. George Bush showed that every idiot can rule. Donald Trump showed that not every idiot can rule.

😂 there’s an absolute war in the comments it’s hilarious

Today I discovered that we have a CSV export button for an order transaction system, on a page which is completely disconnected from the rest of the website.

It is only being called by an internal server, used by our Data department.

They run selenium to click the button.

Then they import the CSV into a database.

That database is accessed by an admin panel.

That admin panel has an excel export button.

Which is clicked by our CFO. But he got bored of clicking, so he uses IFTTT to schedule a download of the XLS and import it in Google Sheets.

That sheet uses a Salesforce data connector.

Marketing then sends email campaigns based on that Salesforce data...

😒

Every day at work. I think everything might just burn down if I leave.

Slack.

A product which I hated in the beginning, is something that I have started admiring now.

Like Telegram, things just kept improving without bloating the shit out of the product.

What's interesting is that they came up with Huddle, an instant call and connect feature where they support Audio and Screen sharing.

Totally a game changer and a Zoom killer because Zoom could be even better in terms of UX.

Functionally, hands down, Zoom is flawless but slowly it's becoming an overkill.

I am excitedly waiting to see how both of these compete because Slack surely has an upper hand in this game.