Agentic Workflow as of October 2026

Sunday, October 18, 2026

tl;dr: This post describes my first current very rough approach to agentic development. This approach is heavy on docs, folder structure, and copious tools and scripts for verification feedback. My current approach is codified by the Winetech Standard Repo, which is a barebones skeleton of the structure and built-in agent ready documentation to get started on a new project. Actual Take-Aways Use ADRs Prune memories, AGENTS.md, and other context-filling documents regularly Provide a space to put observations found during their tasks so don’t get distracted and information doesn’t get lost Keep as much inside the repo as possible, to provide agents with the context on demand that they need Provide tools and scripts that can give negative feedback to the agents so they can quickly course-correct on their own Give them a runtime of your application to test against in a live setting. Static analysis is not enough. Table of Contents tl;dr: Actual Take-Aways Prerequisites Models Harnesses Subscriptions Project Ownership Folder Structure adr/ investigations/ tickets/ backlog.md Verification and Feedback Repo Tools AGENTS.md and Memories AGENTS.md Memories Skills Pruning files when they get too big or outdated Working with the Agents Prompting Style Corrections Lean into their biases and expectations for tools and docs Hooks and notifications Parallelization Some Usage Patterns “Wrap up” Handoff Documents Rewrite To Be Forward Looking Team A vs Team B Recent Worked Examples Reducing Token Spend on Backtracking during Failed Test Runs Test Suite Optimization Automation and Accessibility Migrating a Failing Robotics Sample From Gazebo to MuJoCo Prerequisites People get different results from the different workflows, tools, models and harnesses they use, so I’d like to set out what my particular set up looks like at the outset, so you can adjust your own expectations. …

Implementing OAuth 2.0 from the RFCs

Monday, January 5, 2026

Prologue OAuth is a common peice of web technology infrastructure that underpins many common websites. To keep things short, its how you log into websites. But we’re here to learn more than that. First, how much detail would you like to learn? Select a skill level, and we’ll work from there. n.b., we will only be covering OAuth 2.1 here, since OAuth 2.0 is now deprecated. That means no Implicit Flow, and Authorization will use PKCE only. Also, we’re going to be deep-diving into a bunch of RFCs, so depending on the experience level, be prepared for some technical writing. …

Programming Language Features I'd Like Most Languages To Have

Tuesday, January 10, 2023

Here are some things I am dissappointed to leave behind when I switch back and forth between languages that dont have certain features. If Expressions Found in: Rust; probably other functional languages Irritatingly missing from: Everything let x = 5 + if true { 1 } else { 7 } println!("{x}"); // 6 What I have to do instead: let x = 5; if true { x += 1; } else { x += 7; } System.Console.WriteLine($"{x}"); Ternary Found In: Everywhere except Go Ternaries are like If Expressions but less powerful …

Music Channel Part 3 - Branding

Wednesday, March 27, 2019

This is the third in a series of posts about analyzing YouTube music channels. Part 1 - Music Channel Introduction and Data Collection Part 2 - Analysis of Channel Activity Part 3 - Branding Branding Remember that we’re basing our channel the behavioral patterns of some other channels: TheSoundYouNeed MajesticCasual MrSuicideSheep Chill Nation Eton Messy MonsterCat MikuMusicNetwork Among their other patterns, we’re going use them as a base for how to brand our channel as well. …

Music Channel Part 2 - Stats

Tuesday, March 26, 2019

This is the second in a series of posts about analyzing YouTube music channels. Part 1 - Music Channel Introduction and Data Collection Part 2 - Analysis of Channel Activity Part 3 - Branding Your Questions, Answered We left off last time with a freshly created database full of information we could query. We sought to answer a few questions: How many videos should we seed our channel with? How often should we upload? Should we upload more than video at once? How long can we wait between uploads if something goes wrong? Channel Seeding? We’ll take the first upload date of each of our channels and see what their total upload count is: …

Music Channel Part 1 - Data

Monday, March 25, 2019

This is the first in a series of posts about analyzing YouTube music channels. Part 1 - Music Channel Introduction and Data Collection Part 2 - Analysis of Channel Activity Part 3 - Branding Background I often listen to new music on YouTube because their discovery systems unearth some occasionally great finds. After a while of listening there however you begin to realize that there are only a handful of channels that get recommended to you, and they all seem to just upload songs and let the views roll in, not unlike a radio DJ. Sometimes these channels become so successful that artists will begin to sign with the channels for exclusive releases, in effect turning the channels into a de-facto label. Some of these channels have even turned into de-jure labels, such as Proximity. …

It's always DNS

Monday, February 25, 2019

I had decided that I was going to re-visit the way Lyricall’s infrastructure is deployed, because while functional, it was many complicated and esoteric steps away from “one-click deploy”. Near the completion of the .NET Core side of the deploy where it became time to test production-like connections to the primary, real database, problems started to arise. No matter the configuration, .NET was spewing connection refused errors to the postgres backend. I tried the following diagnostic steps: …

Swipr - Server

Thursday, December 13, 2018

Recall our arch diagram from the two chapters ago: The Database Service is a collection of methods opening and closing SQLite connections and, while important, is really exceedingly boring and furthermore, unsurprising. As such, we’ll leave it out of the discussion. We’ll also leave out building the Razor Pages and the views, dealing with identity, migrating our initial user tables with EF Core and other such minutiae of running an ASP.NET Core server. …

Swipr - Datastore

Thursday, December 13, 2018

We need a datastore. Primarily so that we can stow a given user’s Tinder information – Facebooked ID, Facebooked password, Facebooked access token, and Tinder access token, – but also because we now have a complicated application it’s state must be preserved somehow. We’re going to skip talking about tables relating to how ASP.NET Core projects do identity because there are a lot of tables for that. The only thing worth pointing out with respect to that is many of our tables will keep a foreign key to the autogenerated AspNetUsers.Id field. …

Swipr - LibSwipr

Thursday, December 13, 2018

As a harness for our model, we’ll create a server that serves as a centralized access point. This server provides the necessary facilities to register an account with it, interact with Tinder, and receive responses from the model. The general architecture for the server will go something like this: SwiprServer is the server, in our case, an ASP.NET Core 2 project, and LibSwipr is our custom tooling around all the other interactions. …