John Wilger

Four rules got added to my agent harness the morning I built Lanyard.

This morning I had an annoyance.

Every pitch for AI-assisted development leads with speed.

I use separate Chrome profiles for personal and work browsing.

I didn't set out to build an eval system for my coding-assistant plugins.

A while back I helped build an AI assistant that lived inside a business application and answered questions about the company's data.

There's a pattern I've noticed among developers working with AI coding assistants.

Before we start, I want to make it clear that I'm not going to "blame the controller" for losing this game.

The first time I worked on an application that heavily relied on OpenAI's chat completion API, my years of experience managing APIs within an extensive service infrastructure shaped my approach.

When I first engaged with computers, the landscape was predominantly shaped by command-line interfaces, a stark contrast to the GUI-based systems like Windows or MacOS that later emerged and democratized computing.

UPDATE 2019-07-25: Based on some comments made on the original post below, I swapped out the Asus ThunderboltEX 2 AIC for a Gigabyte GC-Titan Ridge Thunderbolt AIC that supports two DisplayPort inputs.

Ecto makes it easy to work with typical uniqueness constraints in your database; you just define your table like this: defmodule MyApp.Repo.Migrations.CreateFoos do use Ecto.Migration def change do create table(:foos) do add :name, :text, n…

I just released version 0.24.0 of Kookaburra to Rubygems.org.

I started using tmux recently after a) I was informed that GNU screen is basically an outdated POS, and b) an excellent book on the subject was published.

After getting some good feedback on Kookaburra Kookaburra since the original release announcement as well as using it in a few more projects, [Sam] SLG and I decided to treat all of the versions prior to 0.15.0 as a spike and rewrite the framework from the

I really like using [Jeweler] 1 to create and manage gems, but its default behavior is to publish your gem to [rubygems.org] 2 whenever you run rake release.

UPDATE (2012-01-22): I realized this morning that the credit I gave to Sam Livingston-Gray below may not have adequately shown how instrumental he was in getting this project off the ground; especially since much of his work was done in the private reposi…

I banged my head against this one while setting up our CI build for a new project at work and just now figured it out.

The Renewable Funding technology team is moving into some new office space in a few months, and now that we'll have our own space, I'd like to start up a variation on an apprenticeship program at work.

After growing the ProjectDX team from three to eight software developers, our release process was a complete pain, and it typically took two to three hours to get a good build on the production branch (and even then some insidious issues would sneak throu…

Yesterday, Elizabeth Hendrickson posted her Agile Acid Test in which she asks three questions to determine whether or not a team is truly "agile".

Sprint 1 (11/03) Sprint 2 (11/24) Alpha (12/15) Beta (12/29) 11/03 11/24 12/15 12/29 I facilitated my second release retrospective with the ProjectDX team yesterday.