Ladies and gentlemen, prepare yourselves for a rant with a capital R, this is gonna be a long one.

Our story begins well over a year ago while I was still in university and things such as "professionalism" and "doing your job" are suggestions and not something you do to not get fired. We had multiple courses with large group projects that semester and the amount of reliable people I knew that weren't behind a year and in different courses was getting dangerously low. There were three of us who are friends (the other two henceforth known as Ms Reliable and the Enabler) and these projects were for five people minimum. The Enabler knew a couple of people who we could include, so we trusted her and we let them onto the multiple projects we had.

Oh boy, what a mistake that was. They were friends, a guy and a girl. The girl was a good dev, not someone I'd want to interact with out of work but she was fine, and a literal angel compared to the guy. Holy shit this guy. This guy, henceforth referred to as Mr DDTW, is a motherfucking embarrassment to devs everywhere. Lazy. Arrogant. Standards so low they're six feet under. Just to show you the sheer depth of this man's lack of fucks given, he would later reveal that he picked his thesis topic "because it's easy and I don't want to work too hard". I haven't even gotten into the meat of the rant yet and this dude is already raising my blood pressure.

I'll be focusing on one project in particular, a flying vehicle simulator, as this was the one that I was the most involved in and also the one where shit hit the fan hardest. It was a relatively simple-in-concept development project, but the workload was far too much for one person, meaning that we had to apply some rudimentary project management and coordination skills that we had learned to keep the project on track. I quickly became the de-facto PM as I had the best grasp on the project and was doing a lot of the heavy lifting.

The first incident happened while developing a navigation feature. Another teammate had done the basics, all he had to do was use the already-defined interfaces to check where the best place to land would be, taking into account if we had enough power to do so. Mr DDTW's code:
-Wasn't actually an algorithm, just 90 lines of if statements sandwiched between the other teammate's code.
-The if statements were so long that I had to horizontal scroll to see the end, approx 200 characters long per line.
-Could've probably been 20 normal-length lines MAX if he knew what a fucking for loop was.
-Checked about a third of the tiles that it should have because, once again, it's a series of concatenated if statements instead of an actual goddamn algorithm.
-IT DIDN'T FUCKING WORK!

My response was along the lines of "what the fuck is this?". This dipshit is in his final year and I've seen people write better code in their second semester. The rest of the team, his friend included, agreed that this was bad code and that it should be redone properly. The plan was for Mr DDTW to move his code into a new function and then fix it in another branch. Then we could merge it back when it was done. Well, he kept on saying it was done but:
-It still wasn't an algorithm.
-It was still 90 lines.
-They were still 200 characters wide.
-It still only checked a third of the tiles.
-IT STILL DIDN'T FUCKING WORK!

He also had one more task, an infinite loop detection system. He watched while Ms Reliable did the fucking work.

We hit our first of two deadlines successfully. We still didn't have a decent landing function but everything else was nice and polished, and we got graded incredibly well. The other projects had been going alright although the same issue of him not doing shit applied. Ms Reliable and I, seeing the shitstorm that would come if this dude didn't get his act together, lodged a complaint with the professor as a precautionary measure. Little did I know how much that advanced warning would save my ass later on.

Second sprint begins and I'm voted in as the actual PM this time. We have four main tasks, so we assign one person to each and me as a generalist who would take care of the minor tasks as well as help out whoever needed it. This ended up being a lot of reworking and re-abstracting, a lot of helping and, for reasons that nobody ever could have predicted, one of the main tasks.

These main tasks were new features that would need to be integrated, most of which had at least some mutual dependencies. Part of this project involved running our code, which would connect to the professor's test server and solve a server-side navigation problem. The more of these we solved, the better the grade, so understandably we needed an MVP to see if our shit worked on the basic problems and then fix whatever was causing the more advanced ones to fail. We decided to set an internal deadline for this MVP. Guess who didn't reach it?

Hitting the character limit, expect part 2 SOON

Whatever the fuck Python's ternary operator syntax is supposed to be.

!rant

I got hired!!

It's been a long month of jobhunting, interviews, and paperwork, but I finally got a job. Real world dev life here I come.

I broke the toilet seat on day 2 at the office and have been watching it get worse and worse until it silently got replaced two weeks later.

Oops.

Somebody put milk in the tea kettle.

To be entirely fair, I'm sure nobody from here has ever seen a kettle, let alone used one.

Oh boy.

I've been partially on-loan to another team that's relatively new at the company for a couple of weeks now, mostly to help them get some testing sorted out, and had scheduled a call with their lead the other day. The call basically started like this:

Lead: Hi
sudo-woodo: Hey
Lead: Okay, so let's talk about <subject>, but I guess you've been told the news
sudo-woodo: What news
Lead: I'm putting in my notice

I love listening to seniors because they always drop some wisdom, but this was some serious wisdom. Guy sounded exhausted at everything, talking mad shit about the company and certain people and I'm just here like 🍿. Seems understandable, a lot of butting heads with the higher-ups and not being able to do his job properly.

Unfortunately we all kinda needed him to do his job because his job involved juggling fifteen different things that the project (and like 90% of my backlog to be honest) depends on.

shit's fucked 🙃

Six hours of meetings in one day.

"If you’re not failing every now and again, it’s a sign you aren’t doing anything very innovative." - Woody Allen

While this wasn't technically a real client, it's still one of the most insane requests I've ever had.

I chose to specialize in software engineering for the last year and a half of my degree, which meant a lot of subjects were based around teamwork, proper engineering practises, accessibility, agile methods, basically a lot of stuff to get us ready to work in a proper corporate dev environment. One of our subjects was all about project management, and the semester-long coursework project (that was in lieu of a final exam) was to develop a real project for a real client. And, very very smartly, the professors set up a meeting with the clients so that the clients could tell us what they wanted with sixty-odd students providing enough questions. They basically wanted a management service for their day-center along with an app for the people there. One of the optional requirements was a text chat. Personally not something I'm super interested in doing but whatever, it's a group project, I'll do my part.

The actual development of the project was an absolute nightmare, but that's a story for another day. All I'll say is that seven juniors with zero experience in the framework we chose does not make a balanced dev team.

Anyway, like three months into the four-month project we've got a somewhat functional program, we just need to get the server side part running and are working our asses off (some more than others) when the client comes in and says that 'hey, nice app, nobody else has added the chat yet, but could you do voice recognition okay thanks?'.

Fucking.
Voice.
Recognition.

This was a fucking basic-ass management app with the most complicated task being 'make it look pretty' and 'hook up a DB to an API' and they want us to add voice recognition after sitting on their ass for three months??? The entire team collectively flipped its shit the second they were out of earshot. The client would not take no for an answer, the professor simply told us that they asked for it and it was up to us whether we delivered or not. Someone working on the frontend had the genius idea of 'just get them to use google voice recognition' so we added the how-to in the manual and ticked the requirement box.

What amazes me about all that is how the client probably had no idea that their new last-minute request was even a problem for us, let alone it being in a completely different ballpark in terms of implementing from scratch.

Team meetings on the toilet

"The best an idea gets is when it’s in your head." - Woody Allen

Finished my internship today, turns out I won't be getting hired because upper management is cutting back due to COVID.

Fuck fuck fuckity fuck, compared to the horror stories I've read here, it was beautiful. The work experience was super worth it though, despite the intern pay. Time to start looking for a real job I guess.

Day 2 of having to use linux at work and I almost nuked the /etc folder.

what a good start

For the Nth time in a row now, the team has met...

...with no agenda...
...with no note-taking...
...with no off-topic course correction...

...and has gone almost an hour over time.

Please stop doing this oh my god, we're wasting time and nobody has a fucking source when two months later somebody asks when/why this was decided and our only answer is "uh we agreed at some point" and we do this all over again.

That one time a Brazilian got into ny GitHub account.

Don't reuse passwords kids!

I worked on a game jam last year, and for the first time I managed to finish a full software project that wasn't for a job or university. It was really fun to work on, and seeing my vision come to life, even if compromises had to be made, as well as applying all the programming and project management knowledge I'd picked up until then was an experience unlike anything I'd had before.

The community aspect was great too, everybody shared and discussed each other's games and were super friendly and encouraging.

Literally painful dev learning experience: Do your damn stretches and invest in a good chair.

Spent a couple of months of WFH working eight hours a day in an awful chair and started getting back pain out of the blue. Part of my first paycheck after that went into a decent office chair, in hindsight I should've spent more on it but goddamn what a relief it was not having to spend an entire day in the tiny, back-breaking piece of shit my landlord calls a desk chair.

Welcome to this week's episode of "sudo-woodo tries to get a single Python script merged", starring...

•The software architect so senior they were working here while I was still in pre-school. Wasn't added as a reviewer and was completely absent on this project for two months but came in on this PR with a few questions, including questioning design decisions they agreed on the last time they saw the project.
•The QA lead with ten years of experience... in Java. Has never even touched Python and asked to review, only for every issue raised but one stemming from not knowing the language.
•The CI guy. A script guru who will find a problem with literally anything. Honestly the most helpful person of the bunch.
•My coworker. Hasn't said anything yet.

please send help

How ignorant we all are about the world. It's not necessarily a bad thing, just a fact. After a four year degree I've learnt so much, how a computer works from the physical phenomena on the hardware level to the inner workings of an OS to the highest level abstractions of modern web development, a wide array of programming languages covering several different paradigms, mathematics from calculus to statistics to algebra, how to work with databases, how to administrate a server, how to build a website, and much more.

And that's just in a degree. I have knowledge in one domain and I wouldn't even call myself an expert in it. Medicine, physics, biology, the hundreds of branches of engineering from civil to nautical to aerospace to automobile, to geology to meteorology to astronomy, to the practical application of this knowledge in hundreds of trades. There's so much more to know in so much depth and only recently have I realized how little we all know on an individual level.

Finding this out has been a mixed bag, on the one hand it's made me value what I know and what others can teach me a hell of a lot more, on the other, knowing that people haven't realized this and adamantly discuss and impose from a position of ignorance isn't very nice.

tl;dr I know that I know nothing

The more I use LinkedIn the more I hate it. I know I shouldn't be a nosy fuck but sometimes I've got nothing better to do for a couple of minutes on my work OS and the tab's right there. Every time I open it up it reminds me of why I'm not on Facebook. My coworkers are probably the most benign people to follow, all they do is repost company videos and blogposts. Basically advertizing, whatever.

It's the other people who get to me, the ones who are advertizing themselves. The soapboxing, the 'look at all the cool shit im doing', the reposting shit from people who I have no clue about. It's literally a window into just the good parts of peoples lives, like any other shitty social media site, but put through the filter of corporate PR bullshit. At least you can be yourself somewhat anywhere else, everything on LinkedIn needs to conform to what's acceptable to the sterile corporate environment, which amounts to showing off your certs or marketable products and the most surface-level 'progressive' social politics.

Fuck LinkedIn and fuck my curious ass for opening it like a dumbass kid who doesn't understand why you shouldn't touch a hot stove.

Every task is for fucking yesterday

Shitty meme I made when talking to a friend about how much I hate dealing with UX and people problems:

Is it normal for productivity to wildly fluctuate from one week, or even one day, to the next? There are days where I hardly get a couple of hours of real work in and others where it's eight hours straight, and I find it hard to "justify" to myself why the former happens if I'm capable of the latter.

Why would companies ever hire a manager from a non-tech background, at least for managing engineers? After reading @IAmNotARobot's latest rant I just have to ask because it makes absolutely no sense to me. Surely non-tech people should be reserved for managing non-tech roles like sales, HR, and maaaaybe team leads, right? How can you manage someone if you don't understand anything of what they do?

Just wanna throw this out there...

That time when the IT guy for your client company email you asking if we need to change code of their web based system cause they got new printer.

He forwarded the question from users like he didn't know the users needed to select a new printer or change their default printer.

God knows what he's doing there!!

Followup to my wk200 rant.

I'm like 90% sure I wasn't muted when I flushed last meeting

#Agile Tip: Awesome people will do awesome things when they have an opportunity to be awesome.

Notepad++

don't @ me

!rant

Gonna make like Robotnik because I just got a prrrrrrrrromotion!!!!

First or second week of my first job (internship) and my manager mentions that upper management has decided that a couple of engineers are being reassigned to the new technical writing team, myself included, effective tomorrow with no prior warning, before dragging us into a tech-writing standup.

A couple of hours later my manager apologizes to me for forgetting to tell me about this and asked how I felt about this. I basically answered "not well, this isn't what I signed up for", and credit to him, he pulled enough strings to get me out of that team and back to my actual job. In hindsight I suspect that it was more due to the fact that this internship was a three-way contract with the university and that if I complained they might get their intern supply cut off.

nice

In other news, I am upset that there is no way to make my avatar look like a tree.

Oh my fucking god, we're doing SCRUM, why does every task get stuck in review limbo and take a sprint and a half minimum because of it.

!rant

I've never given much thought to coffee and brushed off anybody saying it's deep as a hipster, but I'm a simple man who's only ever had instant coffee, basic cafeteria stuff and 50c vending machine trash. Well there's a coffee machine at work and there's actually a decent variety of capsules. All I have to say is holy shit, the hipsters were right. The flavours, the aroma, the strength, they're all so different and all so good, goddamn!

@dfox Could you please let rants already downloaded when online to be read offline?

Learning how to make browser plugins by shamelessly ripping off my favourite dumb Reddit Enhancement Suite feature. DevRant Nicknames, coming Soon™️.

Working in an Agile manner provides numerous ways to lessen or eliminate dependence on estimates. #NoEstimates

!rant

Finally (kinda) done with the nicknames addon. I wanted to hook into the sites actual modal menus for the UI, but I don't know JQuery and I somehow doubt modifying the existing javascript of a site from a plugin is possible, so we're stuck with knockoffs for now. But it works, it saves and loads nicknames correctly and displays them everywhere except on the notifications because I didn't add an onload listener to them.

My boss has been pretty insistent on us writing good tests (which I wholeheartedly agree with) for our new project, and being the less-experienced junior that I am, asked if we could get some guidance or a demonstration.

Took two weeks, but I finally got it said guidance... by opening a pull request with tests that weren't absolutely perfect.

Can these requirements stop having issues...

FOR FIVE MINUTES?!

Emotionally painful dev learning experience: My laptop (and only computer I had in the area) broke at the worst possible time during university and the guy fixing it fucked it up meaning it took even longer. Combine this with:

*Stuck having to learn Android Studio in two weeks to make a whole-ass app with a professor who didn't know how to make a Hello World and gave us no resources. Pair project so I had someone depending on me to do my part, meaning a lot of sharing their computer just to be able to use Android Studio.
*Having to work on another solo project by using various public and awfully specced university computers. Said project involved real-time 3D graphics and was running at about a third of the speed it should on every machine.
*Realizing how much I depended on my laptop for entertainment and that I basically had nothing that could help me de-stress and relax at home.
*Not knowing when the laptop's spare parts would arrive or if the repair man would give me bad news and even more delays.
*A very poorly timed issue in my relationship.

I know university can be stressful even though it never really affected me before or since but man, those couple of weeks broke me.

I was always into computers, ever since I was a kid. Played a lot of videogames on Windows 98 and XP, and a lot of my earliest drawings were level ideas for those games. My first encounters with code were with game creation software like GameMaker, but I barely touched the code proper outside of editing a few variables from other people's code. After that I basically forgot all about it and spent most of my teen years being a shutin.

Skip ahead to my last year of high school without much idea on what to do. I was good at math when I wasn't being a lazy shit, so between that and what my parents expected of me, I was prepared to go to university for civil engineering. However, two things changed that decision, the first being a great IT professor, when me and a friend were so far ahead, he started assigning us some harder work, and suggested we study computer science at university. The second was a super jank and obscure open-source early 2000's game that somehow still has a thriving community and is actively being developed. I stumbled upon it by chance, and after playing for a while, I submitted a balance change on the GitHub repo. Even though it was just a single variable change, that time I got it. That time I saw how powerful programming could be and what could be done with it. I submitted PR after PR of new features, changes and bugfixes, by the time I left there I had a somewhat solid grasp of the fundamentals of programming, and decided to enrol in the computer science degree.

Enrolling was possibly the best decision I ever made (not america; debt isn't an issue), as well as giving me actual social skills, every course I took just clicked. The knowledge I already somewhat intuitively had a vague grasp on from videogames, general computer use and collaborating with russian coders who produced the jankiest shit that was still somehow functional was expanded upon and consolidated with a high-quality formal education. Four years later and I'm fresh out of uni, it was a long road between when the seed was first planted in my mind and now, but I've finally found out what I want to do with my life.

won't know for sure until i find a job though ffs

Dealing with government bureaucracy today. Prepare for pure anger.

First of all, what fucking dipshit site does testing and maintenance in production without letting users know? Bitch I'm getting an invalid date error when I use your own stupid date selector and I had to waste the office lady's time asking about it because you couldn't be arsed to either test your shit properly or actually take it down if it's broken. Who made that stupid ass decision and why the fuck did nobody question it. Fuck you.

Is the devRant website not feature complete or am I just stupid? Liked rants and comment history only go like 30-40 entries back unless you use the app.

Best documentation have probably been most language docs and references I've worked with, official or otherwise, especially C++. Completeness, consistency, tidiness and examples really help a lot, since I know I can rely on the docs for basically any problem and makes work so much easier since I'll be guaranteed to leave understanding what's up.

Worst documentation has got to be the internal docs we had to create for a seven-man uni project, you couldn't find shit in the sea of docs that were out of date or just plain wrong. It was so much easier to ask whoever was working on that part about the intricacies of the cobbled-together mess than to either read the code or the docs. One absolute mouthbreather was working on the database docs and put in that it stored ArrayLists. Fucking Java ArrayLists in a motherfucking database. One day I am going to rant so hard about this dumbass and it's gonna be a spectacle.

Bonus points goes to the company's public documentation at my internship. It was good and pretty complete, but sometimes there was a document from 2 years ago that had been written by a non-english speaker that was absolutely awful. Some of them were so bad that as soon as I'd finished learning what I needed to, my mentor told me to go and fix the docs, I don't blame him.

Day one of the sprint and my coworker has already found some fucked up requirements.

Goddamn do I hate this shit sometimes.

My homies really out here giving me three units to test spread out across two + four thirds of a file and expect me not to raise an eyebrow.

No, that is not three + one third. That would imply that the thirds all belong to one unit, or one file for that matter.

Just got back to a solo project I hadn't touched in 5 months due to having other priorities. The whole thing is probably less than 1k LOC split over a half-dozen files and I'm not sure whether I should be angry at my past self for leaving the most recent part untested and insanely bug-ridden, taking almost an hour a fix, or be happy that past me organized and documented everything well enough for it to only take almost an hour to fix.

!rant
Ya boy is now officially an intern! I'm starting next week, everything is sorted except one thing: we have to bring our own computers and basically get to use whatever software we want. I've got a fresh install of Mint and was wondering what IDEs or editors everybody here uses (and recommends), since I only really have a bit of experience with Atom and Netbeans, and I don't think I'll be able to get away with coding in Notepad++ or Gedit here.

I wanted to make a (shit)post when my ++'s were at the same number as Sudowoodo's pokedex ID. Missed it ages ago by a long shot but I woke up today to find out that I missed Bonsly's pokedex ID by a single ++ that I got an hour before.

I've been looking for an internship for the past couple of weeks and just had another interview today. I was given a simple code test that involved changing some of the features in a small program, nothing too challenging except that the program was insanely buggy and had a tendency to spit out the wrong result if you looked at it funny, and that was before I started touching it. I don't even want to know what production code looks like...

A woody joke-
What would happen if you had a wooden car, with wooden seats, and a wooden engine?

How did you decide what you wanted to do with your career? I'm fresh out of uni and am looking for work but have no idea what roles or languages or software types I want to work in, only a vague idea of stuff I don't want and a vague idea of what could be nice. I'm also at a bit of a crossroads because I've applied to multiple very different jobs and have no idea which one to accept if multiple offer me a job (given that there weren't any red flags when interviewing).

Is LinkedIn actually any good?

Never used it and now that I'm a few months away from graduation I might just start. devRant is usually straight to the point about these things, what do I get out of bothering to use it?