Explore Articles By Topic Tags
Filter engineering reports by specific technology stack, protocols, performance metrics, and security frameworks.
Explore Articles By Topic Tags 61 Tags
Most Popular Technology Tags
I attacked my own npm package before launching it. It let the proposer approve their own writes
My library exists so a human approves an LLM's UPDATE before it runs. It never checked that the approver was somebody other than the proposer — and wrote \"approved\" into the audit trail anyway.
The Tragedy of the Clean-Handed Auditor
\"I could save them if they'd only listen...\" Hey, you. Yeah, you: the compliance or governance...
I Gave My Agent One Signed Permission It Couldn’t Mint Itself
Evidence status. The supervised operator run completed on 2026-08-09. An operator-signed job...
What Is the Circuit Breaker Pattern? A Practical Guide
What Is the Circuit Breaker Pattern? A Practical Guide for Developers Imagine your...
Real-Life Refactoring Example: ~3x Less Code to Read
There is a popular idea that refactoring is making code shorter. It is not entirely wrong....
Protecting Microservices: Implementing End-to-End Encryption Across REST APIs
End-to-end encryption across REST APIs is the difference between a microservices architecture that...
Build an MCP Server in Go (Part 1): Designing a diagnostic-grade Kubernetes client
This post designs the Kubernetes client. The next post wraps it as an MCP server and wires it to an...
Building Sluice: QoS-Aware Capacity Governance for Self-Hosted LLM Inference
📦 Project: https://github.com/VampiricCyborg/sluice 1. The Problem: When Capacity Becomes...
One GPU, four ways to share it: ten scenarios, and the headline finding I had to retract
I measured every GPU sharing mode across ten scenarios, published a headline finding that duplicate models are nearly free on unified memory, then failed to replicate it and retracted it. Here is what the controlled replication showed and how the original measurement fooled me.
I Thought I'd Lost the Plot. I Was Writing It.
I Thought I'd Lost the Plot. I Was Writing It. I set out to build autonomous...
The Write Policy Is the Hard Part: Promotion Pipelines for Agent Memory
Storing agent memory is easy. Deciding what earns a permanent write, and keeping the write-path alive through RBAC and network policy, is the real work.
I Changed How I Think About AI Memory
I Changed How I Think About AI Memory When I first built Lean AI Memory, I focused too...
I Thought I'd Lost the Plot. I Was Writing It.
I Thought I'd Lost the Plot. I Was Writing It. I set out to build autonomous...
The Write Policy Is the Hard Part: Promotion Pipelines for Agent Memory
Storing agent memory is easy. Deciding what earns a permanent write, and keeping the write-path alive through RBAC and network policy, is the real work.
I Changed How I Think About AI Memory
I Changed How I Think About AI Memory When I first built Lean AI Memory, I focused too...
Build an MCP Server in Go (Part 1): Designing a diagnostic-grade Kubernetes client
This post designs the Kubernetes client. The next post wraps it as an MCP server and wires it to an...
I Gave My Agent One Signed Permission It Couldn’t Mint Itself
Evidence status. The supervised operator run completed on 2026-08-09. An operator-signed job...
One GPU, four ways to share it: ten scenarios, and the headline finding I had to retract
I measured every GPU sharing mode across ten scenarios, published a headline finding that duplicate models are nearly free on unified memory, then failed to replicate it and retracted it. Here is what the controlled replication showed and how the original measurement fooled me.
I attacked my own npm package before launching it. It let the proposer approve their own writes
My library exists so a human approves an LLM's UPDATE before it runs. It never checked that the approver was somebody other than the proposer — and wrote \"approved\" into the audit trail anyway.
I Changed How I Think About AI Memory
I Changed How I Think About AI Memory When I first built Lean AI Memory, I focused too...
One GPU, four ways to share it: ten scenarios, and the headline finding I had to retract
I measured every GPU sharing mode across ten scenarios, published a headline finding that duplicate models are nearly free on unified memory, then failed to replicate it and retracted it. Here is what the controlled replication showed and how the original measurement fooled me.
I attacked my own npm package before launching it. It let the proposer approve their own writes
My library exists so a human approves an LLM's UPDATE before it runs. It never checked that the approver was somebody other than the proposer — and wrote \"approved\" into the audit trail anyway.
I Changed How I Think About AI Memory
I Changed How I Think About AI Memory When I first built Lean AI Memory, I focused too...
I got tired of SSHing into 10 VMs a day, so I built a live map of my whole infrastructure
Every day at work looked the same. Something breaks, or I need to push a new image, and I'm SSHing...
What Is the Circuit Breaker Pattern? A Practical Guide
What Is the Circuit Breaker Pattern? A Practical Guide for Developers Imagine your...
Protecting Microservices: Implementing End-to-End Encryption Across REST APIs
End-to-end encryption across REST APIs is the difference between a microservices architecture that...
Tìm Kiếm Giải Pháp Theo Công Nghệ & Tiêu Chuẩn Thực Tế
Mỗi thẻ tag trong hệ thống bài viết đại diện cho một tiêu chuẩn kỹ thuật thực chiến như `#Nuxt4`, `#KEDA`, `#Zero-Trust`, `#Kafka`, `#vLLM`. Sử dụng thẻ tag để nhanh chóng khoanh vùng các bài viết giải quyết chính xác bài toán hệ thống của bạn.