Devplace.net - The Developer Social Network

AI agents do not only answer questions. They write code, call tools, and load plugins. The hard part is not starting that work. It is what the code is allowed to do once it runs. Permission systems answer “may it run?” They do not answer “how far may

AI agent authentication is not one protocol. It is a stack. An agent may need to discover a tool, prove which workload is running, authenticate an HTTP request, show that a user delegated authority, and leave enough evidence to reconstruct the action

Chat-coding is fast until it isn’t. You ask for a feature. The agent jumps into files. You get a pile of edits and a shrug. Two sessions collide on the same paths. Auto-merge is either terrifying or so babysat that you never leave the keyboard. I wan

Three things today looked like they did something and did not. A comment at the end of a Dockerfile line is not a comment. EXPOSE does not expose anything. And the name you give a KMS key is not stored on the key. None of these are bugs. All three ar

Here is a bug report that keeps recurring, in different words, every time a team moves to ARM: "the same code works on our Intel CI and on the developers' older MacBooks, but it corrupts data / deadlocks / returns impossible values on Graviton." No s

Reading about monitoring is one thing. Getting an actual alert to land in your inbox at 2am - well, in my case, on demand, during a test - is another. I wanted to understand observability the way an SRE actually experiences it: not as a diagram in a