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"

*client calls in*

Me: good morning, how can I help you?
Client: my ip is blocked, could you unblock it for me?
Me: certainly! What's your ip address? Then I'll have a look.
Client: I'm not giving you my ip?! That's too privacy sensitive.
Me: 😶
Me: 😶
Me: 😶
Me: sir, I'm very keen on my privacy myself but without that information I can't do much for you 😬
Client: ah so you're refusing to help me?
Me: not like that, it's just very hard to lift an ip block for me when I don't know the ip address.
Client: you just don't want to help, fine.

*click*

😶

So I got an email yesterday. The balls on this fucking guy.

Programming in a tree. I usually climb up here and read, but I decided to code, and I didn't drop my laptop :D

I covered the screen with my hand because my code's ugly, and I don't want anyone to see it lol.

Random guy : Well I'm not tracked on the internet, I use private tabs.
Me : Well, I'm not sleeping with your mom, I use condoms

!rant
I've launched a small new project at https://2048.run

It will let you play 2048 (the game) over SSH or Telnet.

Connection Details
ssh play@2048.run
telnet 2048.run

Use username/password "play" to play the game.

Have fun!

Me in the digital circuits class: "Bro I just got a pick up line in mind!"
Friend: "Go on.."
Me: "Girl, are you a boolean signal 1? 'Cause you turn me on 😏"
Friend: "I can't believe I'm your friend."

Me: hey look, the time is gone!
Collegue:........?
Me:...... you don't see it? 😅😆
Collegue: no......?
Me: 4:04 🤣
Collegue: *gives death stare*
Me: 😞☹️

Haha keeping the tradition alive.

when I pull latest and all of my code is refactored

I will have a bear.🐻

(c) Creative Tim. Worth to read pips!

How to land a programming job

1. ABC (Always Be Coding) - The more you code, the better you'll get.

2. Master at least one multi-paradigm language - Some good candidates are C#, C++, Java, PHP, Python, and Ruby.

3. Re-invent the wheel - You should implement the most common data structures in your language choice.

4. Solve word problems - Pick those that test your ability to implement recursive, pattern-matching, greedy, dynamic programming, and graph problems

5. Make coding easy - At least, make it look easy.

6. Be passionate - If you don't care, then nobody else will.

7. Don't make assumptions - Ask questions if you're not sure.

non-IT friend: I still don't understand what is"hardware"

Me: it is the part of the computer that you can kick.

The wizard

at least not public void I guess..

My freelancing horror story?

I remember like it was yesterday. It was late at night and I was doing some freelancing. (You know... the good stuff...)

All of a sudden the light began flickering, it got really cold and I felt like something was watching me!

OMG! SOMETHING JUST TOUCHED MY SHOULDER! I TURN AROUND AND...

...nothing. Nobody was there.

"I really need some sleep", I think to myself and turn back to my monitor.

Wait a second, what's that?
"10%..."
"20%..."
"60%..."

Oh my god...
How could this happen to me?
Those bastards got me after all!

I just witnessed...

A WINDOWS UPDATE!!!

The end~
______________________________

I don't feel responsible for pants that need to be washed now.

A nice word to all developers who say stuff like "I know I write bad code, but what does it matter.":
Please try to think in a logical way about what this part you are about to write has to do. It is much more difficult to rewrite code, the longer you wait after you started to code.
Bad code can have big impacts on different levels.
For example financially: Bad coding style or program structure can lead to thousands or much more in losses because of nasty bugs, bad performance, expandability or maintainability.
Think about quality over quantity.

A little example: I had to work together with other coders to meet a fucking tight deadline. The last day we coded like crazy and these dudes started to apply styling changes (CSS) directly as inline styles to the HTML code, instead of taking a few minutes more to find where in the CSS files they had to make the changes.
At the end of the deadline we had more stylingbugs than before. It took us another whopping 3 hours to fix what they had done.

So next time you code: Thinking before coding is mostly faster than just straightahead coding and fixing at the end. 😉

Whatever I'm not taking it back.

Did you say security?

When Ice - Cream is life!😍

P.S: This is the best review I've ever read😂

Phone conversation between me and a client:

CLIENT: "I see it weird..."
ME: "Which browser are you using?"
CLIENT: "The one you tech guys don't like"
ME: "Internet Explorer, isn't it?"
CLIENT: "Yeah, I'll switch to Firefox then."

I made a discord chat for anyone that wants to just chill: https://discord.gg/TzVmkuJ

Lmao

Oh no!

Tech support to my friend:

Friend: Root my phone!
Me: why
Friend: play store is not working
Me: why do u want to root for that?
Friend: is there any other option?
Me: give me ur phone

After 20 sec ...
Me: Sign in to ur Google account 😐😐

I just discovered ctrl+r in the Linux terminal.

Mother of god this fucker speeds up my workflow!

A massive amount of kudos to the person who made this 😍

Never be afraid to ask questions and look stupid.
Those who ask questions become smarter.
Those who don't - remain stupid.

Why does bit(128) in PostgreSQL take up 21 bytes of storage?

"hey there is this bug, could you fix it?"
me: sure whats the bug?
*explains the bug*

me:... thats.... thats your feature request from last week

!rant.

Most QAs are dumb beasts, unable to think clearly or rationally, lazy parasites that suck the lifeblood out of a project.

Except this one guy I work with. He blackmailed the CTO to move, and landed himself a junior dev job.

He joined my team a few months ago.
"Right" says I "forget the crap you've learned so far. Here's a list of algorithm books from Amazon. Order them and read them. There'll be a test at the end."

He did. He is now reviewing lead dev work and merrily trolling their poorly performing work. Speaking to them in Big O (and so confusing the crap out of them) and earning stars at every turn.

I'd like to think I had a hand but all the effort was his.

ARE YOU FUCKING KIDDING ME. I SPEND HOURS INVESTIGATING INCOMING & OUTGOING DATA. I CHECKED ALL THE CODE, I EVEN TEAMVIEWED A CUSTOMER WHICH WAS HAVING SOME ISSUES WITH MY APP.

TURNS OUT I FORGOT A FUCKING '/' IN MY FUCKING CODE. WHICH MEANS THE HOLE GODDAMN API URL MAKES NO SENSE.

WHY THE FUCK DO I ALWAYS OVERCOMPLICATE SHIT LIKE THIS.

FUCK