Thoughts on building systems, engineering teams, AI-native workflows, and durable product practice.
A few pieces that capture my current thinking about AI-enabled engineering, review workflows, and the social systems that make software work.
We now have machines that do not merely execute instructions. They participate in reasoning. Not perfectly, not independently, not in some mystical human-equivalent sense - but enough that the mode of interaction has fundamentally changed.
Remote work made hiring global, but compensation still hits a border. A Melbourne-versus-US comparison shows how same-team pay can diverge sharply even after accounting for super and employer payroll costs.
An intentful, workplace-ready substitute for the stigmatizing "vibe coding" paradigm
When code output is cheap, trust becomes the constraint. Guild Driven Development makes review the control surface that keeps systems coherent.
How I successfully transitioned context between AI agents to solve a complex Sailfish test discovery issue, turning a long debugging session into a collaborative success.
Building positive work relationships is not only the way to be more effective, its necessary for being a leader and getting ahead.
Iterative planning in software development offers a robust framework for delivering products that are not only high in quality but also aligned with customer needs and market demands.
Time can be an expensive commodity - so sometimes it pays to focus on the need before anything else
Making small, incremental changes to your software speeds up delivery and improves product surviability
Artificial Intelligence has taken a leap - and our APIs need to be ready for it
Software development and biological evolution share a lot in common, so much that we can distil and apply useful principles
A Guide for Making Code Reviews Easier for you and your Peers
If the Big Bang took only milliseconds to disperse all the galaxies light years apart, then how did the matter get there faster than the speed of light?
What does a future with AI look like?
A record of a semi-popular stack overflow answer I gave to a question
I encountered an annoying error when building a nextJS app that uses nextMDX using github actions
I once had someone ask me what I thought about using my PhD title in my profile name because they were wondering if they should as well
An abstraction pattern to simplify the creation of new endpoints that have the same base abstract logic
Part 3: Applying SOLID for a clean file management abstraction
Part 2: Palavyr Persistence Abstractions
Part 1: The three phases of the Palavyr API surface
Autowired properties in Autofac are tempting, but are they a good idea?