canterburry

I'm sorry, but this blog post is written as if the described functionality should obviously be available and supported by the Internet and companies who expose their data.

I agree it would be neat.

But, when did we conclude this "should" be possible and thus warrant such a whiny post?

This is an automated form of violating my 1st amendment rights.

Very impressive new format. 10,000 years...wow. That's great.

Now, can someone please help me get some data of this Iomega ZIPdrive disc?

I wonder if the incident root cause analysis will point to vibe coding?

Finally...a dedicated app to bitch at people.

I vibe coded for months but switched to spec driven development in the last 6 months

I'm also old enough to have started my career learning the rational unified process and then progressed through XP, agile, scrum etc

My process is I spend 2-3 hours writing a "spec" focusing on acceptance criteria and then by the end of the day I have a working, tested next version of a feature that I push to production.

I don't see how using a spec has made me less agile. My iteration takes 8 hours.

However, I see tons of useless specs. A spec is not a prompt. It's an actual definition of how to tell if something is behaving as intended or not.

People are notoriously bad at thinking about correctness in each scenario which is why vibe coding is so big.

People defer thinking about what correct and incorrect actually looks like for a whole wide scope of scenarios and instead choose to discover through trial and error.

I get 20x ROI on well defined, comprehensive, end to end acceptance tests that the AI can run. They fix everything from big picture functionality to minor logic errors.

Could someone relate KDE to PopOS or Ubuntu for me?

I've been on Ubuntu and PopOS for the last 15 years.

Like...why? Why do we need to try this?

"The “Smart Agent” Trap: I tried making agents that could “figure out” what to do. They couldn’t. Be explicit."

So what about this solution is actually agentic?

Overall, it sounds like you sat down and did a proper business process analysis and automated it.

Your subagents for sure have no autonomy and are just execution steps in a classic workflow except you happen to be calling an LLM.

Does the orchestrating agent adapt the process between invocations depending on the data and does it do so in any way more complex than a simple if then branch?

I have tried all sorts of UI based workflow and orchestration tools over the last 20 years.

As someone technical, I start, I build something simple quickly but then start thinking edge cases, exception handling, alternate flows etc and suddenly all that is easier to handle in code directly.

Much of the power of these solutions is the pre made integrations into other systems, and not the flow control to someone technical. Once you realize that, you start looking for integration platforms and not workflow.

According to your stats, when is the best time to post to get noticed?

How about put it on the roadmap for v4?