Sure. You’ll notice no libraries, no CI, no issue tracker, written in C, no landing page, no dashboard.

So much of the discussion here is about professional practice around software. You can become an expert in this stuff without actually ever learning to write code. We need to remember that most of these tools are a cost that only benefits for managing collaboration between teams. The smaller the team the less stuff you need.

I also have insights from reading his C style but they may be of less interest.

I think it’s also impressive that he identifies a big and interesting problem to go after that’s usually impactful.