32bitkid

But, I think the value of commit messages become really apparent once you (or your team) are relying on other visualizations of commit messages like `blame` and `bisect`

Tracking down the introduction of a bug with bisect and resolving to a commit whose message in “minor”, because the person in the past didn’t think this change was important enough to describe intent can quite the temporal foot-gun.

Tell me more about how everyone else in the “modern world” is the problem…

Before moving on, a quick `git reset —-hard` will get back to a clean flip

Klein tools makes combination head tools that engage both, which is fantastic if you are upgrading a bunch of outlets.

The ultimate interface _for me_ would be somewhere in between Calca (which I think has superior support for functions/graphing/logical calculations) and Soulver (which I think has better usability/readability) and a graph-based note-taking system like Obsidian/Zettlr. I'm sure somebody will say "there is a Vim plugin that'll do that" but… yea.

And

Color Maximite 1/2: http://geoffg.net/maximite.html

Are two interesting takes on modern BASIC

The difference is in their numerical notion. ~N means go to my Nth first parent. Where ^N means my Nth parent, which is really only valuable/useful on merge commits (Or more specifically octopus merges that merge more than two commits)

This is why ~ and ^ in the single form mean the same thing.

So, in one mental model of the DAG you can think of ^ as horizontal navigation (Right) and ~ as vertical (Down)

Don’t just build stuff—study stuff!

https://en.m.wikipedia.org/wiki/Mirth_Connect

  Role: Developer/Designer
  Location: Denver, CO
  Remote: Yes
  Willing to relocate: Yes
  Technologies: React, ES6, Typescript, CSS, SCSS, Go, Kotlin
  Resume: https://j.holmes.codes/resume/
  Email: [email protected]

As for myself, I've been working on a 2d-space combat game set on the surface of a Poincaré Disk as a hobby over the past few years, not sure i'll ever do anything with it for real, but it's fun.

I know that a lot of it is just my age, and I remember my father growing up used to work on/rebuild the engine on his '64 VW beetle. I think for very similar reasons: nostalgia, limited complexity, the tangibility of the "API". For me, POKEing a value in memory and seeing the screen change or a sound play is tangible. The opcodes of an 8088 are _just_ enough that I can feel like I understand it. Modern computers feel several orders of magnitude more complex and—admittedly—more powerful, but at a _cost_. I'm sure my dad thought the same about electric fuel-injected engines and the ever increasing complexity of "modern" cars.

Currently, on my work-bench in the garage is a half-completed [Micro8088](https://github.com/skiselev/micro_8088) and 8-bit ISA back-plane; still waiting for a few parts to come in. Its been a lot of fun to work on, and the intent is to get back into doing some retro-programming. (Hopefully, I have a better understanding of the underlying architecture now than I did when I spent a summer when I was 14 trying to figure out the relationship between AH/AL and AX without a concrete understanding of binary/hexadecimal math)

What intrigued me though is two fold: one, I find myself also remembering my father when I was growing up, he was not interested in computers, they were more or less just a tool to get a job done, but he loved cars. He had a VW beetle, late 50s early 60s model (though they didn’t change much) and he would tear it down, rebuild the engine, do whatever. But I mean honestly, I can’t see much difference between what he was doing then, and what I am doing now (building a home-brew Micro8088). In fact, probably for a lot of the same reasons...

There is something about that era of computing, I can hold a lot what is going on in my head and there are very few abstractions between myself and the machine. The limitations of the architecture inspire creativity and doing things “the wrong way”, but in a way you can gain a more significant understanding of the underlying system. But, part of that is just nostaligia, and I imagine if i could time travel back and have a beer with my dad over his car, he’d probably say something very similar about the lack of fuel injection computers and the simiplicity of a two stroke engine...

And secondly, and this isn’t intended to be a scoff at “millennials”, quite the opppsite actually, I wonder what the current generation will look back on as this level of “things were simpler then”-retrospection. Because I’m sure that my dad never thought that I would look back on the 8088s and z80s of my youth as a manifestation of “simplicity”. So, what am I not seeing about my present?