I feel like I'm missing something here. Was this supposed to be a game? I just kept clicking and reading and clicking and reading. I finally gave up. If the goal is to tell a non-interactive story, I'd rather just scroll...
It's awfully literary. It reads like James Joyce attempting to convey advice about effective leadership for technical teams. In my opinion, it's an obnoxious, pretentious approach to writing about practical subjects, but I may be in the minority.
SO has always had a pretty strong stance against opinion-based questions, but this is maybe the niche they should be exploring now. Humans still have a lot to say about the "best" solution to a given problem. The whole idea of an "accepted" answer could be removed, for example, since that's what AI will already generate.
Claude is just a tool. My team members are each free to choose the text editor or IDE that they are happiest with. In the near future, I hope to be able to say the same for coding agents. I really like Claude, but I don't track Claude resources in our repos. If something better comes along, I'm betting it will be perfectly happy to parse the markdown of my existing memory files, and nothing in the repo itself will force anyone else to know that I switched.
It kind of blows my mind that the majority of Claude users have just accepted that CLAUDE.md is a tracked file that the whole team has to standardize on and share. Coding agents are the ultimate API. They conform to however you prefer to interact. Is anyone really expecting to enforce standard operating procedures with this non-deterministic black box of magic?
Yeah, this was yesterday in the web version. I only did the one run, and only for a couple of levels, so I don't think I can give you any help reproducing it.
I did a quick run on the web version. I was able to sneak attack everything on the first two levels, which felt like a bug, but I'm honestly not sure.
When I found a spear, I kind of expected to be able to throw it, but I didn't find a throw option anywhere. I think that makes the short sword better in every case, but maybe I missed something.
Overall, I love the execution. Quality retro fun with a really nice interface.
Because the goal isn't "keep this exact version of the app alive and running". The prototype is never the whole application. If your only metric is incidents, then yeah, don't ever touch the code again.
You can get a few feet closer to the moon by building a treehouse, but you still can't turn it into a spaceship.
This problem definitely predates AI coding agents, though it may be exacerbated by them. The article essentially concludes with the ancient advice of "plan to throw one away". Well sure, I also read Mythical Man Month, but how do I convince the decision-makers?
I got excited about TUIs when I was exposed to the Bubble Tea framework for Go. I'm sure that Claude has accelerated the trend, but interesting things were already happening years ago.
I think both can be true. Ideally, we should do more to address the social issues that cause people to drink and drive, but revoking licenses is still a good short-term move. We could outlaw AI policing while we work on deeper issues with law enforcement.
I've used foreign keys and unique indexes to enforce validity on even the smallest, most disposable toy applications I've ever written. These benchmarks are really interesting, but the idea that performance is the only consideration is kind of silly.
I think this is too soon to call. No one questions whether AI can build things. We question whether they can build stable things that work as expected and stay online in the long run.
I think "make a product" is the important point of disagreement here. AI can generate code that users are willing to pay for, but for how long? The debate is around the long-term impact of these short-term gains. Code _is_ a means to an end, but well-engineered code is a more reliable means than what AI currently generates. These are ends of a spectrum and we're all on it somewhere.
You ever notice how everyone who drives slower than you is a moron and everyone who drives faster than you is a maniac? Your two camps have a similar bias.
I deal with a fair amount of newline-delimited JSON in my day job, where each line in the file is a complete JSON object. I've seen this referred to as "jsonl", and it's not entirely uncommon for logs and other kinds of time-series data dumps. Do any of the popular JSON CLI tools work with this format? I didn't see any mention of it here.
I'm proposing that DST is an awkward solution to the problem. You're suggesting that we should use the awkward solution and then also stack another solution on top. Why not cut out the extra step?
Uncle Steve is the same number of hours ahead that he has always been, and that's a thing that could be looked up just as easily as finding his time zone. I think the author is greatly exaggerating the degree to which time zones solve any of the problems mentioned. Uncle Steve might be on a different sleep schedule from me, regardless of whether or not he's in a different time zone.
Days of the week definitely become interesting in a global UTC system, but noon used to literally mean "the sun is at it's highest point". I suspect that people would grumble for a year or two and then forget that another system ever existed.
Well, I'm not one of those people. I like waking up with the sun and driving to work in the daylight. The idea that DST solves anything absolutely blows my mind. If you want the ability to start your work day earlier and end it earlier, that seems like a worker protection bill that needs to be passed. DST is the kludgiest kludge that ever kludged.
Everyone acts like the electoral college was a blunder. The founding fathers studied the democracies of ancient Greece, and they made a very intentional choice to guard against unfettered democracy. You were supposed to be involved in local politics, where you could actually know and evaluate your representatives. Those representatives were supposed to make national decisions on your behalf, including choosing the president.
I'm not qualified to know who will make a good president. You probably aren't either. Pushing the process further into American Idol territory would make it worse, not better.
Is "founder" the right word for living off of savings for 8 years while trying various things? I haven't done anything more impressive, but I also don't describe myself as a founder. If someone killed me tomorrow, I'd be "murdered", not "assassinated".
Preventing the traffic from being distinguished is the whole premise. Port 23 gets blocked because everyone uses it for telnet, and everyone expects bad actors to know that. If everything moves to 433, we'll end up with a variety of routing systems and no focal point for attack. The only alternative is to disallow port filtering in core internet infrastructure.
We can either have a standard and accept that bad actors will use it against us, or we can accept the chaos that results from abandoning it.
I've only ever built something that worked by first building a couple of things that didn't. No amount of theory or specification can replace what you learn by actually building and interacting with a system. Accept that there will be a version 2.