The first time I realized I wasn't as good as I thought I was when I met the smartest dev I've ever known (to this day).

I was hired to manage his team but was just immediately floored by the sheer knowledge and skills this guy displayed.

I started to wonder why they hired outside of the team instead of promoting him when I found that he just didn't mesh well with others.

He was very blunt about everything he says. Especially when it comes to code reviews. Man, he did /not/ mince words. And, of course, everyone took this as him just being an asshole.

But being an expert asshole myself, I could tell he wasn't really trying to be one and he was just quirky. He was really good and I really liked hanging out with him. I learned A LOT of things.

Can you imagine coming into a lead position, with years of experience in the role backing your confidence and then be told that your code is bad and then, systematically, very precisely, and very clearly be told why? That shit is humbling.

But it was the good kind of humbling, you know? I really liked that I had someone who could actually teach me new things.

So we hung out a lot and later on I got to meet his daughter and wife who told me that he had slight autism which is why he talked the way he did. He simply doesn't know how to talk any other way.

I explained it to the rest of the team (after getting permission) and once they understood that they started to take his criticism more seriously. He also started to learn to be less harsh with his words.

We developed some really nice friendships and our team was becoming a little family.

Year and a half later I had to leave the company for personal reasons. But before I did I convinced our boss to get him to replace me. The team was behind him now and he easily handled it like a pro.

That was 5 years ago. I moved out of the city, moved back, and got a job at another company.

Four months ago, he called me up and said he had three reasons for us to meet up.

1. He was making me god father of his new baby boy
2. That they created a new position for him at the company; VP of Engineering
and
3. He wanted to hang out

So we did and turns out he had a 4th reason; He had a nice job offer for me.

I'm telling this story now because I wanted to remind everyone of the lesson that every mainstream anime tells us:

Never underestimate the power of friendship.

She got a Mac and cheese now

Now I've seen it all!

This man explaining equals in JavaScript deserves a reward

Before you're hired:
1. A binary tree?
2. Currying?
3. Higher-order function?
4. How does event loop work?
5. What is prototype?
6. What is encapsulation?
7. Can you draw an algorithm?

After you're hired:
1. Hey, can you add auth token and login to our app?

Inspirational JavaScript

I just completed my first live soldering project...

Converted my son's mobile (dangly plush animals and music not cell phone) from using 4 X C batteries (LR14) to using an AC-DC transformer

I hardwired it at 6v and it worked, and I didn't burn myself, and I cut a little gap for the wire and it's really snug so the solder is under no tension.

I tinned the wires beforehand like I knew what I was doing and for once I didn't fuck it up!

Sorry, just had to tell someone. The wife's asleep and she just won't understand.

Is it me, or does ‘hackaton’ mean ‘come and write code for us for free’?

Arch users are literally like vegans, or guys who study the law - they can’t live normally if they don’t tell you that they use it. Just because you can install it, doesn’t make you instantly a Linux god. It’s like Kali users that they think that they’re hackers if they install it, or MacBook users that think that they are “kool kids” because they have a laptop that thousands of other people have.

Nobody. Cares.

I bought a System76 laptop. They're headquartered in the same city where I live. In the "special instructions" section of the checkout process, I put, "I'm buying this because Apple took away my escape key."

This note came today.

Pick your programming language Waifu devRant.

My new setup ✌

Best 404 page I have ever seen 😊

https://acm.illinois.edu/404

My glorious new ryzen build ❤️

Me: *Opens GitHub issue*

Maintainer: "it's a known issue"

# issue closed

Gdpr

Or: "how to screw over individuals who were to lazy to update their Website"

Accurate summary of CORS headers

First rant here!

So i just inherited this legacy application in my new job.

I started looking at the code and it just doesnt make sense!

What the fucking fuck!!

New devRant feature! Filtering by post type! This took a bit longer to get out than we had planned, but now that extra click to label a post type will be put to good use! Hate memes but love rants? Want to only see questions? Don't want to see random off-topic posts? Filter away!

We're pushing to Android now, iOS shortly, and web will be coming soon.

Developed an android app for the client. It was going great. Prototype for the initial (and static) content to show to the client was on the way. All until...

*goes back in time to when we were developing the prototype*

The asshole boss: "Wow this is good, just remove the login after the splash screen. Redirect it to the dashboard immediately."

Me: "What? Why?"

TAB: "He (the CEO of our company) said that the client doesn't need to see the login."

Me: "Well, alright." (Orders are orders, better remove it)

*A few days later, we present the prototype to the CEO. He'll be the one talking to the client. TAB isn't in this meeting.*

CEO: "Where is the login screen?"

Me: *dumbfounded and confused, in silence, and pressure rising*

The Good Boss: *whispers* "Where is the login screen? I thought I told you guys it should be there."

Me: *whispers* "TAB told us to remove it."

TGB: *Looks toward CEO* "TAB told us to remove it."

CEO: "Ugh. TAB is sick."

A little giggle. Nonetheless the meeting continued. He was displeased. I was a little guilty. The login screen's code was already there. Just couldn't show it since the app doesn't redirect there anymore.

*A discussion after the meeting*

TGB: "Why'd you guys remove the login?"

Me: "You and TAB had a meeting with the CEO the other day. After the discussion TAB went to us and told us to change it."

TGB: "But the CEO said no such thing! Anyway, let's go back to the office and straighten this out tomorrow."

*The next day, TAB was in the office*

TGB: *Chatting on messenger with me* "He is completely denying it."

Me: "WHAT?"

TGB: "He said he never told you guys anything. And he is persistent. I kept telling him it was his fault, but he denies all of it. He never approached you guys to change anything."

Me: "Well yeah. I guess we magically thought to ourselves and said, 'Hey, let's remove the login screen for fun. Let's show them less content because that's how we please our clients!' -_-"

Seriously, what kind of assholefuckery is this. This shit is a whole new level. I am so TRIGGERED.

I don't really care that the meeting didn't go as planned. Just MAN UP AND ADMIT YOUR MISTAKE YOU FILTHY SON OF A GOOSE. Never listening to this asshole again. Thought he could be trusted. I will always ask my good boss next time.

As a freelancer I get side requests from bigger development companies from time to time that don't have the time or capacity to deal with it themselves.

So usually the employees are pretty friendly but they do not like to read any of the documentation I send with the code. They call me up with stupid questions that are usually answered in the documentation.

I had sent them everything they had requested last Thursday so they called me on Friday to ask the usual stupid question. However, this time I had beforehand decided to have some fun! I told them I had to leave for the weekend and to call me back on Monday. Of course they called me during the weekend, but I didn't answer. So they called me today.

What I had done before handing it all in was I had named the methods that I wrote illogically, while stating and explaining the whole situation in the documentation extra clearly.

So I answered the call today and the first thing they did was apologize. Since I didn't answer their calls during the weekend they finally realized that the best way to go is reading the documentation instead of calling me all the time. They were freaked out at first because they thought there was something completely wrong with the code and they had to tell their client that the deadline had to be pushed back.

We are all good now :)

I worked with a good dev at one of my previous jobs, but one of his faults was that he was a bit scattered and would sometimes forget things.

The story goes that one day we had this massive bug on our web app and we had a large portion of our dev team trying to figure it out. We thought we narrowed down the issue to a very specific part of the code, but something weird happened. No matter how often we looked at the piece of code where we all knew the problem had to be, no one could see any problem with it. And there want anything close to explaining how we could be seeing the issue we were in production.

We spent hours going through this. It was driving everyone crazy. All of a sudden, my co-worker (one referenced above) gasps “oh shit.” And we’re all like, what’s up? He proceeds to tell us that he thinks he might have been testing a line of code on one of our prod servers and left it in there by accident and never committed it into the actual codebase. Just to explain this - we had a great deploy process at this company but every so often a dev would need to test something quickly on a prod machine so we’d allow it as long as they did it and removed it quickly. It was meant for being for a select few tasks that required a prod server and was just going to be a single line to test something. Bad practice, but was fine because everyone had been extremely careful with it.

Until this guy came along. After he said he thought he might have left a line change in the code on a prod server, we had to manually go in to 12 web servers and check. Eventually, we found the one that had the change and finally, the issue at hand made sense. We never thought for a second that the committed code in the git repo that we were looking at would be inaccurate.

Needless to say, he was never allowed to touch code on a prod server ever again.

CodeCaptcha - An actual fun captcha! [more details]

Presenting my research on fraud detection with Machine Learning

As a developer, sometimes you hammer away on some useless solo side project for a few weeks. Maybe a small game, a web interface for your home-built storage server, or an app to turn your living room lights on an off.

I often see these posts and graphs here about motivation, about a desire to conceive perfection. You want to create a self-hosted Spotify clone "but better", or you set out to make the best todo app for iOS ever written.

These rants and memes often highlight how you start with this incredible drive, how your code is perfectly clean when you begin. Then it all oscillates between states of panic and surprise, sweat, tears and euphoria, an end in a disillusioned stare at the tangled mess you created, to gather dust forever in some private repository.

Writing a physics engine from scratch was harder than you expected. You needed a lot of ugly code to get your admin panel working in Safari. Some other shiny idea came along, and you decided to bite, even though you feel a burning guilt about the ever growing pile of unfinished failures.

All I want to say is:

No time was lost.

This is how senior developers are born. You strengthen your brain, the calluses on your mind provide you with perseverance to solve problems. Even if (no, *especially* if) you gave up on your project.

Eventually, giving up is good, it's a sign of wisdom an flexibility to focus on the broader domain again.

One of the things I love about failures is how varied they tend to be, how they force you to start seeing overarching patterns.

You don't notice the things you take back from your failures, they slip back sticking to you, undetected.

You get intuitions for strengths and weaknesses in patterns. Whenever you're matching two sparse ordered indexed lists, there's this corner of your brain lighting up on how to do it efficiently. You realize it's not the ORMs which suck, it's the fundamental object-relational impedance mismatch existing in all languages which causes problems, and you feel your fingers tingling whenever you encounter its effects in the future, ready to dive in ever so slightly deeper.

You notice you can suddenly solve completely abstract data problems using the pathfinding logic from your failed game. You realize you can use vector calculations from your physics engine to compare similarities in psychological behavior. You never understood trigonometry in high school, but while building a a deficient robotic Arduino abomination it suddenly started making sense.

You're building intuitions, continuously. These intuitions are grooves which become deeper each time you encounter fundamental patterns. The more variation in environments and topics you expose yourself to, the more permanent these associations become.

Failure is inconsequential, failure even deserves respect, failure builds intuition about patterns. Every single epiphany about similarity in patterns is an incredible victory.

Please, for the love of code...

Start and fail as many projects as you can.

TeamWork 1 week before release de projet

Guys i dont know why but all the projet is fuckup in Git ...

Me: where is your firts commit of all these shit ?

He: just there

Me : git reset eb23ae --hard && git push origin HEAD --force

Me: now you sit there and you play with your pencil ! 😡😠

Thx

Mid handover - my Gmail (GApps) access stops working.

FUDGE NUTS...

Attempting to run a Docker (ECS) deploy from AWS.

ERROR
User: arn:aws:iam::XXXYYYZZZ:user/foobar@screwed.com is not authorized to perform: ecr:DescribeRepositories on resource: *

Hilarious.

Have any of you ever feel like chocking your client to death

When the machine is too kind..

I can't believe that something I threw together in an afternoon to make my work flow better turned into something people actually use! People are opening issues and suggesting things. Never thought it would get over 2.5k downloads! 😮