From a Dev at my old place: Don't use git for such a small project, I think we should use email to send our code to each other.
Turned out that this "small project" was a piece for a larger project.

Also turns out there's such a thing as merge conflicts outside of git.
Our code was broken for 3 days once because of his shitty advice.

Scope creep is so great. I love it when someone wants to add something to a request that has nothing to do with the request, and will only be used MAYBE once annually. /s

Just do the easy part(s) of the task first. Once you see that the task isn't as bad as anticipated, you're more likely to just tackle the whole thing. That's my experience anyway.

I used to work for an owner of a company that just would not order/buy anything that we needed. If we were running out of a license for something, he would wait until at least a week after it expired to renew it. We lost so many sales and trust from people because of that fuck.

Bought myself a Samsung s3 and while choosing what apps I want to receive notifications from, I noticed everything was off by one.

Do side projects, even if they're small. If you already have completed side projects, show them off. Employers love to see your efforts and eat that up.

Dev c++. Our school had us use it because they thought everyone in the CS department was an idiot and needed an easy to use GUI for c++ development. It was okay until we found out it was for very simple c++ development.

Doing anything outside of making one class and printing some statements was cryptic as fuck.

Welp my game dev career is over.

Got pulled into a meeting that should have been an email about requirements for something I was building. It was basically 3 people arguing the whole time and trying to decide what they specifically wanted.

They even called our other branch and started arguing with them.

Total time: 2.5h

Beer. When working on a personal project or working from home. Helps me relax, find the problem, and move on

Plan before you start a project (write pseudocode, draw a small diagram, research other implementations, etc). Without a plan, those projects are usually the ones that turn out unfinished.

Immediately know the most efficient way to implement something.

When everything kind of just clicked.
I was struggling with learning how to program for quite some time when I first started, but one day I'm not sure what happened but everything clicked. It all started making sense and I felt like I could do anything with code. It was on that day that I knew I was going to be a dev for life.

Develop AI's to steal jobs from everyone in every work field! If I can't have a job, no one can!

Not at my current dev job, but I worked for a place that had us be On-call and if someone called we would all get an email telling us who was complaining, where the site was, the problem, etc.
This service was a 24/7 service.

Anyways one of my first times on call I definitely slept through like 12 emails throughout the night, and when I woke up the next morning I saw that the owner of the company had taken all 12 and resolved the issues.

I thought I was a goner for sure.

Interviewer: Alright, so tell me what you like about software, but you don't have to limit it to software you can talk about hardware too. But yes what do you like about software?

Me:

When a ticket comes in I usually jump right on it, get about half way done with it, then either get stuck or it's lunchtime/end of day.

I really should take the gifs advice.

Our instructor for game development claims that variable names are not important if your scope is small.

Thoughts?

Here is a picture of his code he gave us as a reference the other day.

If you have a template of what you're expecting me to make, don't bullshit around for 2 weeks explaining what you think you want. Just give me the template and I'll make what you actually want.

I have this instructor at the moment, and I've had this instructor before but this semester is almost intolerable because of the instructor. He is good with processors and knows the history of how computers came to be pretty well, mostly because he lived through it, but for the 2nd year in a row he is teaching how to create games. This class is mandatory. We are creating games using html5 and Javascript. He refuses to give any game engine a chance. He gives inconsistent grades (i.e. we did everything right but got 17/30) only to go to his office, sit there for about 45 minutes watching him struggle to operate a computer and nitpick our code. He asks us what certain things do in our code, but not as in a teacher-student questionnaire, he just plain doesn't know what any of it does. Then after the shenanigans, you see your grade updated a few days later and he gives you maybe 5 points back, so you go back until you get the grade you deserve. It's a mess. This is my last semester with him and I've mapped out my last year at the uni to make sure I DON'T take any classes with this him.

Thank you for the stickers devRant! I'll make good use of them 😊

Not specifically a Dev job, but I did do a bit of development at this wifi startup. It was a wifi shop where we set up wifi for hotel clients all over the US. Anyways, they said I would make great money doing "on call" support, and me being an intern and naive I said absolutely I'd do it. Well 3 months later I was put on call essentially every day and one weekend I was with my mother and it was her birthday. At her party at this nice restaurant, with all of our close friends/family, I got a call. It took me 45 minutes to solve because of how idiotic the clients were, and after that I got 4 more calls equally as frustrating and long throughout that night. I asked for help from employees, the owner, ANYONE. Nobody helped. Needless to say I emailed the owner and said farewell that following Monday.

We work in an office where we must lock our computer screens because our screens may have confidential information on them, plus you could do things as the person without taking any blame (ie sending an email).
Anyways anytime someone forgets to lock their screen we always prank them pretty hard. The greatest thing we ever did was in our latest release we had our managers buy us drinks at the pub. Well our managers left to go to the pub and one of them forgot to lock their computers. So we downloaded an image of the blue screen of death and made it full screen, unplugged his mouse and keyboard for added effect, and locked his computer. He came in the next Monday and couldn't log in because his keyboard wouldn't work. He actually called IT to bring him a new keyboard and mouse... then he unlocked his computer and freaked out with the IT guy because there was the blue screen of death. Needless to say he got a brand new computer as well as a new mouse and keyboard.

I'd call it a win win?

Absolutely frustrated with some people's inability to make the information in their databases consistent. Had a request to make a report based on some criteria, and couldn't find the information from tables that seemed to have most of the information. Some information was correct based on what was on the website, some was not. What the fuck.

Our development team had a potluck the other day. We made sure everything was accounted for, and we even resolved conflicts!