Forgejo (a gitea fork) is a better choice for FOSS, can't remember why.

"Today I learned learned"

I went helix -> vim -> emacs -> kakoune -> neovim, super interesting to see how people's experiences differ

There's always the fork network graph, but it's not exactly easy to spot which forks are good, just the ones with the most recent commits

Well they are both interoperable

I think the story is photoshop

I've done it with a new language each year in the past, but this year I decided to do it with stuff I'm very familiar with - with an added twist: I have to visualize something for each day.

So I built myself a little app/puzzle harness that serves up the sample/puzzle input and provides some boilerplate so I can just write the x-data for a new Alpine.js module for each day. Then I setup d3 and plan to visualize something for each day using it. For example, I just settled on a simple bar graph (final value of each row) for each part of day 1:

Hoping once it inevitably gets to grids and such, I can do something more interactive. Would love to have something where I can animate or manually step through each step of the solution (such as the pathfinding algorithm last year).

Excellent!

Revert doesn't just move head back, it creates reversal commits. As such, merging again can happen since the changes are present and require a merge commit

Yep, definitely wasn't expecting that 4 there

And the whole thing with running CI builds on branches not being "integrating" until merge time is so funny to me.

Like, does this person not know that you can merge master back into a feature branch, such that you are, in fact, integrating the feature branch up to date with master? And it's done... Gasp without breaking the master build for everyone else in the mean time!?!

And the parts about pair programming and knowledge sharing are easy to fix, too. Just have regularly scheduled pairing sessions with the people who need to knowledge-share.

Trunk-based suggestions always comes across to me as "I don't understand how to do feature branches/PR-based development"

It was 100% worth it for me, but I have several handhelds that I have disassembled numerous times and have proper tools, so I wasn't expecting any big trouble. I decided beforehand that I wasn't going to swap the touchpad covers or the buttons, because I think they look cheap and bad. So that simplified concerns about the touchpads being fragile and/or hard to modify.

My process was to watch extremeRate's howto before buying, and then weigh the risks as such:

• Assuming no carelessness, what's likely to break?
  • Screen
  • Trigger hinge(s)
• How much do they cost?
  • $70
  • $20 (each)

And since I can afford ~$110 it would cost if I broke both triggers and the screen, it would be sad if I broke it, but not a huge problem.

And ... I love it. I keep looking at it and just being floored that it's mine.