// Topics / Developer Experience

Developer Experience

    AI Documentation Search: Versioned Retrieval and Citations AI docs systems often retrieve the wrong version and never admit uncertainty. Build one with hybrid search, version filters, citations, and freshness jobs. engineering ai llm Model Context Protocol in Go: Building an MCP Tool Server I built a Model Context Protocol server in Go with mcp-go. The protocol layer is clean. Auth, permissions, and write safety are still on you. agents ai go AI for Technical Documentation: Drafts Yes, Ownership No AI is a decent drafting assistant for technical docs and a poor substitute for ownership. Draft with AI, review in the same PR, and ground doc search. engineering ai developer-experience Most AI Developer Tools Are Not Worth Adopting Yet AI developer tools are multiplying, and most add complexity without removing friction. The filter I use to decide what earns a spot in the stack. ai developer-experience opinion AI Coding Assistant Productivity: Three Months of Numbers Three months tracking Copilot and GPT-4 on real Go work: 25-30% faster on boilerplate, no gain on debugging, and a 15% review tax on AI-written code. ai developer-experience productivity AI Code Review: What It Catches and What It Misses Three months of AI-assisted code review on Go services: it catches unchecked errors and leaks, misses context, and only helps once you filter the noise. ai engineering developer-experience Five Days With ChatGPT: First Impressions From an Engineer Five days with ChatGPT as a working engineer: fast first drafts, confidently wrong answers, and why verifying the output now matters more than typing it. ai llm developer-experience GitHub Copilot After Six Months: Faster Drafts, More Review Six months with Copilot in real projects. What it actually helps with, where it quietly makes things worse, and why the productivity claims are overblown. ai developer-experience productivity Platform Engineering: DevOps Grew Up Platform engineering is what happens when you realize 'you build it, you run it' does not scale past a handful of teams. platform-engineering devops developer-experience Monorepo vs. Polyrepo: A Practical Decision Guide Monorepo or polyrepo depends on coupling, team shape, and your appetite for build tooling. Here is how to decide without getting religious about it. architecture development developer-experience Engineering Documentation: Owners, Doc Types, Docs as Code Engineering docs get ignored because nobody can find them, trust them, or tell what they are for. Owners, separate doc types, and docs as code fix it. engineering developer-experience teams Engineering Onboarding: Ship a Real PR by Day Three Most engineering onboarding wastes the first week on access requests and context overload. The fix is simple: ship a real PR by day three. hiring leadership teams Platform Engineering Maturity: Why Teams Stall at Level 2 Most platform teams build tools nobody asked for while developers wait in ticket queues. Lessons from platform teams at large companies. platform-engineering devops developer-experience GitHub Copilot: First Impressions From a Go Developer Early notes from GitHub Copilot's technical preview on Go code: strong on boilerplate and tests, wrong on domain logic, unresolved on licensing. developer-experience ai go Internal Developer Portals: Start With the Service Catalog What I learned about internal developer portals at large telecom companies, and why the service catalog is the only part that matters on day one. platform-engineering developer-experience How I Build CLI Tools in Go: Patterns That Hold Up Patterns for Go CLIs that hold up: cobra commands, stdout vs stderr, useful errors, signal handling, config precedence, and shipping static binaries. developer-experience go Developer Experience: Internal Platforms vs Ad-Hoc Tooling Purpose-built internal platforms versus the scripts and Makefiles teams grow themselves, and the team size and pain at which each one wins. developer-experience platform-engineering devops Internal Developer Platforms: Treat Them as Products Most internal developer platforms fail because nobody treated them as a product. Lessons from building, and scrapping, platform tooling at three startups. platform-engineering devops developer-experience