djha-skin
Joined 9 years ago
Joined 9 years ago
Modern AI programming looks an awful lot like traditional product owner or product management roles.
It reinforced in my head this idea that hobby programming is entering its "sports" or "running" era.
Consider the modern jogging enthusiast. They buy Nike shoes that make it really easy to run long distances, specialized clothing, fancy water bottles. They find spots to drive to and park at before getting out and running downhill for a few miles, getting picked up at the bottom by one of their friends. Stuff that makes for a great social media post.
They do the hard part of running, but curated to just the parts that they enjoy. They drive the rest of the time and when they do run, it looks nothing like the first marathon run of ancient Greece.
It sounds nice and all to talk about "I'm going to code anyway," but when I did this I found that there are always parts of the coding that I really really never did want to do and that I'm happy to just outsource to my agent like the jogger outsources getting to the top with their car. Testing, writing docs, making the readme logo. Stuff that probably wouldn't have happened without the AI but that I'm glad exists.
> We spent a lot of money finding out that a lock is more performant.
I want to hear about that journey.
> Besides, it's a btree.
I guess it's not a hash table, but I think the point of Vincent's post is still worth exploring. You and he both say that essentially a key/value store is mutexed, and the user's code runs inside that mutex. That is fascinating. Why would that be better? Clearly it is, or you wouldn't have spent the money. What controls did you put in place to ensure user code didn't blow up the performance, or did you even feel the need for such controls? Is WASM VM execution fast enough for this? Is there even a market for that? Who pays to put their code inside that mutex and why? I want to know more.