1. The quality of the coffee and toilet paper you encounter during an interview tells you more than promises about table tennis or fruit baskets.

2. Try to determine who their primary client is: subscribers, app buyers, advertisers, etc. It's a major influence on the company dynamic.

3. Before an interview, you can just say: "I would like to sit down with a PO and run through one backlog feature and one bug, to get a feel for the type of tasks at the company". Such an activity immediately reveals team structure, whether they have product owners & scrum masters, what a sprint looks like, how they prioritize tasks, and how organized/chaotic your work experience will be.

Never ever touch legacy code...

My grandfather the other day over the phone: "so, hows work?"
Me: "a bit stressful right now, Im realy tired at the end of the day when I get home, but its alright".
Him: "okay, so when are you going to get a real job?".

How developers deal with someone else's code!
Fixing bugs after bugs and it goes on.

Some empty-headed helpdesk girl skipped into our office yesterday afternoon, despite the big scary warning signs glued to the door.

"Hey, when I log in on my phone, the menu is looking weird"

"Uh... look at my beard"

"What"

"Just look at this beard!"

"Uh.... OK"

"Does this look like a perfectly groomed beard"

"Uh... it's pretty nice I guess"

"You don't have to lie"

She looks puzzled: "OK... maybe it could use a little trimming. Uh... a lot of trimming". "I still like it though" she adds, trying hard to be polite.

"I understand you just started working here. But the beard... the beard should make it clear. See the office opposite to this one?"

"Yeah"

"Perfectly groomed ginger beards. It's all stylish shawls and smiles and spinach smoothies. Those people are known as frontend developers, they care about pixels and menus. Now look at my beard. It is dark and wild, it has some gray stress hairs, and if you take a deep breath it smells like dust and cognac mixed with the tears caused by failed deploys. Nothing personal, but I don't give a fuck what a menu looks like on your phone."

She looked around, and noticed the other 2 tired looking guys with unshaven hobo chins. To her credit, she pointed at the woman in the corner: "What about her, she doesn't seem to have a beard"

Yulia, 1.9m long muscled database admin from Ukraine, lets out a heavy sigh. "I do not know you well enough yet to show you where I grow my unkempt graying hairs... . Now get lost divchyna."

Helpdesk girl leaves the scene.

Joanna, machine learning dev, walks in: "I saw a confused blonde lost in the hallway, did you give her the beard speech?"

"Yeah" -- couldn't hold back a giggle -- "haha now she'll come to you"

Joanna: "No I already took care of it"

"How?"

"She started about some stupid menu, so I just told her to smell my cup". Joanna, functional alcoholic, is holding her 4pm Irish coffee. "I think this living up to our stereotype tactic is working, because the girl laughed and nodded like she understood, and ran off to the design department"

Me: "I do miss shaving though"

I am from Germany.
And I wanna make a (new) website.

This is fucking exhausting 😩
(Do I have to translate it to english as well? The site will be bilingual).

I miss the time when I was a careless teenage who would just code and not care about bureaucracy...

I've never had a great experience working with designers, but this one might be the laziest! Props if it's for a friend and unpaid though.

captcha these days... 😂

Release Day

My conversation with my wife today, while I was at work:

Wife: The wifi isn't working.
Me: What's it doing?
W: Not working
Me: Try turning it off an on again.
.
.
.
Me: Is your phone on LTE? Or is it connected to wifi and the internet isn't working?
W: LTE. Aubrey (my wife's sister) said she turned it off and nothing happened.
Me: did she turn it back on?
W: Do you really want me to answer that?
Me: Just making sure. What lights are on on the router?
W: (Sends me a picture of the router with no lights on)
Me:...
W: Oh it isn't even plugged in
Me:...
W (after a couple minutes): Its working now!

YES I REALLY WANT YOU TO ANSWER IF YOU TURNED IT BACK ON!

"How would you reverse a string?"

One of the best Java interview questions I ever had! (no kidding)

Definitely should get one!

When the PM gives you the project estimates...

@dfox so is devrant turned out to be what you thought/hoped it'd be when you first started it, or is it different than the initial idea?

When your code does what you have not expected.

Credit: skillprogramming.com

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.