Drafts

Is AI making us more productive yet, more faster yet? Non-code # [1] probably not I’ve seen this question hitting all over the Internet lately, and often points to people not writing code. Copilot turns prompts into emails, emails back into summaries that look a lot like prompts. I think there’s a place for this, making rambled thoughts sound more coherent, summarizing notes and meeting minutes. All good stuff but does it make us more productive, probably not by an amount that you can put $ $ behind, unless you are reducing headcount. thats not what we are doing right??? Coding # [2] with chat, probably not When we talk about chatbots like gippity I think there’s a benefit to having someone with jr skills in everything to talk to, someone who can read all of the docs in an instant to get you some code snippet that might have taken all day to research and get right, but more productive, probably not. Agentic Coding # [3] maybe I’ve hit a stride with coding agents this year u...

drafted by kimi /style How I write and build this site. A personal style guide. Tone of Voice # [1] Casually self-deprecating with technical credibility. I write like I’m talking to someone at a conference after-party, not a LinkedIn profile. It’s okay to poke fun at myself and my projects. “Under-funded, over-dreamed, barely documented” is a feature, not a bug. Principles: - Use first person (“I”, “me”, “my”) - Keep sentences punchy and direct - Include real personal details and hobbies - Show technical expertise without taking myself too seriously - It’s okay to mention frustrations with mainstream tools Writing Rules # [2] Formatting: - No em-dashes. Use periods or commas instead - No emoji - 80 character hard wrap - Double space between sentences - Headers should be concise (2-4 words) Structure: - Put code examples front and center - Add brief context or “why this matters” even if just one sentence - It’s okay to say “I use this when…” or “This saved me fr...

drafted by kimi /interests Things I’m passionate about and why they excite me. Mechanical Keyboards # [1] I’ve fallen deep into the custom keyboard rabbit hole. Building keyboards combines electronics, ergonomics, and 3D printing into one satisfying hobby. What I love about it: - Tactile feedback - Every keystroke has personality - Ergonomics - 40% split layouts changed how I think about typing - Customization - From switches to keycaps to case design - DIY culture - Hand wiring, firmware hacking, designing my own PCBs Current projects: - Building a split 40% wireless keyboard - 3D printing custom keycaps - Designing the “portajohn” keyboard case See my keyboard posts [2] 3D Printing # [3] From functional parts to artistic experiments, 3D printing lets me materialize ideas. What I print: - Keyboard components - Cases, keycaps, plate files - Practical tools - Knife sharpeners, microphone mounts, dovetail experiments - Kid projects - Working with Wyatt on various b...

Are developers really running 5 agents in parallel? How the Heck do they keep up with the changes? This seems Impossible. I was listening to Syntax.fm this morning and heard this question, and thought I’d throw in my take, which is probably pretty similar to Wes and Scott’s. https://www.youtube.com/watch?v=NrBQI9So5lM&list=PLLnpHn493BHHNUfHN5lDf11UD8jQ5Bpzl&index=1&t=99s [1] Yes # [2] Yes, developers are running 5 agents in parallel. It’s not that hard it requires you to shift from thinking about the weeds and seeing the forest see: Pm Not Babysitter [3]. It requires effort and diligence. Most importantly it requires planning, it requires agents, it requires tooling. Is anyone doing this all day? Probably not. At least not outside of the startup companies that are building out tools to do this. Yes there are some, there’s always outliers, but its going to be rare. To have multiple agents running in parallel add day you need a lot of tokens, access to good models, and right now ...

A running list of blog post ideas to strengthen underrepresented topics on the site. Docker Posts # [1] Building out Docker/containerization content to match the llms.txt claims. Existing Foundation # [2] - docker-deep-dive.md [3] - unpublished notes from 2021 - docker-minecraft-server.md [4] - minecraft in docker - modded-minecraft-in-docker.md [5] - modded server setup - emoji-in-headless-chrome-in-docker.md [6] - headless chrome fix Suggested Posts # [7] - “Why I containerize my entire dev environment” - Philosophy post linking to the 2026 resolution about working from a distrobox image - “Docker vs Kubernetes in the homelab [8]: when to use what” - Standalone comparison post (referenced in right/wrong reasons posts) - “My devtainer workflow: dotfiles in Docker” - Document the actual devtainer setup mentioned in llms.txt - “Migrating from Docker Compose to Kubernetes with kompose” - Experience from the 6-months-in post, expanded - Finish docker-deep-dive.md - Turn th...

I’ve been dabbling with go this week using

In early 2026 I’m trying to lean more in to agentic workflows. The tools are not only better than they were a year ago, but available to me now unlike they were 6 months ago. What I’m using # [1] At home I’m using opencode, the tooling here is fantastic. LSP incide of these things is incredible, mcp is fine when its needed. The free models it gives you are impressively good for free models, but they are still not the big models from the big providers. I’m using what work gives me, they give me a tool with access to good models, the models are great, the tools kinda suck. I’m being vaugue here because I dont share real work details. Skepticism # [2] I’ve been skeptical the whole way, I see ai being a very useful tool. I remain Techbrophobic [3]. It’s better than the non believers will tell you, and no where near as good as the hype bros will tell you. The industry is shitty and doing shitty things, I’m not here to change this, I’m here to do my thing and try to get better. Softw...

I’m late on this one so I’ve seen everyone else’s. I’ll try my best to make some bold predictions I’ve not seen elsewhere more open source, less open contribution # [1] I predict that this is the point in time that we see an explosion of open source, but more projects than ever going the way of sqlite, Livestream, android, unreal engine, aesprite. It is getting so easy for agents to generate 10k lines of code in a few hours. This makes it easy for folks who have ideas they want to create to create them. It also makes it much harder to accept outside contributions when they make such massive changes. Thirdly it will be easier for folks to just make their own fork to do what they want. Right now it’s hard to name 5 big open source, closed contribution projects by the end of the year there will be 5 more that are recognizable. I think more open contribution will go the way of [[ whenwords ]], spec driven development. This is very high level. Very easy to understand a large portion ...

A new approach to agentic workflows. This is probably news to no one else, I’m sure I’m behind on this one. You can’t one sentence prompt and expect to get what you want. Agents.md # [1] Writing Complete Prompts # [2] References: [1]: #agentsmd [2]: #writing-complete-prompts

It’s the start of 2026 and agents are getting a lot better than they were. I’m using opencode at home, free mode with Zen and big pickle. At work I have access to a wider variety of models including what seems to be the gold standard 3 from anthropic opus, sonnet, haiku. Note I’ve sat on this post for over a month, refactored it a few times, things feel like they are moving so fast that its hard to keep my feelings straight. Things are changing # [1] Around Aug 2025 I wrote I'm Out On Agents [2]. I saw others in the space having such great success I gave it a solid shot, but found it to egregious edit more than I asked, make massive unneeded changes, and make more small bugs hidden in the details than was worth it. This was just after the tipping point where not just hype bros were making the switch, but people I work with, people I trust and have made really good Software in their career. People like the creator of Flask Armin Ronacher. People who are really good at writing co...

Old Man Hardware # [1] Character Profile Name: Graybeard McGee Age: 64 years old Role: Senior Systems Architect (counting down to retirement) Background Graybeard’s been coding since before most developers were born—starting with assembly on PDP-11 systems in the late 1970s. He still has his original DEC VT100 terminal in the garage and actually uses it occasionally. His collection of vintage computing gear would make a museum curator jealous. Tech Stack - Loves: C, Assembly, FORTRAN, Perl (the “real” scripting language) - Hardware: Sun SPARCstations, DEC VAX, vintage IBM mainframes - Editor: Vi (not Vim—“Vim’s for kids who need training wheels”) - Version Control: CVS ( reluctantly moved to Git [2], complains about it daily) Personality - Grumpy but surprisingly helpful when you prove you’re not “another JavaScript framework cowboy” - Believes “if it was good enough in 1985, it’s good enough now” - His office smells like old electronics and coffee - Has strong opini...