Coding Architect

Configuration is the tax you pay for not knowing who your user is.

An agent decides it is done when the checks it can run come back green.

Types made “this value is a string” checkable.

I have around 120 repositories under my personal GitHub account.

The reading order problem Stock Rust testing is fine, in the sense that a hammer is fine.

MCP server configs across the ecosystem default to npx.

The developer inner loop — edit, build, test, debug — is the highest-leverage piece of any engineering team’s workflow.

Most code review tools want to be a service.

The pull request was built for a world where humans wrote most of the code.

The same graph that helps an agent write code can help a reviewer trust it.

A Rust-Native Architecture Toolchain: forge, puml, and adoc Replacing the JVM and Ruby pieces of the architecture documentation stack with single static binaries Most of the tools I reach for when documenting architecture were built in another era.

The more context and tools an AI coding agent has access to, the better it performs.

Exploring Your Backstage Catalog Without Backstage How bsv gives you instant visibility into your software catalog from the terminal Backstage has become the de facto standard for software catalogs.

Visualizing Project Structure with rv A fast, interactive way to see what’s actually in your project Every developer has had the experience of opening an unfamiliar codebase and trying to figure out what’s where.

Seeing Your Codebase as a City Why we need better ways to understand code at scale – and how 3D visualization can help Software teams accumulate code the way cities accumulate buildings.

Building a Code Knowledge Graph for AI Agents How I rebuilt codegraph in Rust to give AI coding assistants a semantic map of your codebase There’s a fundamental tension at the heart of agentic coding today.

Vibe Coding is an innovative approach to software development that emphasizes creativity, flow, and emotional engagement in the coding process.

Hello there, fellow tech enthusiasts!

As someone delving into the world of software development, the journey seemed smooth and set.

There has been quite a lot of commentary on various social media channels about agile ceremonies and the traps that they often pose to enterprises. if not taken in the context of the value that they provide.

Interactive web applications are always more appealing than static sites.

Yesterday I spent some time experimenting with building containerized Go applications.

Ward Cunningham is credited with the first use of the team Complexity as Debt or Technical Debt (YouTube video) as a metaphor poor software implementation.

At the start of my career I worked with fairly dumb terminals and mainframes.

Orchestration and Choreography are often discussed as design options for event driven systems.

Risk is typically expressed as a function of likelihood and severity or impact.

Over the last month or so I have been writing some data collection and simple analysis routines for the things we (developers) use every day.

For the last few years I have been very interested in what we can learn about our software development processes by looking at the data generated by the tools that we use to manage and deploy our work.

Creating useful software models that represent the buisness they serve is hard.

As a developer I recognise the importance of generating logs for the systems that I help design and develop.

While developing web applications I have often needed to change the style of one or more elements based on the state of the data model used by the application.

I don’t usually write reviews but I was so deleted by es-mode for emacs that I felt compelled to share.

In domain driven design (DDD) we talk a lot about entities; objects that have identity and lifetimes that typically outlive their values. e.g.

Working with small teams is a lot of fun and I find it fairly easy to keep track of what is happening with version control and build systems.

How can we get the benefits of IoC containers at a higher level - the services that we deploy into environments?

In his keynote ‘This is water’ Neal Ford talks about “Yesterday’s best practices become tomorrow’s anti-patterns”.

If Conway’s law applies the how we set up and organise teams should either be aligned to the architecture of the applicaiton or system being developed or application/system architecture will shift to match the team structure.

The idea for lazybuilder came up during a recent coding dojo doing code kata.

After a long wait CODE keyboards are available again and I received mine last night.

Browsing some blogs recently I came across some interesting C++11 lambda code and thought it would be cool to try it out for myself.

I have been spending time recently writing command line apps in C++11.

I am about to embark on a new Java project so I thought I would take a look at the current state of build tools for Java projects.

I like to commit code frequently when working on a project.

Continuous Deployment is the act of automatically deploying an application every time the build is successful.

Following up on the [next_permutation]({% post_url 2013-08-03-next_permutation %}) from a couple of weeks ago word finder uses next_permutation to find words in character sequences.