Interviewer: Explain Deadlock and I'll hire you.

Le programmer: Hire me and I'll explain it to you.

If I had to name one of my weaknesses it would definitely be impatience.

When I'm working on a backlog issue I want it to be done, finished, pronto. In the real world that's ofcourse not always the case, I can't disturb my colleagues with every question or ask for feedback every minute. I also hate it to have to wait for someone else to do something for me if it's blocking me, like when I need to fix something on a server but don't have access or when I somehow don't have permission for something and have to wait for someone to come and fix it. Even worse: Slow programs that fuck me up when I _just a second ago_ figured out how to fix a bug or implement something.

I also have to wait for pull request reviews so I usually end up with a bunch of stacked PRs that all feature small changes but are dependent upon each other because I needed a change for a different change, never more than 2-level stacks though!

Obviously it's a bit childish to lack professional patience, but it's definitely something that I wanted to rant about and think I should grow in.

TLDR: programming helped with my math weakness

I've always been bad at math. I always failed my math quizzes, and to be honest the only thing that I remember from that time was that I hated it, I didn't want anything to do with it, to hell with functions and formulas and all of that garbage.

Fast forward a couple of years. I just started my masters degree in machine learning and I'm sort of inclined to applications of deep learning in signal processing. Currently I'm writing a fourier transform in raw python and I've never had more fun. I feel like programming has helped me a lot with math, being able to see how each component behaves when you write a function helps a lot! Being able to plot things helps a lot! Not having to imagine mathematical functions as esoteric mystical wonders but being able to split them up into small components and seeing what you're doing wrong HELPS. A. LOT.

Just felt like sharing. I feel like programming has made me a generally smarter person, in regards to how I approach problems and think about stuff.

Welcome to the future, where a video platform is a better radio station than a dedicated music service.

Wow...lets a minute to appreciate the unsung hero's that revolted and went on to lead and win the battle against IE6.**shiver**

https://blog.chriszacharias.com/a-c...

The majority of you will not understand or be able to appreciate the gravity and extent their actions had on improving quality of life for web developers globally... that is the true gift & legacy of their noble deeds.

and yes it was that bad... no, actually it was even worse - the best words i can use to describe (attempting) development in IE6 is that it felt like we were imprisoned in the software equivalent of a concentration camp where they had perfected the cruellest form of torture, where they allowed us to develop amazing next level experiences in modern browsers just so they could watch all hope drain from our faces as we were forced to destroy them, tearing out the magic in the name of IE6.

Back in grammar school we started programming in TI-Basic on a TI89 Titanium as it was part of math class (calculus and geometry). I didn't really understand much because the teacher thought it was a great idea to start with recursively calculating GCD (and we were in a sort of "linguist profile", nobody had ever touched a line of code in their lives before). I still liked it though and by some coincidence I got an old Win95 compaq notebook to play with from a friend.

I started playing around with the CMD prompt and batch files and could apply some of the things I had learned on the TI, like GOTO or If statements. I still didn't know what I was doing of course, and so it happened that I used the > file pipe when trying to compare two values. Suddenly there was a file with some code fragments and I started to get what I had done. I put the file pipe into an endless GOTO loop and was amused how those few lines filled up the whole desktop with nonsense files. I went on to refine this a little so I could control it with another file that acted as a kill switch when present. Over the next weeks I played some more with it and made it write out and start another batch file that would check whether the original script was still there and recreate it if not.

That notebook was so large and heavy I could not bring it to school, so I wrote all code by hand on paper and typed it in when I got home, that way I could still code in class when I was bored and no one would notice.

So my first ever "program" that I wrote myself was some lousy malware.

11:41 a.m. and I am almost ready to be productive.

worth it
http://expensivecheesegrater.com

"I think I can automate this..."

all user input is evil
trust none of it

I was really hyped for what I would learn by doing internship.

The files on the web app server are updated by drag and drop on FTP.

Why the hell there is a skype meeting with around 100 participants... And all i have to do is just connect and listen to same 2-3 persons... Repeatedly.

PS- mostly no one even listens😑

Oh wow.
Google deems me worthy!!?!!

Nobody:

Senior frontend Dev at my company: "microservices best thing ever"

Also him: "Relational databases gonna die"

Also him (talking to the DB team): "You're gonna dissapear, Mongo is the future"

Me: "Eh... Dude, Mongo is still a database.."

Him: "Microservices"

Send help...

When a hiring manager wants 5+ years experience in Swift.

Swift release date = June 2, 2014

😂👍🖕

"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.

We have a 15-machine cluster that went down last night because one machine in the cluster went down. Apparently having a cluster for redundancy is just a nice idea and doesnt actually work in practice.

Also I shouldnt have to go to a vendor's forums to find out the bug that is causing my cluster to go down is fixed in a future version. It should be in the goddamn patch notes!!!

I did it! I told her. I admitted that I have a crush on her. It was awesome, we were in her room, chilling and having Belgian beer and looking over at the beautiful dome of Les Invalids and the lights of Paris through her window. It was raining a little bit. All perfect.
I told her how I really enjoyed her company and how I found her really cool and interesting and how I had a not so small crush on her. She was very surprised but she was glad I told her. I'm really proud that I did something so big.

Oh, she said no btw.

Drop ur file here to convert it to another file type

10 mins later after conversion

99%

"Sorry but u can't convert ur file cause u got an adblocker enabled pls disable it and try again"

Have u guys ever whipped ur dick out and smacked the monitor with ur dick with hope that ur dick smack will transmit the smack into the website across their face

Source: /r/ProgrammerHumor

My company doesn't allows or uses Wi-Fi. It's too dangerous... Like fucking really. We also don't use a repository. We version stuff by dates folders. Yes we are a ecommerce business.

WTF!?!?!?!?....

Ok WTF

*Looking at other student’s code*
Me: Why do you have a line that only says “var != var2”? That doesn’t do anything.
Them: That tells the computer to set var to anything except var2, right?
Me:

I had to go help marketing with a website UI issue today:

Me: What version of IE are you using?
Her: Oh my god! Did you say virgin?
Me: No, "Version".
Her: Hahaha you guys I thought he asked what virgin am I using!
*room erupts into laughter*

WTF is this high school?

Boss: "I looked at a testing suite. It is $2,500 a license and I'm buying 60 licenses. You should probably get familiar with it."
LeadDev: "Um, we already use NUnit, and it's free."
Boss: "Hmm...I'd better add Pluralsight training in the budget so you can learn about the new program."
LeadDev: "Oh, no...we need new laptops more than we need software."
Boss:"New laptops? Not my budget. When we buy this new software, everyone is going to use it"
LeadDev: "Everyone? How will you monitor it's usage?"
Boss: "I'll have networking send me captures of all the running tasks on the dev machines. The test suite better be running. Writing good tests will be our #1 priority."
LeadDev: "Um, we already write tests using NUnit."
Boss: "I don't understand what you are saying. I need something I can visualize. This UI testing suite is exactly what I need."
LeadDev: "Maybe the testing suite would be better suited for you and QA?"
<click..click>
Boss: "Submitted the budget. There will be a test server available for you to configure. This whole project costs over $100,000, so don't screw it up. Any questions?"
LeadDev: "Oh...well...what server ..."
Boss: "Dang...sorry, I'm taking off the rest of the afternoon. We'll talk about this more on Monday. Get started on those Pluralsight videos. I'll expect a full training and deployments by next week. Have a great weekend!"

"Let me review your code, I used to work as a toilet cleaner"

"This is not an application: it's a bug pretending to be an application." (This comment was left as an app review on Google Play Store)

Someone on the IP 127.0.0.1 has been creating a lot of bugs in my code, please beware of you notice any connections from that address.

And that was enough encouragement