It looks pretty :)

Everyone has different requirements and experiences. I switched to Moniker about 4 or 5 years ago and have about a dozen domains there. Never any issues, and a reasonable system.

This reminds me, a couple of months ago I made my Z80 assembler public on GitHub [1] but never mentioned it anywhere.

It has the usual opcodes and directives, includes, relocation data etc, with a couple of other helpful output files alongside the expected binary one.

Because the driver for it was coding on the ZX Spectrum it will also create tap files with a BASIC loader and loading screen support. And it has a not very featuresome sprite editor built in for the Spectrum screen and attributes. Oh, and a PNG-to-SCR conversion process for loading screens that does a bit of work to show problem areas (as heatmaps).

It's only actually been used by myself and one other person so there may be a few hiccups, but it WOMM :)

[1] https://github.com/kcartlidge/GoZ80

> That is so sad and even somewhat shocking.

It would be if it were a meaningful comparison, but it isn't. The comparison shouldn't be about the GDP per capita etc, but the life that gets you in the country you live - and there it fails.

There's a distinction.

- For the AI provider it is a massive money sink due to cost/revenue maths

- For the AI consumer it's not a massive money sink if you arrange things so your ongoing costs are lower than your savings

It isn't a simple yes or no overall, only per side of the fence.

With agentic stuff there's also a large amount of commits which are not code.

For instance with OpenClaw and similar, they often simulate institutional and short term memory with markdown files in folders. Other tooling that runs companies using agents as staff, for example, do the same - but also with files for inputs, outcomes, handovers etc.

All of this means a lot of extra churn as these kinds of files can be changing with every interaction not just every traditional commit point.

A 1-2-1 in this context likely refers to the 1-2-1 sessions some leads/managers have on a regular basis with each of their reports. One on one catch-ups on how they're doing.

Yes, that's what I said, but there's no "2" in there. It's "one to one", not "one two one"

As we're sharing pipelines:

- I write in Markdown files using VS Code and a custom syntax highlighter

- A custom C# tool stitches it together (with YAML metadata)

- It generates reports on chapters, dialogue, character presence etc

- It uses custom code to generate an EPUB (v2)

- It uses custom code to generate a DOCX (validated)

- It uses custom code to generate a PDF (print or with interactive links)

Works great and gives perfect results in seconds (beats Vellum, which I quite like). The only drawback is the yak shaving involved in my totally stand-alone solution leads to more time tinkering than writing.

> syntax highlighter

This was critical for me, but I didn't see an easy way for Markdown to bring it to my Linux+Emacs home, so I went with Org-mode.

Custom Go code parses the Org-mode syntax into HTML, WeasyPrint turns that into paginated PDF. The latter step is a bit slow, so I proofread iterative content updates in the HTML.

One of my trifecta of 'perfect' DOS software: DataEase 4.53, WordPerfect 4.2, and TopSpeed Modula-2. Given the restrictions of the day, all three were incredible.

I'm a fair bit lower than some others as I only use it outside of work hours on my own small projects, but my Cursor account shows (for a random recent date) 12,184,233 tokens in a day. That day feels pretty representative.

That's with 86 interactions spread intermittently over a couple of hours so if I did a full working day like that I'd be looking at maybe 40 to 50 million.

My employer is paying for it, so I'm cost insensitive, and this is mostly with Claude / Opus 4.7 (which consumes a lot of tokens?).