| |
| 🔗 Stories, Tutorials & Articles |
| |
|
| |
| Why I stopped using NixOS and went back to Arch Linux |
| |
| |
After a year on NixOS, the author reverted to Arch Linux. They blamed frequent breakage, rebuild loops, and unpredictable regressions after updates.
They flagged NixOS's reproducible config, isolated builds, and multi-generation installs. These swell disk use, force wide glibc rebuilds, and make updates slower than pacman. |
|
| |
|
| |
|
| |
| Announcing the AI Gateway Working Group |
| |
| |
Kubernetes launched the AI Gateway Working Group. It will add standards and declarative APIs to make networking play nice with AI workloads and extend the Gateway API.
Active proposals attack two gaps. Payload processing inspects and transforms full HTTP payloads using declarative configs, ordered pipelines, and explicit failure modes. Egress gateways route outbound AI traffic out of the cluster.
This is a system shift. The group pushes AI-specific networking into the Gateway API, moving policy enforcement up to the platform so inference traffic follows standardized network rules. |
|
| |
|
| |
|
| |
| When Kubernetes Is the Wrong Default |
| |
| |
The guide maps team size, workload shape, and time-to-value to three tiers: managed platforms, VMs, and Kubernetes.
It calls out Kubernetes bluntly: expect a 1–3 month delay to production. Expect ongoing consumption of 30–50% of one engineer. It only pays off for multi-region setups, complex networking, or teams with dedicated platform engineers. |
|
| |
|
| |
|
| |
| How I Use LLMs for Security Work |
| |
| |
| LLMs like Claude, Cursor, and ChatGPT help tackle complex problems, but prompting them like Google won't cut it. Use role-stacking for varied perspectives (e.g.: you are a senior security engineer and sr. software engineer with experience in Docker, Kubernete..) and always specify your tools for better output. Validate reasoning, ask for systems thinking, and iterate prompts for enhanced results in security work. Keep human judgment paramount; LLMs enhance, not replace, our critical thinking. |
|
| |
|
| |
|
| |
| Podman fixed every problem I had with Docker, and I switched in an afternoon |
| |
| |
Author swapped Docker for Podman. The swap revealed CLI parity and minor networking and volume tweaks.
Podman eschews a central daemon. It runs containers as system processes and defaults to rootless via user namespaces. That cuts privilege exposure and trims baseline overhead. |
|
| |
|
| |
👉 Got something to share? Create your FAUN Page and start publishing your blog posts, tools, and updates. Grow your audience, and get discovered by the developer community. |
