Changing the native browser scrollbar should warrant the death penalty.

Do not make it narrower. Do not make the colors blend with the background. Do not hijack it its functionality. Do not minimize it until I hover.

I am so fucking tired of websites that think they are in charge of my browsing "experience" and hide or otherwise marginalize the single most useful part of the page's UI.

Yesterday my tests caught more typos in copy/paste test cases than in actual logic.

'twas was a decent day.

Sprint 0: This design is the appropriate amount of engineering abstraction.

Sprint 2: This is over-engineered, too much work

Sprint 5: This is under-engineered, too many edge cases

Sprint 10: This is over-engineered, component Foo could be replaced by a bash script

Sprint 42: Foo is now the cornerstone of half our business logic

Our #bigtech repo is like 19 billion LOC so how am I the first one to try to do simpleThing with obviouslyRelatedThing?

My search foo yields nothing and I fear its not supported yet.

fml

I work so hard to name things well and yet last year's code is always full of esoteric and misleading nonsense.

Recently briefed a manager that we need to adjust Q2 plans to address the institutional knowledge lost during layoffs.

Yes, I know, write documentation, etc. This is reality, all our shit ain't documented.

me: I will major in CS so I can work with computers, not people

narrator: But little did he know...

21 lines of business logic (including whitespace and comments)

9 lines of build config

386 lines of tests (and tests for the tests)

For a software developer, I don't spend as much time in front of an IDE as I'd like.

Fuck me why do my unit tests pass with garbage input.

I can't go into a long weekend with this shit in my head rent free.

In the spirit of Valentine's Day, here is an exhaustive list of things I love about JavaScript:

POV: You fixed a hairy bug at a FAANG as a:

L3: "You're a technical wizard!"
L4: "Good job."
L5: "Why did you allow this into your team's code base?"
L6: "Why didn't you delegate that?"

Effective 1:1s are perhaps the most important soft skill that no one teaches you.

The HR onboarding section for 1:1s is only chapter one. But your manager won't teach you, your skip level won't teach you, and your mentor won't teach you. At best one of them even has an effective 1:1 skill set.

90% of 1:1s become operations: What went wrong this week and what needs to happen next week. Basically a private standup.

You attend 1:1s all year and yet somehow your manager doesn't know the difficulties you overcame, what you'd like to change, or how you're pushing yourself to grow. Then you get re-orged to a new manager.

If like to meet someone with effective 1:1s *and* low job satisfaction.

We're digital plumbers.

90% of this job is figuring out what thing to connect to what thing and then figuring out how to connect them.

Writing the code that goes in-between both ends of the pipe is easy if not trivial 90% of the time.

Meaningful change in this industry is centered around endpoints: contracts, deployments, etc. Nobody needs yet another way to organize and import their leftpad().