Write Software for the Team You Have
A contractor's architecture test: when the work is handed off, can the client's team understand it, extend it, and actually want to keep working that way?
Writing
Newer writing belongs here first, whether it is published on this site or elsewhere. The old blog remains available as an archive, but this page gives the current work a cleaner place to live.
Recent articles that still represent what I am thinking about now: pragmatic cloud work, small useful automation, technical tradeoffs, and the human machinery around software.
A contractor's architecture test: when the work is handed off, can the client's team understand it, extend it, and actually want to keep working that way?
Notes from moving a bash workflow into Azure Functions, including logging exceptions and saving generated PDFs to Google Drive.
A practical look at juggling personal and client calendars without letting schedule management become its own job.
Next on kyle.baley.org
Future posts can publish directly on this site and appear here without being mixed into the legacy archive. Western Devs pieces stay credited to their original home.
Articles from Western Devs are collected here as part of the public body of work, with links back to their original publication.
Legacy Archive
337 posts from 2006 through 2015, kept for reference and separated from newer writing so the site no longer feels frozen in time.