Whenener I say that I'm a videogame programing student, why is still everyone judging me like "so you have no future" or "so you spend your days gaming..."
I'm not studying on stack overflow, I'm in a specialized school and I DO have a social life besides that 😡

I don't know why my position has to be labeled "developer", when in reality I ain't develop shit, all I do day after day is fixing legacy code

Support: A customer complained about a nasty bug.
Senior Dev: There are no bugs in our software, just challenges that need to be solved.

University is not there to teach anyone to code. Drops the mic.

I have 2 screens @ my desk with my back facing manager's room. Whenever he opens his door, he can see my second screen.
Thinking of a side project based on webcam that will auto open visual studio upon seeing him. Any leads would be appreciated. 😊

Hi Lead Architect,

Oh? You want me to explain how database clustering works? I guess you're just testing me because I'm new and junior.

Oh, and also explain how load balancing works? And what a bastion host is?

What's the architectural intent of this project? Let's have a look at the documentation and diagrams you have been creating of your designs.

You don't have any? That's okay, you've only been leading the architect team on this project for a year now.

Why don't you just keeping asking the most junior dev on the team about how the fuck you are supposed to do your job. As if I know how to do your job when I have zero training and am just expected to know everything.

Oh, its 3pm and you're heading to the pub. That's cool, I'll just guess what I need to build.

How bout instead of "Disrupting space-time continuum" or "Moving satellites into position" .. you just launch your crappy app.

I sent the iPhone crasher in my classgroup yesterday. Today morning a few girls out of my class said that I triggered a virus with a textmessage. Bruh

I'm currently working in call center. Making them a management system for agents. I'm the only developer there. No one asks about the progress even the owner doesn't know a thing about softwares. This gives me a freedom to do work when I want and how fast I want. But because of this I don't care anymore about the little things. and I have adopted some bad programming habits during my stay. Should I quit or what?

Teach programming languages practically. You can’t make a person learn to program when they’re just sitting in a lecture hall staring at the board. Sure, you can teach them concepts like classes/OOP/etc., but you can’t throw 20 lines of code up on the screen and expect everyone to understand it and be able to replicate it or tailor it to their needs.

It’s like learning a language. You can learn the concepts of e.g. tenses in Spanish by sitting in a classroom, but you don’t really know it until you’ve used it in real-world situations. You need practical experience building stuff in a programming language to *really* understand it.

“just”

I taught myself to programm (properly) when I was 27. I got a job in 2016 as a junior developer but had to quit in early 2017 because I relocated with my partner to the Bay Area.
I'm finding it very hard to find work, no one looks at my CV seriously 😭
I turn 30 this year and I feel like I left things too late...
It's hard being a junior dev at 29 haha.

Alright, these business cards are awesome.

Basically.

“User" is the word used by the computer professional when they mean “idiot." 😂😂😂
- Dave Barry

Raspberry Pi's in the food magazines section xD

TFW you call BS on a client/colleague's actions, they concede and you feel guilty for confroting them.

"You gave us bad code! We ran it and now production is DOWN! Join this bridgeline now and help us fix this!"

So, as the author of the code in question, I join the bridge... And what happens next, I will simply never forget.

First, a little backstory... Another team within our company needed some vendor client software installed and maintained across the enterprise. Multiple OSes (Linux, AIX, Solaris, HPUX, etc.), so packaging and consistent update methods were a a challenge. I wrote an entire set of utilities to install, update and generally maintain the software; intending all the time that this other team would eventually own the process and code. With this in mind, I wrote extensive documentation, and conducted a formal turnover / training season with the other team.

So, fast forward to when the other team now owns my code, has been trained on how to use it, including (perhaps most importantly) how to send out updates when the vendor released upgrades to the agent software.

Now, this other team had the responsibility of releasing their first update since I gave them the process. Very simple upgrade process, already fully automated. What could have gone so horribly wrong? Did something the vendor supplied break their client?

I asked for the log files from the upgrade process. They sent them, and they looked... wrong. Very, very wrong.

Did you run the code I gave you to do this update?

"Yes, your code is broken - fix it! Production is down! Rabble, rabble, rabble!"

So, I go into our code management tool and review the _actual_ script they ran. Sure enough, it is my code... But something is very wrong.

More than 2/3rds of my code... has been commented out. The code is "there"... but has been commented out so it is not being executed. WT-actual-F?!

I question this on the bridge line. Silence. I insist someone explain what is going on. Is this a joke? Is this some kind of work version of candid camera?
Finally someone breaks the silence and explains.

And this, my friends, is the part I will never forget.

"We wanted to look through your code before we ran the update. When we looked at it, there was some stuff we didn't understand, so we commented that stuff out."

You... you didn't... understand... my some of the code... so you... you didn't ask me about it... you didn't try to actually figure out what it did... you... commented it OUT?!

"Right, we figured it was better to only run the parts we understood... But now we ran it and everything is broken and you need to fix your code."

I cannot repeat the things I said next, even here on devRant. Let's just say that call did not go well.

So, lesson learned? If you don't know what some code does? Just comment that shit out. Then blame the original author when it doesn't work.

You just cannot make this kind of stuff up.

........