My biggest dev sin is not writing any unit tests for devRant :/

Did you say security?

When I find a bug that I made

A SEO expert walks into a bar, pub, drinks, beer, alcohol

My mum said I needed company, so I started one

Met a cute girl at the ATM today.
Long story short, she gave me her Instagram account and I ended up giving her my GitHub account.

When you're not creative enough to make a post that would give you some stickers but you have a 3D printer...

1. Customer wants X.
2. Developer delivers X.
3. Customer wants developer to change X to Y for free.
4. Developer demands money.
5. Customer gets mad.
6. Developer compares situation to ordering a hamburger, consuming it, and demanding a pizza for free because customer didn't like the hamburger.
7. Customer pays

Welcome to 2017:

Facebook = Blue Snapchat
Whatsapp = Green Snapchat
Instagram = AllPossibleColors Snapchat

Ps: First rant **yayy**

*Me and my GF who works for CIA*

Me: Send nudes
GF: Whose do you want ?

There are two kinds of people in the world:
There are those who can extrapolate from incomplete data,

My friend said an intern designed this UI for an internal site.

No. Just... no

Huge code improvements

!rant
A few days ago a friend of mine rang me up complaining about internet issues with his computer. As usual I did the "is it plugged in, turn it off then on again" sort of thing to waste time while my pasta was cooking. After a while he asked if I had another bogus solution, so I suggested flushing his toilet.

He runs off, I hear the flush, comes back and viola - it fucking worked.

The point of this is: if it don't work, flush the toilet. You're welcome, tech support out ✌️

Graphics girl

This is going to sound stupid to some.. I recently finished sololearns JavaScript course and I loved it but I want to learn more but I have no idea where to start.. I've been browsing tutorials on YouTube but it doesn't help too much.. does anyone have any suggestions?

Never make the same mistake twice.

There are so many new ones, try a different one each day.

A few years ago when I was still an apple fan boy, friend of mine bragging me about how android is awesome, we were drinking some shots at our local pub and I was starting to get light headed. At one point he showed me so called "terminal emulator" app. I checked it out, and assumed it's an emulation, just like dosbox, so I decided to verify that "rm -rf *"... (the phone was rooted)

The phone shutdown within seconds, I couldn't stop laughing, while my friend was shock that his new phone was longer booting.

Luckily he managed to reflash the ROM. What can I learn from that experience?
1. Don't drink and sudo
2. Don't call your app an emulator if it's the real deal.

Reality

Story of my life..

When languages play poker

We were doing some temp work, and a girl we were working with had gone out to talk to her boyfriend on the phone.

1. Flip screen orientation 180 degress
2. Take screenshot
3. Set that as wallpaper and flip back
4. Hide icons, hide taskbar, move taskbar to far right edge
5. Invert mouse movement
6. Invert mouse buttons
7. Flip back 180 degrees, everything looks normal.

Sit back, relax and watch the show.

P.S. she gave up, we had to fix it.

Oh yes I know how it feels.

I find it super annoying, this trend where no one wants to write learning documentation anymore, but instead put up a bunch of demo videos and video "training courses."

I don't want to spend 5 minutes watching you do something that would take me 10 seconds to read. I can't search for terms in your video, and I can't use them as a general reference manual. I can't go at my own pace, easily keep my place between devices, enter code as you go, the list of cons goes on and on.

I would rather pay you money for a good eBook (and no, PDFs don't count), than to have the only realistic way to learn about your software be a playlist on your YouTube channel.

This, however, this...

Went to check out Ansible again, because I've heard good things lately and it's been a couple years since I've looked at it.

Took me a while to find their docs because there's almost no mention of anything on the home page except trying Tower for free.

Found the docs. The first item there is the Quick Start Video and I think, "Cool. That's a good use of video, showing off the product."

I dig out some headphones, click play:

"Ansible is a powerful" BOOM!

Enter my email to watch the video?!

Ah, forget it. Maybe I'll see you next time, Ansible.

After months of tedious research, I finally feel like I understand machine learning.

All of my programmer buddies are in envy, but I keep trying to explain that what I finally get is that it's not as hard as it's presented to be.

I feel like a lot of the terminology in machine learning is really pretentious and unnecessary, and just keeps new people from the field.

For example: I could say: "Yeah, I'm training a classification model with two input neurons, a hidden activation layer, and an output neuron", and you might think I was hot shit. But that just gets translated into "I'm putting in two inputs, sorting them, and outputting one thing".

I feel like if there was a plain language guide to machine learning, the field would be a lot more attractive to a lot more people. I know that's why it was hard for me to get in. Maybe I'll write one.

When I was intern I saw best use of comment ever. There was a code block that you can only end up there with FATAL ERROR. And there was these lines as a comment :

Last thing I remember, I was
Running for the door
I had to find the passage back
To the place I was before
"Relax, " said the night man,
"We are programmed to receive.
You can check-out any time you like,
But you can never leave! "

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

Just buy more and more and more books.
And coding. No one needs books, if he don't code.

when the only solution to your problem is in a youtube video made by a lame 12yo kid