Definitely interesting, I hope all of this standardizes some day in the future, and if it's your protocol, great.
I have been following AlignTrue https://aligntrue.ai/docs/about but I think I like more your way of doing accountability and acting on thinking process instead of being passive. Apart from the fact that your way is a down-to-earth, more practical approach.
Great showcase live demo, however I would have liked a more in-depth showcasing of AAP and AIP even in this situation of multi-agent interactions, to understand the full picture better. Or simply perhaps prepare another showcase for the AAP and AIP. Just my two cents.
PS. I'm the creator of LynxPrompt, which honestly falls very short for this cases we're treating today, but with that I'm saying that I keep engaged on the topic trust/accountability, on how to organize agents and guide them properly without supervision.
I prepare custom AGENTS.md with the help of https://lynxprompt.com (Disclaimer: I'm the dev)
The more time you spend making guidelines and guardrails, the more success the LLM has at acing your prompt. There I created a wizard to get it right from the beginning, simplifying and "guiding" you into thinking what you want to achieve.
I produced https://lynxprompt.com as an IDE/tool-agnostic AI config rules generator & catalog, via CLI & WebUI. There is a lot of love (and $$$) put in the Wizard generator, you can check it both via CLI or WebUI.
I've got some users and the stuff I can do each time I start doing vibecoding is astounding. Obviously 50% the work is just fixing what the AI didn't understood or imagined too much, but having a good AGENTS.md is key (and patience from me) - so that's why I'm buidling LynxPrompt indeed, for having an easy way to own a good AGENTS.md file for my next projects... and hopefully you too.
We’ve been “losing skills” to better tools forever, and it’s usually been a net positive. Nobody hand-writes a sorting algorithm in production to “stay sharp”, most of us don’t do long division because calculators exist, and plenty of great engineers today couldn’t write assembly (or even manage memory in C) comfortably. That didn’t make the industry worse; it let us build bigger things by working at higher abstraction.
LLM-assisted coding feels like the next step in that same pattern. The difference is that this abstraction layer can confidently make stuff up: hallucinated APIs, wrong assumptions, edge cases it didn’t consider. So the work doesn’t disappear, it shifts. The valuable skill becomes guiding it: specifying the task clearly, constraining the solution, reviewing diffs, insisting on tests, and catching the “looks right but isn’t” failures. In practice it’s like having a very fast junior dev who never gets tired and also never says “I’m not sure”.
That’s why I don’t buy the extremes on either side. It’s not magic, and it’s not useless. Used carelessly, it absolutely accelerates tech debt and produces bloated code. Used well, it can take a lot of the grunt work off your plate (refactors, migrations, scaffolding tests, boilerplate, docs drafts) and leave you with more time for the parts that actually require engineering judgement.
On the “will it make me dumber” worry: only if you outsource judgement. If you treat it as a typing/lookup/refactor accelerator and keep ownership of architecture, correctness, and debugging, you’re not getting worse—you’re just moving your attention up the stack. And if you really care about maintaining raw coding chops, you can do what we already do in other areas: occasionally turn it off and do reps, the same way people still practice mental math even though Excel exists.
Privacy/ethics are real concerns, but that’s a separate discussion; there are mitigations and alternatives depending on your threat model.
At the end of the day, the job title might stay “software engineer”, but the day-to-day shifts toward “AI guide + reviewer + responsible adult.” And like every other tooling jump, you don’t have to love it, but you probably do have to learn it—because you’ll end up maintaining and reviewing AI-shaped code either way.
Basically, I think the author hit just in the point.
Hey. I'm trying to arrange views in multi-monitor setups, but when I tried to arrange some windows on a DisplayLink screen, it literally makes them disappear, unable to open/restore them until I force-close them.
It's also not showing apps in other spaces, which I would like to be shown. Mac's default Cmd+Tab does that.
Spanish here. I've been to many homes occupied by squatters due to the nature of my voluntary service for quite some years.
The people you seem to be describing just applies for a tiny proportion of the actual landscape of squatting in Spain. So your sentence is partly true, but nowadays as the situation becomes chronic, most people just do it because it is convenient for them
Believe me when I say that I've been tasked to helping "homeless" people and once I got closer, some of them were begging in the streets, making +300€ on a good day. I was speechless the first day that I heard about it.
I have sciatica and lumbar pain. After many years of search through every major chair designer, I now work with something that eases my pain quite a lot: A 40$ 0-gravity chair. Yes, it seems unbelievable but it has been the best purchase for me in the last 10 years.
I don't use any Meta service for the same reason. But I was using Telegram because of a perceived better treatment of chat history and compatibility with people around me using it. But I didn't know the last actions from Pavel Durov... which seem totally in line with Meta's wrong-behavior.
Sorry, but at least in my smartphone, I can understand better the unprocessed audio showcased down in the Web page, than the noise-suppresed audio. How is that?
So sorry about your family. I also started personally getting psychiatric care after all this happened, and continuing now. The situation is so complex, but definitely it should have been managed better overall. I'm no expert so can't comment.