This is the second "I built a programming language" post in a day, and if I post the one I'm building, we can have a three-day streak :D They thought AI meant personal software, but it also means personal programming languages!
In all seriousness, this is great, and why not? As the post said, what once took months now takes weeks. You can experiment and see what works. For me, I started off building a web/API framework with certain correctness built in, and kept hitting the same wall: the guarantees I wanted (structured error handling, API contracts, making invalid states unrepresentable) really belonged at the language level, not bolted onto a framework. A few Claude Code sessions later, I had a spec, then a tree-sitter implementation, then a VM/JIT... something that, given my sandwich-generation-ness, I never would have done a few months ago.
I was looking for a Slimelight reference in the article, too. The world's longest-running Goth nightclub, it used to be BYOB, which made it a cheap night out. I still have my membership card.
Beyond the chatbot's error and the legal approach they took, this bad PR could have been avoided by any manager in the chain doing the right thing by overriding things and just giving him the bereavement fare (and then fixing the bot/updating the policy).
> today's "conspiracy theory" is tomorrow's verified fact
Most popular conspiracy theories remain just that, if not provably false. Horrible events do not compute for most, and they reach for alternate answers.
> Conspiracy theories offer easy answers by casting the world as simpler and more predictable than it is. Their popularity may pose a threat to societal well-being.
> I still read a lot about technology, but at the margin I probably get more value from reading histories of institutional disasters and near-disasters, and the biographies of people who helped avoid some of those disasters.
Anyone know of a reading list or a website that collects 'institutional disasters and near-disasters'? e.g. stuff like the recent Accenture/Hertz article, breaking then saving healthcare.gov etc.
> features like ctrl+P which lets you to jump to functions rather than play with files, I didn't know any other editor which allowed this feature to be there
My rational to it is that I have enough clutter, in my house and on my hard drive, that I don't need to add to it with stacks of CDs or GBs of hard drive space. You and the Japanese should meditate on the nature of impermanence, everything in the physical world is rented so your music should be too ;)
CurrentC will not fail because of this, they will fail because they use QR codes. An old lady could probably write a check faster than most people can scan a QR code.
For me it wasn't when or how much but what. At it's worst I was taking prescription medicine ate what I thought was healthy food (whole grain bread, oat cereal) and still had heartburn every night. I am not celiac but eliminating beer, whole grain wheat, and oats got rid of my acid reflux. Wheat, especially the modern variety, is not well tolerated by humans http://news.discovery.com/human/why-you-should-probably-stop.... If you can't give up bread eat Sourdough http://cookusinterruptus.com/blog/?p=4245
For me this is a magical combination of two unpopular modes of communication. There's a reason texting/chat is so popular, people don't like email and they don't like phone calls.
Tongue firmly in cheek; but does this mean they're going to start applying design to their products? I could fill a book of examples just from Gmail (settings screen, inconsistant placement of reply button, no option to reverse converstation view).
In all seriousness, this is great, and why not? As the post said, what once took months now takes weeks. You can experiment and see what works. For me, I started off building a web/API framework with certain correctness built in, and kept hitting the same wall: the guarantees I wanted (structured error handling, API contracts, making invalid states unrepresentable) really belonged at the language level, not bolted onto a framework. A few Claude Code sessions later, I had a spec, then a tree-sitter implementation, then a VM/JIT... something that, given my sandwich-generation-ness, I never would have done a few months ago.