0x445442

Flour.

That was documented in the movie Office Space.

However the kernel differences between Linux and BeOS/NewOS are really part and parcel of Be/Haiku. It's like running Smalltalk in the terminal.

Yeah the social media giants cribbed Lifestreams sort of with the timeline but without the search capabilities that were a cornerstone of the paper. You can see glimpses of this metaphor elsewhere with email, rss and news readers but it would be interesting to make that the centralized metaphor of an entire system for all the system's data.

If something is task-specific (well understood) wouldn't this be a good candidate for a computer program?

Just tell the clanker to read the api documentation that should already exist. You dont need an MCP server for that.

What interactions with internal tools? If you can answer that question then the clankers can help you write a deterministic program for that same interaction and you only spend the tokens once.

MCPs are a bad idea because they encourage token burn at runtime when a deterministic program that uses the API should be used.

Of course Mario, Sammy, Jensen et al. would be for this.

I'm old enough to remember the OpenAPI spec.

I don't know if it's even OK for a cop to just randomly watch a random street corner without a specific reason to do so. If a cop was following a given person around all day every day without probable cause would this not be considered harassment? If we view the Flock Camera network as a single system is this not harassment?

This is what I've been mulling over for months. Surely there's a better, more rigorous specification format than Markdown prose that already exists in the industry and is useful to the agents. Formal Use Cases perhaps? Probably not Gherkin but maybe some other spec DSL.

I agree with this but what I've been trying to answer the last few months is if there was an optimal language for the spec. As with you, I don't think it's English Markdown, but I don't think it's Java either. I also don't think it's Gherkin, Lisp perhaps? I'm still searching.

Upper management material right there.

Result<T> { String resultCode; T data; List<String> errors; }

The Architects you're describing aren't reviewing the code and making suggestions for changes so your comparing apples and oranges. What I'm describing is more of a team lead to team members relationship.