You can lie but you can't hide:

Wake up to this. I'm calling in sick.

200 OK
{ ok: false, error: "Not found", code: 404 }

"Hey, quick call?"

No.

They ate their cake and still expect to have it:

Fix my depression
Learn C++ properly
Fix my life's future
Try to pick up a relationship which I've dropped out of stupidity again.

Once C++ walks into a bar and sees C.

C is drunk, falling on the floor, spitting, and swearing.

How classless! -says C++

Happy holidays

My first serverless experience

Forgot to secure my mongo db instance, found half the data gone, and a new db holding me at ransom , learn_how_to_recover_your_data , good thing offline backups are a thing.

Recovered in no time, never will I ever repeat this mistake

Beware the Nvidia installer.

So today I receive 23 emails on DMCA takedown notice from last year project (which is a personal project). I asked Github why they think it is violating their policy, they told me they receive tonnes of complaints from a company, they shared the chat and that's the ex-company that fired me.

Even the project is not related to them, they seem to want to "Cancel" me on Github. Bro this is Github, not Twitter! Cancel culture does not work here.

Some of my IoT projects they flag it In Github, which I believe my ex-company they don't do any IOT projects. How the fuck it is violating their so called "code nondisclosure"?

The joys of using overpriced enterprise software...

Me: Hey, I tried connect to the server, but I'm getting a "connection refused" error. Is it really running.
Other: hmm, I'll check
Other: The host restarted, but I'll get the software up again, no problemo
Other: I started the server again, but there's, but it's throwing errors while initializing. Time to write customer support

And then you get that premium customer support that think we don't know how to use their software at times. And once they realize we do, they don't know much better either. And once they realize we know how to use it there are 3 possibilities:
* They need our help to debug stuff before knowing what is going on
* They need to release a new version and accidentally break backwards compatibility and create enough work for us to burn through the clients contact hours
* They provide helpful advice (secret ending)

These fuck don't even release a proper changelog for their software nor their manuals.

HR: Hey you really need to be more sensitive with what you say

Dev: What makes you bring this up?

HR: Well we had a concerned employee overhear you telling one of the interns that the Russian word for “approved” is “blyat”.

Dev: Ah.

What do you think?

Well I did it guys. I'm officially a Software Engineer.

I'm feeling serious imposter syndrome. Working on telling myself that I'll be OK though.

In 2022 be like

COVID variants should adopt a semantic versioning, rather than using greek alphabetics.
COVID v.19.2.34
COVID V.22.1 Beta (testing in US)
COVID v.22 release 1 (being tested somewhere in London)
COVID v.22 nightly builds (still brewing in China)

Manager: our file IO is slow, any suggestions to make it faster?

Code: multithread writing to a few hundred small (temp) files then single thread combine to one big file and delete the temp files.

Eyes: bleeding

Interviewer: "I'll checked your GitHub, your side projects looks very interesting! Tell me about your other hobbies. "

Me:"Other hobbies? "

Manager: How come the intern does way more tickets than you?

Dev: Because you told me to only give him the easy ones since he either can’t do them otherwise or takes too long on the hard ones

Manager: Well how is he going to learn if we only give him easy ones?

Dev: That’s what I told you when you orig—

Manager: Assign him ALL of the hard tickets on your board immediately!

*Tickets closed per day drops significantly*

Manager: WHAT IS TAKING SO LONG ON THESE TICKETS!!!!!

Dev: …

Dev: Hey our current server is starting to chug a bit. Can I get approved for $1200 additional spend to double the speed?

Manager: *Sharp inhale*. We need this project to cost as little as possible, we really can’t justify spending any additional money for any reason right now.

*2 days later*

Manager: YOU ARE APPROVED FOR $100,000 TO IMMEDIATELY IMPLEMENT SOMETHING RELATED TO NFTs IN ANY OF OUR APPS. THE BUSINESS NEEDS TO EXPAND INTO THE METAVERSE ASAP IMMEDIATELY. I NEED AN ETA BY EOD AS TO WHEN THIS CAN BE ROLLED OUT.

Dev: …

Manager: We need to setup the security in the Mexico server

Dev: You mean that 3rd party firewall add on?

Manager: Yes

Dev: And set up the billing on the Mexico account?

Manager: Yes

Dev: lol, sure thing I’ll create the ticket

Manager: What’s so funny?

Dev: Nothing

Ticket: Build wall and get Mexico to pay for it.

surprise API

So today this Mother F**ker get HR to back him up to accuse me of not communicating well in the team because I consistently asked him (the code owner) why he kept coding not following the coding guideline.

How is it not communicating? He literally ghosted me and blocked me every time I ask him questions. Which I somewhat don't understand what he is trying to do. HR lady told me that a senior software engineer should have the knowledge to understand everything and all the code.

But the code looks like this :

No complaining on this.

Statistics never lies.

We're fakked.

I think the weekly rants just exist because @dfox & @trogus got banned from stackoverflow and they still have questions.

When it comes to learning cutting edge tech... Go build already!

I found Rust intimidating.

I read the first few pages of the official book, got bored, gave up.

Few months later, decided to write a "simple" tool for generating pleasing Jetbrains IDE color schemes using Rust. I half-finished it by continuously looking up stuff, then got stuck at some ungoogleable compiler error.

Few months later I needed to build a microservice for work, and against better judgement gave Rust a try in the weekend. Ended up building an unrelated library instead, uploaded my first package to crates.io.

Got some people screaming at me that my Rust code sucked. Screamed back at them. After lots of screaming, I got some helpful PRs.

Eventually ended up building many services for work in Rust after all. With those services performing well under high load and having very few bugs, coworkers got interested. Started hiring Rust engineers, and educating interested PHP/JS devs.

Now I professionally write Rust code almost full-time.

Moral of the story:

Fuck books, use them for reference. Fuck Udemy (etc), unless you just want to 2x through it while pooping.

Learning is something you do by building a project, failing, building something else, falling again, building some more, sharing what you've made, fighting about what you've built with some entitled toxic nerds, abandoning half your projects and starting twelve new ones.

Reading code is better than reading documentation.

Listening to users of your library/product teaches you more than listening to keynote speakers at conferences.

Don't worry about failures, you don't need to deliver a working product for it to be a valuable experience.

Oh, and trying to teach OTHERS is an excellent method to discover gaps in your knowledge.

Just get your fucking hands dirty!

Saw this on LinkedIn

It's painful.