Found 8185 bookmarks
Newest
A Concrete Definition of an AI Agent
A Concrete Definition of an AI Agent
An AI agent pursues a goal by iteratively taking actions, evaluating progress, and deciding next steps. Useful agents must be reliable, adaptive, and accurate.
·nngroup.com·
A Concrete Definition of an AI Agent
Little hierarchies everywhere
Little hierarchies everywhere
Dave Winer, OG blogger, podcaster, developed first apps in many categories. Old enough to know better. It's even worse than it appears.
·scripting.com·
Little hierarchies everywhere
DC In The Data Center For A More Efficient Future
DC In The Data Center For A More Efficient Future
If you own a computer that’s not mobile, it’s almost certain that it will receive its power in some form from a mains wall outlet. Whether it’s 230 V at 50 Hz or 120 V at 60 Hz, w…
·hackaday.com·
DC In The Data Center For A More Efficient Future
Docker Images and Their Layers Explained
Docker Images and Their Layers Explained
To enable fast builds and efficient usage of disk space, Docker introduced the image layer model. This article is an in-depth explanation on how the layer
·dominik.info·
Docker Images and Their Layers Explained
KServe
KServe
KServe - A Kubernetes-native platform for serving machine learning models with standardized protocols for both predictive and generative AI. Scale to zero, GPU acceleration, and multi-framework support.
·kserve.github.io·
KServe
How to Evaluate Your Architecture
How to Evaluate Your Architecture
Evaluating the architecture of a system can be a very complicated process, with a lot of different possibilities for tools and techniques. In this video, we describe a mental model for evaluating architecture that helps us make sense and make the right decisions.
·mozaicworks.com·
How to Evaluate Your Architecture
The Patching Paradox Driving Most Breaches
The Patching Paradox Driving Most Breaches
More than half of breaches occur after fixes are available, revealing an execution gap as delayed patching turns known vulnerabilities into ongoing enterprise risk.
·linuxinsider.com·
The Patching Paradox Driving Most Breaches
STOMP
STOMP
The Simple Text Oriented Messaging Protocol
·stomp.github.io·
STOMP
Live Verify
Live Verify
·live-verify.github.io·
Live Verify
What Was I Reading Last? In Three Not-So-Easy Pieces
What Was I Reading Last? In Three Not-So-Easy Pieces
Syncing reading progress across devices sounds simple until you try it. Discovery, sync, and conflict resolution — with and without a cloud.
·tech.stonecharioteer.com·
What Was I Reading Last? In Three Not-So-Easy Pieces
In the team of the future, roles are verbs, not nouns
In the team of the future, roles are verbs, not nouns
If someone asked me to set up a team in charge of software documentation, I would not hire for specific roles or cookie-cut job descriptions. Professions tied to knowledge buckets are bound to shrink or disappear. Instead, I would hire people that could move freely between four quadrants, each defined by the proximity to a focus pole and its skills. The poles in this team setup would be the following: Product Vision, Knowledge Design, Engineering Depth, and Delivery Strategy.
·passo.uno·
In the team of the future, roles are verbs, not nouns
Delegation as Data: Applying Cedar Policies to OpenClaw Subagents
Delegation as Data: Applying Cedar Policies to OpenClaw Subagents
Intra-domain delegation enables an agent to grant constrained authority to subagents without expanding the system’s trust boundary. In the OpenClaw + Cedar demo, delegation is modeled as data and enforced by a stable policy set, preserving policy integrity while allowing dynamic scoping of power.
·windley.com·
Delegation as Data: Applying Cedar Policies to OpenClaw Subagents
Write your APIs like you write a movie
Write your APIs like you write a movie
If you have built APIs, then by now, you are already familiar with the practices of how we typically build APIs:
·mohammad-shaddad.com·
Write your APIs like you write a movie
Implementing Amazon Dynamo in Elixir
Implementing Amazon Dynamo in Elixir
For the next paper in my Paper Implementation series, I picked the Dynamo 2007 paper by Amazon. I had a really good time with this one. Large scale distributed systems always fascinate me , how do you handle that much data, across that many machines, and keep it working when things inevitably break? The Dynamo paper has a clear answer, and it keeps repeating it in case you miss it: eventual consistency.
·jiteshcodes.com·
Implementing Amazon Dynamo in Elixir