Dev: Breaks unit tests

Same dev: Merges it to master anyway

Same fucking dev: Can't merge to master coz CI is screaming at you? Merge locally and FORCE push.

Me: Hi, I'm blocked. I can't merge to master coz of this failing test, can we get on a quick call and figure this out?

Same fucking fuckface dev: *after 3 fucking days* Yeah, I don't know why it's failing.. the results seem to be inconsistent..

Jesus Christ. I am so close to leaving this side-project because of the frequent shit I have to go through with this fucking idiot.

God I wish I didn't need the money.

Saw this in a facebook dev group and wonder why I never thought of this before xD

We had a client visit our PH office to "hang out" and see the progress in this educational type game we were building for their private school (apparently, it's the one that Obama's kids went to).

Manager oversold the progress and actually guaranteed some features that we were still working on and estimated to finish in the next 3 sprints (2 week intervals).

Client was due to be in the office in 2 days.

PM pushes back and says we need to manage client expectations properly.

CEO got wind and sat the dev team down. Dev lead, two seniors, and junior me. He sat us down and asked us what we think.

Lead says we can do it.

Now to be fair, I know this guy to be very competent and an INCREDIBLE programmer. He is the person I consider to be the first real mentor I ever had but I really thought we were fucked here.

Next day and half was hell--for me, at least and I really couldn't see how this was all possible.

But then the fucker came through. This beautiful, majestic meganerd and the two other guys shat out 6 weeks of code in ~30 hours.

And the crazy part was it was all working. Bugs were caught in the next few days for sure, but the demo went flawlessly.

I never doubted this guy again.

Years later, I'd meet up with him and would talk fondly about those days and all he could say was "I don't really remember". He remembers the project and that we had a demo but he couldn't remember anything around those days.

Two of the most stressful days of my life and to him it was a fucking Wednesday. What a fucking champ.

People who say "hi" on slack and then take 50 years to say what they actually want to say.

People who sit on the table beside yours to play games on their phones.

People who call you dad.

People.

1. Find a function: getDayDiff(d1, d2)
2. d1 and d2 are momentjs dates.
3. See that function performs complex ancient math rituals and then returns an integer
4. Try to rewrite function, return d2.diff(d1, 'days')
5. Should be OK right? Run tests
6. Whole module melts down. WTF?!

Turns out the math performed returned the difference + 1 because it included the current day which moment's diff() function does not (out of the box).

Processes that depended on this function then uses the result like this:

const diff = getDayDiff(d1, d2)
if (diff-1 == should_match) { /* more fun logic */ }

$ git checkout .
$ run-shutdown-script-because-fuck-you

I fucking hate the fact that this group I'm side-hustling for gives maintainer access to every shitty dev they have.

Dev pushes four commits directly to master branch. Each time, pipeline fails on unit tests.

Shithead ignores failed tests and manually deploys to stage anyway.

Fuckface then declares (in group chat) that her "fix" works on stage and proceeds to merge to RC branch without updating the fucking unit test.

Pipeline fails (of course) and remains unfixed for the last EIGHT FUCKING HOURS.

This is what I woke up to at 6-fucking-AM in the god-damn morning.

*insert multiple expletives and insinuation of mother's excessive girth by comparing waistline to equator

Oh you'll love this. A master password to access any user.

Something like:
const masterpassword = <dayABCyearXYZ>
if (password == dbpassword || password == masterpassword) { // allow access }

The best part is this code is available to our clients. They can literally see how this "master password" is generated. And they don't want me to remove it because it's being used by testers.

Not sure if this has been asked before but I would love to get some book recommendations, particularly about tech.

Though other genres that you think might be interesting are welcome.

This guy I know applied for a senior position at a company I used to do freelance for. He walked in while I was spending the day there to work on our project.

We used to work in the same company and I knew that this guy doesn't know shit. He's the type that would foam in the mouth while bullshitting his way through any sort of discussion.

Anyway, they had him set up on a computer a few tables from me to complete some coding exercises--real simple stuff just to see how he would approach some common problems.

There was no time limit set but the tests shouldn't have taken him more than an hour.

He sat there for SIX HOURS.

At this point, I went out for a smoke, came back 5 minutes later, and found that he wasn't there anymore.

Apparently, he just stood up and said, "Nope, can't do it" and then left the building without a word to anybody else.

We never heard of him again.

Oh, and the tests? Not a single line of code written XD

Just received an email from a client's new liaison.

He spells "going to" as "goner" and "could have" as "could of".

As if I needed more anxiety these days.

It's nice to see people posting what they've been up to during their free time.

Oh wait, did I say nice? No, fuck you and your slightly better circumstances!

I don't like coding in the dark anymore. I think I've been doing it for about 2 years but I, just now, realized it.

I never even noticed when I started doing it. I just remember that--when the sun sets and I'm still working--I think to myself "ugh, it's too dark in here".

It just seems crazy to me because I used to love the dark. Not in the broody, ooh I'm a hacker kind of way.. just that I worked better in the dark.

I used to choose afternoon or evening shifts whenever given the choice because my brain works better when it's dark out (if that even makes sense). I used to work inside conference rooms with the lights out or dimmed.

But now, I just caught myself thinking I needed a brighter light in my home office.

Huh. I think I'm getting old.

A few weeks back we ported our PHP Rest API into a couple of Go micro-services.

Incredibly _satisfying_ job.

Requests went from 20+ seconds to ~100-300ms.

There was still one bottle-neck, though, because we had to use most of the old cluster-fork of a database (because no way I'll be able to fix all that in a week).

And ooh, next we're thinking of switching to gRPC. Man, we have the best jobs.

if err != nil {
if err.Error() == sql.ErrNoRows {
return nil, err
}
return nil, err
}

found me some choice, grade A Go code here.

9:00 AM: Ahh, first day back at work.
9:05 AM: AAHHHHHHHHHHHH!!! I want my vacation back.

My favorite one was always from our tech lead when I was a junior,

"Huh, didn't know we could do that. Very cool."

It was real ego boost and something that really stayed with me.

WTH?! I just installed Windows on a high end laptop and fiber connection in under 20 minutes.

Nobody told me this is how people in first-world countries lived!!

Yeah, if my so called "friends" can just stop making me feel guilty for staying in with my son instead of going out having beers in pretentious clubs, with music blasting at a billion decibels that we can't even have a decent conversation.

If you could just stop; that would be great.

I'm sorry I have to work. I'm sorry I can't leave my 6 year old alone in the house on a school night. I'm sorry I don't have an army of maids to look after him. I'm sorry I don't have personal drivers to take him to school. I'm sorry if your family or your wife's family is so fucking rich you're basically a kept man and now bored out of your wits.

Please, just fuck off with this toxic behavior. We are not in our 20s anymore.

Thank you.

v2 production release, day 4:

0 Issues reported

*drops mic

I have the best team.

Just wanted to immortalize this moment.

Stupid stupid stupid API that returns a 204 on failed validations.

Informative docs? Hell no! Here's a few hundred long-ass field names that you need to pass as a JSON.

Doesn't work huh? Yeah, you're structure's all wrong. Some of these are grouped in vaguely named keys like "Wholesale".

Oh you need those as well? Yeah, you can see the whole structure if you try to GET an object.

Oh you need an ID to GET an object? Yeah you can just go ahead and create as many as you want. This is just a sandbox API, it's cool.

Oh that's not the point? Ahh you need the structure to be able to create one! *haha* Right, I'll get back to you on that.

* Email correspondence over 2 weeks time. I have still yet to be able to make a an actual successful request. The fucking 204 doesn't count if it doesn't actually create the resource.

Fucking fucky fuckity fuck fuck fuck.

I swear to god if I ever meet this guy in person, I will probably buy him coffee or beer and have a long talk about how to build proper REST APIs.

Because I'm nice like that.

What do you call time spent by a new dev learning a company's codebase?

Genuinely asking because, as a non-native English speaker who has to communicate with English speakers on a regular basis, I usually end up saying that a dev is still studying the code or familiarizing himself with it.

I'm not sure why it kinda feels off for me. Is there a specific term that describes this?

Sort of how technical debt tells me that it's the cost for someone being lazy with his work before.

Holy crap. I am so torn between getting a razer blade 15 and an XPS 15.

I am going for the small-but-powerful build because I keep finding myself coding on the go (with GoLang, snicker).

I was pretty happy with my Dell Inspiron 14 even though I had issues with Linux in the beginning. But my main gripe right now is how heavy it is to lug around together with it's charger--which I can't leave without anymore.

I'm looking at both laptops' 1800 USD configuration which pretty much have similar specs. And I also did some research about how each plays with Linux and they pretty much have the same (fixable) problems.

What I wanna know from the fine folks here is what their experience have been like. Cause I know I can make it work with Linux but if the total experience is just meh then I don't think they're worth the hefty price tags.

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.

Just in case people forgot that this was a thing.
https://youtu.be/miomuSGoPzI

You're welcome.

Ugh. I hate gmail threads. Especially when people just hit reply and quote the whole thread in their next email.

Going back and sifting through these threads to find relevant information is always a pain in the ass.

I like the new gmail UI. It's clean and works perfectly especially when you have keyboard shortcuts on.

But these threaded messages. Gah!

I have an uncanny ability to--in the middle of coding--open a tab on the browser and type just about anything on the search bar and go on to what I am starting to call a "link binge".

I pretty much bounce around the internet reading about random (not even useful, always) shit and end up wasting hours.

story points that equate to hours.
1 = 1 hour
2 = 1-2 hours
3 = 3-4 hours
5 = 6-8 hours
8 = Kill. Me.
13 = Now.

We had a closed beta today for a product I've worked on for the last 6 months. We've been working late nights for the last week to make sure we get all the kinks out and make sure our demo went smoothly.

After a bit of hyping via a power point presentation by my colleague, we finally start the demo and of course the login fails. Both the API and database were offline. The servers were on but we just couldn't reach the applications. My colleague stalls and I get to debugging.

We were standing in front of 50 people who were hyped-up on a product that was failing in front of them.

But after 10 minutes (felt like an hour) of hemming and hawing, the app just decides to start running again.

What in the actual fuck? Does this happen to anyone else? Coz it feels like it happens to me every time.

I've been off the PHP game for a good bit now so I'm not sure if this is an established practice.

But why in the flying fuck would someone want to use .htm in place of .php files? Especially when you already use .php on other files on the same codebase?!