I just sleep less :/

<sarcasm> best advice?

Write microcontroller code in C++ even if the underlying OS won't understand. You can always decompile the program to C code and use the generated code.

Things he forgot to mention:
- cannot use most of C++ core functionality (basically no STL, no exceptions, all of C++11)
- have to get your code to compile twice (C++ and C afterwards)
- debugging that generated C code is a pain in the ass
- have to debug twice

VSCode you fucking piece of shit!

Just got my code working and rewarded myself with tweaking some of the configurations. Coming back to my file and it's all irrevertably messed up with randomly pasted and probably some deleted code snippets.

How's that even possible? 😡

duration = startTime - endTime;

So much facepalm

(I may be an hypocrite... https://devrant.io/rants/384227/...)

Set all my editors to autosave when they loose focus ~

Makes me go nuts when working on other machines :/

I'm a TA myself and just yesterday wanted to defend my fellow TAs and CS/IT teachers from some of the rants here. Of course not all of the rants are but I found a few quite unfair towards us and I can fully understand a TA getting confused and tired after 5-7 hours of helping and wrapping your head around some of the harder problems the students run into.

However, I'm also a student myself and right now I'm fucking fed up with the shit my supervisor gives me regularly .. So let the rant flow!
(disclaimer: the following text uses “you” to address the rant recipient. So, dear reader, don't feel offended)

First of, why do you fucking care when and especially where I'm working on your project when you know I'm only working part time since I'm usually tutoring students by daylight. Having me come in after my TA shift to work on your project instead of letting me go home, get some rest and food, and start working with a fresh head is neither helping you nor very productive. Also, if you want me to be productive and use your fucking tools to get going faster you better not make me fucking debug your fucking tools. For instance, I don't even have the same first name so all your fucking paths are invalid on my fucking machine! Also, I get that your machine is more powerful than mine and I don't really care about it as long as you don't fucking push convoluted messy timing sensitive scripts and make me search for the correct values on my machine. And, if a file your script is trying to delete is not there aborting is not an valid exception handling!

And don't get me started on the scripts that actually do some work besides setting up your fucking toolchain!

Not sure if that qualifies as prank...

Had an pretty incompetent CS teacher and used to simply unplug her PC when we had enough of her shit. Usually took her about 45mins to figure out what was wrong with her PC and another 5 of ranting why we'd do that. Eventually she started to check the cable first which reduced the ”downtime” to about 15mins.
However, we soon started to flip the power switch at the back of her machine instead. She never figured that out and called IT several times to fix it.

Thinking about it, it's probably worse than a prank 😅

”... Have to use python”

Boss: I wrote some tests and there is a bug in your code but I cannot find it. Fix it
Me: Sure. I'm on it.

Narrator: 5 minutes later

Me: Boss, I found the bug. It's in your testcode...

Seriously... WTF?!

(before someone suggests that my code should handle all test cases... He tried to measure the time the program needed to response and fucked it up...)

Feels like I'm the only one turning on some movies or series to not get distracted while coding?

Well, not necessary my favourite but the first one I learned.

I think the weird syntax and semantics combined with the ridiculous average length of variable names is a major flaw in this one.

Writing an embedded webserver recycling code that is in use for a few years now. Can't get my ’getStatus.ssi’ working. Turns out ’statusTag’ cannot be used and for the last couple of years noone cared that the status field was empty.

That's the first time I did such a thing and it took me only one unpaid (!) day to debug that piece of crap thinking my idiotic predecessor delivered halfway working code.

Is verifying and communicating broken code really that hard?

Was pretty ill for a couple of weeks in 7th grade. Decided to not just lie around but also do something interesting ~ started coding, never stopped since 😊

All those complaining about getting interrupted while coding/debugging. Imagine getting interrupted twice in every 3 minutes during your anyways short working time (talk 2 to 5 hours) 'cause your actual job is to tutor people in using a toolchain and not developing it (at least not during that time)...

Tell them to not buy the ceapest $Machine. They will buy the cheapest and complain why it's not working few weeks after.

Or more specific:
Tell them to buy 1TB ext storage. They will come complain that their data didn't fit their 500GB cheap ass solution and, clearly, it's your fault 'cause 500 > 1 ...(sic!)

Trying to understand other people's code like:
- 6 README, in total 7 lines (that's all there is for documentation)
- 40% of code is commentary like (original code, not altered...)
// if(a = b)
// c = d; // this is not working

Why is there no tool autoinstalling missing programs using your favourite pac(kage)man(ager)?
Like so,
$ program
>> couldn't find “program”. Should I install it? (Y/n)
If there is one... Shame on me *rings bell*

Also, yay! First Post!