> european woke bureaucratic bullshit

This may have been an attempt at rage-bait, but putting woke and bureaucracy next to each other makes it actually hilarious.

I used to hang out there too. However, describing me as 'fine' would require a lengthy debate over definitions.

It would be marvelous if they used a drawing of a spider.

https://27bslash6.com/overdue.html

But in search results, you only find the sites that game the system to maximize their profits, while millions of other well-meaning sites get little to no traffic, and eventually people lose interest in maintaining an online presence. They move toward big silos like Instagram, platforms that just use their content to attract more ads.

Ads do break the internet, or let's say, fundamentally change the model of how it works to the detriment of most people

That's why we had (and for that matter still have) webrings.

I usually ask Gemini to review the spec as well. Sometimes it catches things I missed even after going through a few times.

This might be the "Steve, Don't Eat It!" version of the xkcd workflow comic.

Whatever you ship, steve will eat, and some steves will develop an addiction.

I don't agree with your first point. We are surely writing less code, and it will keep getting less and less. At some point it will reduce to a single run function that will make the universe and everything work and it will be called via a button, and that will be the modern definition of writing code: Click the button. Not a lot of keys with weird alphabet thingies on them.

You are however right on your second point because I'm damn good at clicking buttons.

IMHO the best way is to let a SOTA model have a look at bunch of random samples and write you tools to analyze those.

I think, no model, SOTA or not, has neither the context nor the attention to be able to do anything meaningful with huge amount of logs.

Big part of these differences may be the system prompts and/or the harness.

You don't need a whole server to tell agents that, I think you can just write a skill file or two and be done with it.

That would work, and is still an option. However I think this makes deployment/installation simpler (which is also why I write my MCPs in go).