idunnololz

Banana for scale

I was told to write my idea into an article to share internally with engineers. Then someone internally reached out to post it on our company tech blog. Then it got published on the tech blog. So I guess that’s something?

It used to be pretty bad but they worked on it and made it a lot better over time.

Slightly confusing title here. A less confusing title would be “Mozilla drops support for Mercurial, moves Firefox repository to GitHub”.

Writing a shit ton of code and doing it consistently over a long period of time with the mind set of trying to get better. You still need/prefer the other stuff people mentioned here like reading books and getting good code reviews, but there isn’t really a replacement to experience and some hard work.

And you get paid for it regardless. It’s win-win :D

Hanabi

Some people like myself also just want to stay as a senior dev. Senior dev is a valid terminal position IMO. It pays a sht load already so it’s not like I need way more money. If you’re goal is to literally maximize money and nothing else then yeah the obvious route is to transition to EM. But I would be miserable if I don’t get to write code at my job so I’m sacrificing a bit of money for way more happiness and fulfillment on the job.

I misread disk as dick

You can always solve a problem by adding more layers of abstraction. Good software design isn’t to add more layers of abstractions, it’s to solve problems with the minimum amount of abstractions necessary while still having maintainable, scalable code.

There are benefits to abstraction but they also have downsides. They can complicate code and make code harder to read.

I’m still using the ol’ GDP XD (the first version)

I used to play Hanabi with a large group. We would have like 3 games going at once. Great game. We started getting extremely meta with it and how we hinted.