The next rabbit hole is to start learning rust.

As long you understand the stack you’re good to go. It will help you understand why the borrow checker is like the way it is.

It depends on the project. Not all open source project uses tailwind’s revenue model, which relied on that people are reading their docs.

LLMs won’t destroy open source, but it will change the landscape. Probably not for the better though.

Amen!

I believe they want to divert all their resources into one huge Fortnite like success story. Something that can bring them a reliable recurring revenue stream.

I’ve had both installed on my machine without issues. Jumped back and forth until I decided Gnome wasn’t for me.

I prefer KDE. It works well out of the box and offers a good amount of customization. I tried gnome for a bit and didn’t like it.

What I like about Linux is that it’s easy to switch between DE. Just try out a few ones until you find something you like. I can recommend looking into Cinnamon (the DE of Mint).

2 layers of abstraction is the gold standard

Why should I want simplicity? I want to make unnecessarily complex programs to gatekeep those pesky junior programmers.

Windows pretends it’s friendly, but in reality it’s just there to sell you Copilot 365 subscription.

Anything that isn’t the bootloader is just bloat

No one is going to take IntelliJ from me. Tab completion master race!

Remember: there can’t be a woman in office because they get too emotional.

This is what’s most important. Allow for experimentation!

What works well for one team might not work well for your team. What worked well for your team 1 year ago might no longer be what you need now.

It’s easy to overestimate how much of software engineering is about coding, when in truth it’s mostly about the code you don’t write.

99% of the time it’s just a basic todo list

Have you noticed how every LinkedIn bro is talking about their vibe coding workflows, but no one is showing what they’ve made with vibe coding?

Writing “iteration” sounds absolutely perverse!

I like it to make it clear when the for loop is about iterating lists and when it’s not. For example, the iterations in Monte Carlo algorithms doesn’t correspond to items in a list.

Outside of the for loop counters i and j, short variable names are awful.

I’ve started to prefer writing it out as ”index” or ”iteration” even in for loop counters. It’s easier to read, and not much harder to type.

The FP in Java is still leagues better than whatever the C++ committee cooked up.

The OOP boilerplater is the only one with a job.