I had this recommended for me, but the risk of empty nose syndrome scared the shit out of me.

Do you really discard errors this often? I would say almost all of my Results get propagated to the caller via ? and handled in one place near the start of the stack.

2000s babies are starting to feel old?

Shit…

The cargo culting is always going to happen and turn into elitism. But it stems from real advantages of specific technologies, and sometimes you should actually consider that the tech you’re using is irresponsible when better alternatives exist.

Android users aren’t having kids. /s

the Rust folks wouldn’t care about the in-memory representation as long as the compilation is on point.

Well I can’t speak for everyone, but Rust is very intentional about supporting things like repr(C). At least some of us care a lot.

Nah these are the actual integer representations. Otherwise you would have Some(None) == Some(Some(None)) which is way too Javascripty for Rust folks.

deleted by creator

OK but what is “Git Patch Stacks”? It seems like I’m missing something fundamental that was never actually explained in this post.

EDIT: Oh hey I found it after reading a different blog post on that site: https://github.com/uptech/git-ps-rs

The post is also super rambling in the middle section.

I have to assume that this is something similar to Mercurial’s MQ plugin or Stacked Git (stgit), which allow you to manage revisions as a stack of diffs.

I personally enjoy using stgit, and it fits just fine into the world of feature branches and PRs.

This part scared me:

In a Stacked Branch workflow, you are creating branches for each of your atomic commits, and then you’re defining the relationships between those branches so it can formally store a directed acyclic graph of those relationships.

Why do you want to make a separate branch for every commit? That sounds like a nightmare, and it’s definitely not the intended workflow for git.

takes over their tasks

Every time I help bag this man is thankful. It’s pretty common that a well-staffed grocery store (like Costco) will have dedicated baggers.

In any case, it should be the store to blame, because they don’t open more cash registers or hire more people and let customers in line

Agreed. I wish I had a better grocery so close to me.

You’ve reduced the issue in a way that’s not a faithful representation.

I mean… they carried the bags out of the store by themselves.

Ok. This was a Kroger. And honestly I’m just annoyed that this person just stood there doing nothing while the cashier fumbled his way through bagging groceries. It’s incredibly easy to just help.

At Kroger there’s room at the end of the counter for bags, after scanning, goods are passed to the bagger. Very simple.

That’s how it works. It’s doesn’t matter once you have your groceries unloaded onto a conveyor.

Do challenging projects. Read code from better engineers. Work with better engineers. Try new languages that actually solve technical problems instead of just having nice syntax. Contribute to open source projects that you use. Actually read the manuals that come with your tools. Notice when it’s taking you a long time to do something and reflect on it to find a faster way. Constantly tweak your workflow to be more productive.

And the most important of all:

Get a split ergomech keyboard.

All of my top picks have been mentioned, but I have a few more that stand out from recent memory.

Hijack (Apple TV+) was one of my favorite thrillers, perfectly wrapped up in one season. Multiple jaw-dropping moments. Very hard to put down.

Perry Mason (HBO) is an enigmatic murder mystery that will keep you guessing. Characters are written with depth. Feels realistic for the time period.

Watchmen (HBO) is a faithful continuation of the comic book that, like the book, uses superheros to explore ethical and social issues instead of drawing clean lines between good and evil. Also responsible for teaching many Americans about the Tulsa Massacre.

Yea. I was using bottom until I saw this and did a quick side-by-side comparison (nix-shell -p btop, I use NixOS BTW). btop’s UI is just so much better.

So there’s no LSP function to just show all of the multi-methods that accept a specific type? That’s a pretty serious tooling limitation.

Maybe Julia sounds better in theory than in practice, if the tooling still isn’t ready for production use.

What do you find challenging about multiple dispatch? I don’t use Julia for my job, so I can’t say I’ve had enough experience to have a strong opinion. MD seems like a valuable tool though.