I'm really not much of a drinker, but last night I was apparently.

I thought I played video games until I passed out on the couch and was carried to bed.

This morning, my laptop reveals to me that I had an idea for a web app last night because I made a very misspelled, yet highly detailed to do list for the app, a very blank index file, and 37 open tabs of what looks like research for certain web features.

Project seemed to be some sort of organization thing with a lot of really random and unrelated features like "fruit meterr that scales different fruits you earn" (what does that even mean??) and "sassy bill reminder".

I'm closing out all the tabs I had opened, when I see the tab showing the domain name I chose and bought. I even got the SSL certificate and email domain purchased.

Drunk me seemed to have been really excited about this idea 😶

Boyfriend and I decided to take on a simple Raspberry Pi project as an extra curricular thing to do before uni starts. He claims that I'm better at this sorta stuff than him, so I end up with the Pi for most of the week, but have immense trouble getting what we want to work.
I give up and pass it off to him to have a go when he's home. Few hours later he gets all the things I couldn't get done. I'm a mix of frustrated and relieved.
Unrelated, probably gonna wife that man

I am a home owner. Bought an apartment. Yay! 🎊🎉👌👍✊

Client: I want you to reverse engineer this piece of software!!
*posts some link to an exe on altervista along with some unrelated crap*
Oh and "I PAY"! (Because you can't even take that for granted anymore these days.)

Me: Alright, I'll look into it but I'm not a reverse engineering expert so don't expect too much.
*Closes Facebook*

Client, day after: Hey have you looked into it already? Have you finished it already?! HEY, RESPOND ALREADY!!!

Me (thinking): YEAH AFTER 1 DAY AND NO PAYMENT DETAILS WHATSOEVER, I INSTANTLY DROPPED EVERYTHING JUST TO PLEASE YOU, FILTHY RAT SACK!! You fucking wish, motherfucker. Down to lowest priority you go! And if I don't feel like doing it, how about I just drop your request and tell you to suck my fleshy snek, HOW ABOUT THAT HUH? Fucking piece of shit 😤

So... This company was in trouble. They hire me to help fix things and build this nice new stack to get rid of their old legacy monster application.

I'm there for three weeks when one of their top investors storms in. Apparently they are turning less profit than they told me during my interview. (Yeah, it is one of the things I always ask, even thought I don't always get an answer).

So this investor/shareholder guy starts on this motivation speech which is basically a veiled threat that "we" need to do better.

Obviously he doesn't know anyone in the room other than the boss. And it was apparent, at least to me, he also has 0% knowledge of anything related to software development. The boss doesn't look to happy about having to let this happen.

Then the guy turns to me. He points his finger at me and demands to know how failing so badly makes me feel...

So I answered truthfully... "I've only been here for three weeks, so I don't think I've been failing too much, yet. Now, how long did you say you've been throwing money at this failure without getting the return you wanted?" Emphasizing the "you" by pointing right back at him.

That doesn't shut the guy up, but he does bring his "motivational" speech to a rapid close.

He doesn't bother saying goodbye when he stormed out again, not even to the boss, who looks a lot happier at this point.

Apparently the guy pulled this stunt every couple of months (or weeks, if he was bored enough). After this encounter, he apparently had enough of trying to "motivate" us developers. We I didn't see him again in the 2 years I worked with the company after that.

I got a pay raise the month after. Apparently that was totally unrelated to this incident... 😙🎵

Python. Changed a function to return a tuple instead of one value in some database code. Tests pass, gets deployed, everything works. End of the month comes. Suddenly, we get a report that we're draining people's bank accounts and credit cards.

It turns out there was an untested bit of code inside the billing process that used this function. It used the function that was changed. To make matters worse, when the exception was thrown, the billing had already completed successfully, and due to another unrelated bug it would retry despite this.

So, needless to say, type safety and good unit tests are things I prioritize nowadays.

Testimony found on freecodecamp that made me laugh.

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!

When they use a photo of fucking JavaScript (no hate) code for every fucking unrelated news.

When you hit run after an hour of powercoding:

Old Mcdonald had a bug,
E I E I bug.
And on that bug he had a bug.
E I E I bug.
With a bug bug here and a bug bug there.
Here a bug, there a bug, everywhere a bug bug,
Old Mcdonald had a bug.....
E.....I.........E............I.................

[FATAL ERROR] : Program has ended for a simple reason...not telling why though...here's a completely unrelated line of code you may want to take a look at :)

Manager: Hey how come you left so many comments on my PR?

Dev: Well you’ve just recently learned how to code so there’s going to be a lot of things to learn beyond what you’ve picked up in your online coding tutorials. Don’t worry it’s only minor things like you put everything all in one function, left outdated comments in the code, have if statements 4 levels deep, have a console.log after every line of code some of which log .env variables, skipped error handling, cast to “any” a bunch instead of using more specific types, didn’t write any tests and some unrelated tests are now failing due to a circular dependancy.

Manager: THAT IS SO DISRESPECTFUL!!APPROVE MY PR IMMEDIATELY. IT WASN’T EVEN EASY FOR ME TO CREATE THE PR, NOW I HAVE TO MAKE AN UPDATE!? YOU’RE THE DEV, YOU SHOULD FIX IT NOT ME!! NEVER COMMENT ON ANY OF MY PRS AGAIN.

I just spent an hour debugging my company's web app. More specifically, I was trying to fix a bug that made a label on a comment I just made say "Posted 3 days ago".

After confirming timestamps on the server are correct with a calculator, fiddling around with the js debugger, and ruling out weird timezone-related shenanigans, I came to a conclusion.

The bug was in fact sitting, quite comfortably, between the chair and the keyboard.

Yesterday I had moved the date on my computer roughly 3 days into the future, because I was testing out some unrelated code that was dealing with Redis, and I wanted to expire all of the keys stored inside of it.

Don't blame me, my parents told me I had fallen onto my head as a child.

What is the most ridiculous over-the-top "startup" thing you've been the victim of as a developer?

Alternatively, what kind of weird startup luxury would you absolutely love to have at your company?

For me, at various companies I've worked at/visited:

1. Hammocks & fatboy beanbags. Current employer has a "Netflix & Chill" corner with nice couches, and a small gym. I have encountered isolation/flotation tanks at the office of one of our partners... which is cool, but over the top in my opinion.

2. A fully automated aquaponics garden in the lunchroom. Was awesome, until some fish died and started to rot.

3. One hoverboard per employee, at previous employer. I splashed hot chocolate milk in an arc over three desks. A coworker broke his ankle while watching me spill chocolate milk.

4. Daily scrum standup meetings, on socks, in a big bouncy castle. Not kidding. Fucking ridiculous... (but secretly fun). That employer also had spiral slides between all floors, a tiny half-pipe with tiny skateboards, and someone who rode a unicycle way too much. It was a fucking circus. Stuck in the office of a Fintech company.

5. Soldering bench (at my current company), with drawers full of breadboards, servos and electronics components. Completely unrelated to my work, but it was my idea. It's just great to build a simple kits together with another random coworker while brainstorming platform features & refining specs... much better than meetings with bullshit slides.

6. Unlimited energy drink. Developed a serious caffeine habit (15-20 cans a day), and almost got a stomach ulcer. Not beneficial to employee health.

7. I really do love working from home + unlimited holidays. Just being able to honestly say "fuck you guys, I'm gonna get drunk and play games today", and at other times working until 4am and sleeping in the next day, or taking a week to work in a park in Rome... It makes work truly feel like my favorite hobby. Combined with a good sprints and curious/ambitious people, you can easily track productivity anyway.

Hours at the office: 9
Lines of code: 4
I hate this kind of days.

I applied to Amazon recently not really thinking about it I was just bored. Dropped my CV and I was asked to fill in why would I want to work in that position. I un-ironically put “It sounds like a lot of fun”, got rejected instantly then got an unrelated message from an Amazon recruiter from another division inviting me to apply, rejected it because it didn’t sound as fun.

I’m an honest bloke I just want to have fun.

Dear Customer,

I think you misunderstand the reason I sent you some documents for review.

I sent the examples to you so that you could see what your inputs produced.

I didn't send them to you so that you could fart out your mouth and about what you want like a little kid.

If there's shit on the page it is because you put that shit in the system ....

Please have someone else who is going to put a little bit of effort into this 'super important project' contact me.

Also bullet points don't work like this:

- Here I talk about a thing but
- and here I continue that thought with no context and incomplete sentences
- Also this is unrelated.
- But this is about the first bullet point again.
- Here I repeat another bullet point but I say it in a completely different way.

If I run into a problem with code or a configuration of some kind, like a good little programmer, I Google it.

One of two things will happen:

1) I quickly find the answer to my problem.

or

2) After hours of searching, I can't find anything about my problem. At all. I change the search phrasing, adjust the advanced search settings, read all the somewhat related but still unrelated articles. Nothing.

If #1 happens, awesome, life is great, thanks Internet!

If #2 happens, it's because of one of two things:

1) I am the first person in the world to stumble upon this issue. Quick! To the Blog Cave!

2) I AM TOO STUPID TO BE DOING WHAT I AM TRYING TO DO BECAUSE MY MISTAKE IS SO UNBELIEVABLY DUMB THAT NO ONE HAS BOTHERED NOR WILL BOTHER TO WRITE ABOUT IT, ANYWHERE, EVER. I LOOK AT MY WORK AGAIN FOR THE 100TH TIME AND FINALLY REALIZE MY EMBARRASSING NOOBERY.

2.1 is a unicorn. 2.1's happen to other people.

I am dealing with a 2.2.

"Your resumé looks really good. We would really like to hire you. But you need to do this completly job unrelated test/coding challenge first."

----

"Is the test Android related?"
"Yes"
*Opens Test* -> "what ist the complexity of this function (written in c)"
*Scrolls*
"Implement algorithm xyz in Go lang"
*Closes test and breaks something*

----

"You will need to Code on a small Android projekt so we can see how you work"

"OK, how much time will i need to plan for it?"

"Our lead dev decided to make it small so its only 4-5 days."

----

What is it with all this stupid hiring test these days? And what do these recruiter think?

tl;dr: Bossmang blaming my code for a database connection issue thrown from outside of my code. Bossmang doesn’t listen. Bossmang doesn’t want to believe it’s a connection issue.

———

Bossmang: The code you wrote is causing insane spec failures in the release branch! It’s hard to follow because it’s so insane, but the cause is your code not properly handling undefined settings! Look at this! <spec>

Me: Specs pass on my machine. I ran it with both a set and nil value. <screenshots>

Bossmang: It works when you set it to nil.

Me: But a setting that doesn’t exist returns nil? <screenshot>

Bossmang: Not seeming to.... So this is the spec failure from the release: “No connection pool with id primary found. <stacktrace that starts outside of my code>”

Me: ... That’s a DB connection error. It’s also being thrown outside of my code, and from a `super` call to Rails.

Bossmang: But <unrelated> and <unrelated> and <other spec> is failing, and if I set the version, it has <other failure> instead! That calls your code first.

Me: It’s a database error. Also: <explains probable, unrelated cause of other failures, like someone didn’t mock a fucking external api call>

Bossmang: But if I restore a DB backup, it fails again.

Me: Restoring uses a dB connection, which could be exhausting the pool depending on the daemons you have running.

Bossmang: perhaps.

...

Bossmang: I still think it’s related to spec ordering.

🤦🏻‍♀️🤦🏻‍♀️🤦🏻‍♀️🤦🏻‍♀️🤦🏻‍♀️
This is tiring.