Instead of figuring out how to solve every bug and becoming intimately familiar with with the code, I just delegate all the work to virtual interns and I sit and wait.
I decided to write my own Forth compiler without AI assistance as a result. Side projects should be fun and for learning.
Not judging people who use these tools, I use them too, but i just have been using them less for anything I am doing for fun.
I think there is a big divide between people who just love making different tools from scratch by hand and the rest who love being able to instantly whip up a new tool in minutes AND THEN use it to create something fun.
I literally would never ever in my existence be interested in making a compiler if I had nothing to use it for. If I ever wanted to make a cool program which uses that compiler then whether the compiler came into being thanks to a wizard, my enjoyment wouldn't change a single bit.
In typical tombert fashion, when making an NES game I ended up getting much more obsessed with the tooling around the project than the core project, so when I got it to generate a Forth compiler, I fell down a rabbit hole of learning how compilers work and then feeling cheated out of the actual work.
That said, I'm not a complete luddite here; I wanted a proper comment system on my blog recently, and I don't care enough about web stuff to actually build it myself. I could have used an off the shelf thing but those usually come with a bunch of bullshit involving accounts and the like, so instead I got Codex to build one for me and deploy it and it works fine.
I like using computers to solve problems. I’m more interested in the problem being solved than the journey most of the time, though I’ve also been on some lovely journeys. Sometimes that means I write a tool all by myself. Sometimes it means I download an existing open source tool. And sometimes it means I delegate the creation to an AI model.
Are you just sitting there as if dead when using AI? I find AI work exciting, always something new to discover.
There are plenty of projects I have wanted to do that I don't because the "activation energy" is too high, and if I can get a machine to basically get past the boring crap then I can focus on the parts of the project that I think are fun.
If you look at old school development manuals for stuff like the C64 your options, to get decent performance for something you are writing it seems like the options were “forth” or “assembly”, and I find forth easier to reason about.
To answer the true essence of your question though, I wanted a forth compiler as a means to making an NES game, but after I got Codex to generate the compiler I kind of realize that what I actually wanted was the entire experience of making an NES game, including building the compiler.
Having similar experience with my experimental code generator to Rust. Every time a yet another example does not work, Claude fixes it. However, I am curious whether it would converge to a bullet-proof solution, or I have to carefully read the code and come up with proper abstractions.
I think it helps having an intermediate tree where every value is valid rust code (not just synctactically, but it compiles and runs fine) helps a lot. Like an IR for your transpiler
The site should imitate newspapers either more or less closely. In either case, first limit column height to something like 80% of the viewport to eliminate scrolling within columns. The column switch can select column width as a fraction of screen width.
More closely: when the content is too long for one set of columns, split it into multiple newspaper-style pages. The reader scrolls vertically through the newspaper pages.
Less closely: use columns arranged side-by-side in a horizontally scrollable container. The reader scrolls vertically to reach the container, then horizontally through the columns.
This is a big gripe of mine at the moment. I rarely have any confidence that I know how the thing works, or what additional things it does / does not do but which I expect.
Recent example: all API endpoints should require a bearer token. Imagine my surprise when half of them didn’t enforce this effectively, 3 days later. A bearer token would work, but also providing no bearer token would also work. Over the course of time, tests were removed / things were modified to get to the goal and say “done, boss!”
I’ll note that for this project, “don’t look at the source code” was a requirement. Things have been corrected before release, but the amount of potential foot guns is so damn high.
https://en.wikibooks.org/wiki/Write_Yourself_a_Scheme_in_48_...
https://docs.astro.build/en/guides/build-with-ai/
What a happy coincidence!
