Drafts

I’m tracking results of 2026 Predictions more open source, less open contribution # 2026 is not the year to build hardware # Agents will overwork us # The AI Vampire This was an unusually hard post to write, because it flies in the face of everything else going on. Medium · steve-yegge.medium.com 2026 is to ai as 2012 was for js frameworks #

This is an idea I had today. Using ai to write code is a lot like using CAM software for machining. Default settings plop it in and let it ride is probably decent for a lot of things, but not great for production, you probably want more fine grained tools, higher tolerances, first piece run offs quality gates. A good manufacturing engineer is probably not hand coding g-code, but they know the right gates to pass before sending parts through production.

Take a moment to think about who it is you want to be. Is this really where you are heading? AI is a force multiplier I’ve heard this many times, notably from @theprimeagen, ex Netflix BTW, who is an excellent engineer that I take a lot of inspiration from. I’ve really started seeing this play out with the various people I work with and myself. Now more than ever we need to consider these personality traits as we try to build out our teams, hire and backfill. We need to think about where we want to see this team and what type of person is really going to get us there, what people we have on the team and what gaps we need to fill. The Prolific Prototyper # The ones who were able to knock out entire projects in a week are able to do this in an afternoon. They are able to ship early and often and get something in the hands of users as fast as they ask for it. Code quality, reliability, observability thrown into the wind, we are lookng for features shipped, actionable use cases implemented…

Hyrum’s Law # Any implementation detail in your software will become depended on whether you like it or not. Parkinson’s law # Work will expand to fill its space

Intro paragraph with ordinary strong, ordinary emphasis, ordinary highlight,, a normal link, and deleted text. Build good places for interesting people. Make room for the weird idea. # Some normal paragraph text between headings. Build a that feels yours. # More ordinary prose. Follow the small web, not the cr owd. # Make a perfect memorable site. # Leave space for strange little ideas. # Sometimes the obvious answer weird answer is the interesting one. # A good theme makes quiet words,, and loud words belong together. # A highlighted phrase can be long enough to wrap onto another line and test the highlight background. # Make a small corner of the web that feels like yours. # Chemistry should still work: H 2 O and x 2 # Keyboard syntax should still work: Ctrl + C #

When ai tells you “this is 6-8 focused prs” do you ignore, chuckle, laugh. Ya in your training data it might be. by hand it probably was, but realistically I’m going to shove 3 of these at this level into one pr regret my choices later. Decades of pr data no longer makes sense # Introduced on February 23rd 2008 in their 3rd blog post. via

GREAT # measured: 2.7in x 3.85in x 1.425in calculated: 68.58mm x 97.79mm x 36.195mm measured.64in radius calculated: 16.256mm radius measured:.115in wall thickness calculated: 2.921mm wall thickness PITA # measured: 2.315in x 3.55in x.985in calculated: 58.8mm x 90.17mm x 25mm sharp corner MINE # 68mm x 98mm x 36mm 16mm radius 3mm wall 3 wide = 68 3 + 3 4 = 216mm 2 wise 1 tall = 68 2 + 98 + 3 4 = 246mm

As we have bigger and better ai tooling that continues to rise up in its capabilities month over month, theres a common question that pops up. Are Juniors cooked. Honestly I don’t think they are. I think we will still have unicorns that really dive in and understand deeply the code. I think the John Carmacks of the world are going to be fewer than before, but they will be found as we need them. As more and more and more and more and more tech layoffs happen throughout 2026 get blamed on AI. I become concerned for our industry. how

install linux from scratch create a website from scratch Sharpen a knife

🌱 This post is still growing

🌱 This post is still growing Late last year I started writing I'm Out On Agents. Agents sucked, the models were good, but there was still something missing between the harnesses and the models. They could write good code, they could do some debugging and exploring, but they were too good at fucking up the whole project to be useful. They could crank out Green Field POC’s like nobody’s business, but they created so much mess in brown field projects that it was easier to chat and edit yourself. The Inflection Point # It’s very well agreed on that the inflection point for most people happened with Anthropic Opus 4.5 in late Nov 2025. Early adopters probably noticed right away and shouted from the rooftops how good it was. But we’ve all heard that developers have 6 months before ai writes all the code for years, so this felt like the rest of the noise. Hitting the December slowdown many of us hit code freezes at work. We completely disconnect from work for the last Week and come back in Ja…

I’ve been thinking about this for awhile, the AI wars are so much worse and burnout prone than the framework wars of the 2010’s. I remember really starting my professional programming journey during the framework wars. It was a time when there were new and exciting js things every single month. Frameworks and meta frameworks came and went, the ones that lasted changed best practices yearly or so, often flip flopping on technique. I was deep in python and data engineering at the time and only experienced it adjacently. I was into webdev. I did a bit of react, gastby, vue, gave all the big ones a try in a demo level.

Requirements # Minecraft Terraria SilkSong 3x6 layout #

Session ID: ses_3444b09b1ffeXTEr3ELFg5qqtg Created: 3/4/2026, 7:55:24 PM Updated: 3/4/2026, 8:52:32 PM User # I want to spec out a cli for tmux session switching in go. responsive to terminal size works in tmux popup shows list of tmux sessions with favorites pinned at the top keymap j/k arrow navigation tab to switch sections asdfqwertzxcvb to pick a session (letter listed next to the session) space to select a session, then arrows j/k move that session up in priority and hotkey letter Assistant (Build · gpt-5.3-codex · 2.4s) # Thinking: Initiating brainstorming skill load Tool: skill Input: Output: Assistant (Build · gpt-5.3-codex · 8.8s) # Thinking: Planning cautious context inspection Tool: glob Input: Output: Assistant (Build · gpt-5.3-codex · 27.0s) # Thinking: Outlining comprehensive spec approach Great idea. Here’s a practical spec you can build straight into Go. Product Shape Build (tmux session switcher) as a full-screen TUI that also runs cleanly inside. Primary goal: fast s…

Ansible Vault keeps secrets out of sight, but the ciphertext changes on every encrypt. That turns Git diffs into noise and makes it hard to tell if anything actually changed. Decrypting, editing, and re-encrypting often leaves uncertainty about whether any plaintext changed. This is amplified when secret repos are tightly coupled to dependent repositories. A typical cycle includes decrypting, adding a key, updating a value, applying changes, and returning later with little clarity about what changed while secrets were in plaintext. Today a new workflow was created with @gpt-5.2-codex to keep diffs clean and avoid re-encrypting when the plaintext is identical. Waylon Walker This repo has ansible vaulted secrets and an encrypt/decrypt process, but no way to compare. Please research compare options. The goal is to avoid changing files on encrypt/decrypt when plaintext is unchanged, ideally by comparing decrypted content and reusing the remote encrypted file. @gpt-5.2-codex The repo workfl…

I don’t know if you know this, but the web is a beautiful platform that allows you the freedom to create things and put them out there. Its not tied to four major platforms. You don’t have to post your thoughts, ideas, and apps to a platform, you can just make it. This is a beautiful thing that seems to have been forgotten. I was inspired this morning from @scotthanselman’s tinytooltown. Looking through all of the tiny tools that people have built for themself, as personal software, not answering to anyone but themself, it was inspiring. Agents have gotten a lot better, like seriously better. The ai bros that were ai pilled too early that said SWE is over in six months called it too early. It wasn’t time. Now since Nov 2025 we have had agents that can do some damn work. Proving the point some of the greatest devs I’ve ever looked up to have not written a line of code since. Not hype bros or someone not good at the craft, but seriously good devs leaning on it full time. AI hype over you…

Is AI making us more productive yet, more faster yet? Non-code # 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 # 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 # maybe I’ve hit a stride with coding agents this year unlike I’ve hit before. I…

drafted by kimi /style How I write and build this site. A personal style guide. Tone of Voice # 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 # 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 from…” Personal anecdotes add authenticity Technical terms ar…