If you’ve spent any time working with AI coding assistants, you’ve probably encountered context rot — that moment when your AI session loses track of what it’s doing, starts hallucinating, or produces code that doesn’t match the original plan. The more complex the task, the faster things spiral.
The AI agent landscape in 2026 is crowded, noisy, and full of promises. Two names keep surfacing in developer conversations: OpenClaw and Hermes Agent. Both claim to be the autonomous assistant that finally bridges the gap between AI reasoning and real-world execution. Both are open-source. Both run locally. Both connect to messaging platforms.
For years, AI coding assistants worked the way a single intern would: one task at a time, one conversation at a time, one file at a time. You asked a question, waited for an answer, then asked the next one. Sequential. Linear. Slow. In 2026, that model is dead.
If you’ve been working with web servers and reverse proxies for the past decade, chances are you’ve used nginx. It’s been the backbone of countless web infrastructures, powering everything from small personal blogs to some of the busiest websites on the planet. But recent developments in the nginx ecosystem have led to an interesting fork called Angie — and it might be worth your attention.
In this post, I’ll walk through the history of nginx, what happened after the F5 acquisition, why Angie was created, and why you might want to consider making the switch.
Over the past year, I’ve been working extensively with AI coding agents — intelligent assistants that go far beyond code autocompletion. These agents can plan, execute, and iterate on entire development tasks. They function like tireless pair programmers who never lose focus or context, dramatically increasing productivity when guided correctly.
Install GitLab CE with custom PostgreSQL and Nginx proxy.
In this post I will show you how you can use GitHub Actions for CI/CD and pass artifacts between jobs.
In this post I will show you how to Install and configure Tekton on a Kubernetes cluster.
In this post I will show you how you can set up self-hosted GitHub action runner in Kubernetes with Actions Runner Controller.
One of the most common use case is to build a Docker image with Gitlab. In a previous post we used dedicated docker runners for this job. But howe can we build images in a Kubernetes runner? In this post we well se this.