Johannes "Lockhead" Koch

@lockhead.dev

Builder, CI/CD and AWS enthusiasts, AWS DevTools Hero, creator of https://www.youtube.com/@cicdonaws

Every blog you write is feedback — to OSS maintainers, to product teams, to the community. Your opinion matters. Don't let the flood of AI-generated content stop you from sharing what you've learned. Speak up and never stop! What's stopping you from writing? Let me know 👇

This is exactly what I was talking about! Markus is back to writing after 10+ years. No SEO strategy, no editorial calendar — just thoughts shaped through conversation, published when ready. Welcome back to blogging! https://lckhd.eu/uP2Hek

Hello World - Back to writing (with or without AI)

After more than a decade of speaking and organizing but not writing, a LinkedIn post about AI slop reminded me that blog posts can be conversation starters too. Here

lckhd.eu

I'm actually also going to host an #AWSCommunityBuilders meetup at the #AWSCommunityDayDACH26! I'd love to see you there if you're a community builder to answer all of the questions that you have! See you on the 15ths of september! 🧵

At the AWS Heroes Summit we talked about how many of us have gone quiet in 2026. AI floods the internet with content — but YOUR voice, your experience, your mistakes... that's irreplaceable.

Bild

AI changes the way that I look at the speed of delivering features. We shouldn't talk about "daily" deployments but rather about hourly. The biggest challenge will be how to safely deploy, speeding up your pipelines and ensuring that everything you deploy is tested. #BuildInPublic #AI

Quadratic compute. On every single step. That's what LLM inference looks like without a KV cache. The KV cache fixes it — making inference linear & affordable. But your cluster might be destroying that cache without you even knowing. 😬 AWS User Group 🧵

One of the underrated videos on my YT is one I did with Ran around Claude Best practices and things you need to know - somehow it didnd't get much traction... Why do you think thats the case? #Claude #ClaudeBestPractices #AIEngineering

Hot take: Kubernetes was never built for LLM inference. 🔥 Every scheduling primitive you trust — round-robin, readiness probes, HPA, rolling updates — was designed to IGNORE the exact state that makes inference cheap. The result? Turn 10 of a conversation. 96,000 🧵

Context switching is a big issue when working with coding agents. You need to always keep in mind what you gave the agent. Difficult if you work on different projects and different tasks in parallel. How do you deal with that? #BuildInPublic #BuildWithAgents

#AWSHeroes like to talk and share their opinions. We have a few options to chat and discuss. What I enjoy most is learning from what others share and complain about and this is why #AI will not replace us ever.

Yes, if you can post things from the place that you're "right now" (ide, cli, etc.) it's more common to write shorter posts. This is potentially where X/Bluesky will get more traction from me right now? How do you interact with social media? #SocialMedia #MCP

Now that my MCP server works (again) and has 35 tools available, I can use this to post more human content again - directly from #Kiro @kirodotdev Or maybe also from #KiroCrew in the future?

🧵 Every token an LLM generates attends to every token before it. Without a KV cache? That's quadratic work — recomputed on every single step. With a KV cache? Linear. That's why inference is affordable at all. But here's the catch: that cache lives on ONE specific 🧵

📊 App Stats Update (last 30 days) 🚀 3,987 new installs across 8 apps 🔄 7,239 app updates 📱 1,776 active devices (Android) 🍎 ~26 daily active (iOS) • Gem,Ore & Struct Finder for MC: 1,738 installed, ~26/day iOS, +3,976 new, 7,213 updates • Nexus Share - Social 🧵

Thursday at the AWS UG Bergstrasse: "You are Paying to Compute the Same Tokens Twice" This time we have a new talk by Christopher Haar Every token an LLM generates attends to every token before it. Without a cache, that is quadratic work on every single step, the same 🧵