Hello! This is the website for Graham Brooks: architect, developer and sometime blogger.
Disclaimer: This is a personal weblog. The opinions expressed here represent my own and not those of my employer (LexisNexis).My thoughts and opinions change over time as I learn. This weblog is intended to provide a semi-permanent record of these thoughts and is for informational purposes only.
Blog post authored by AI - with a little prompting.
Adding your own custom command line arguments to your Bazel build for a cleaner interface.
Creating text and document fingerprints that can be used to find similar documents or group text by similarity.
Building and installing locally with Bazel. A simple rule example.
Working with go projects using Bazel. Builing in and out of a container.
Prefer technical health over technical debt as a metaphor for developer practice changes for better code.
Orchestration and Choreography are often confused. This is how I think of them.
The Builder pattern has become very popular over the last few years but there is a growning tendency to use it everywhere. Here are some of the problems and alternatives that you might find a better fit.
Keeping a domain model is hard. Implementing a anti-corruption layer with the right separation of concerns can help.