A working library · A Make Bold Solutions publication
Notes on Azure, .NET, AI-assisted delivery, and architecture—filed by subject, connected by the questions behind the work.
148articles to explore
Search spans article titles, summaries, and subjects. Use ⌘K to jump straight to the search.
Where I think out loud about architecture, AI, and what building software actually teaches you.
My credibility comes from long-running systems, production trade-offs, and the record of writing and open-source work that documents how those decisions are made.
Most architecture work is not about choosing a tool. It is about making constraints visible, deciding where complexity belongs, and leaving the next team with a system they can reason about.
Exploring applied AI, machine learning, and the practical limits of intelligent systems in working software.
Learn moreWorking through Python, data analysis, visualization, and machine learning from a .NET developer's perspective.
Learn moreDesigning Azure-hosted applications, APIs, data flows, and integration patterns with reliability and operability in view.
Learn moreUsing AI tools inside bounded engineering workflows where requirements, review criteria, and architecture decisions remain explicit.
Learn moreHelping teams decide what to keep, what to replace, and how to move without losing the business context embedded in existing systems.
Learn moreApplying Project Mechanics to clarify delivery states, accountability, change management, and leadership decisions.
Learn moreBuilding and documenting small production-oriented systems that make architecture trade-offs visible.
Learn moreTurning implementation work into clear technical notes that help architects, engineers, and stakeholders evaluate decisions.
Learn moreA live set of applications and experiments that show how shared architecture behaves across different frontends and workflows.
Learn moreThe shortest paths into the work: background, frameworks, systems, applications, writing, and source code.
Professional background, architecture focus, and operating philosophy.
OpenThe Adaptive System Life Cycle Development model behind DevSpark.
OpenHow specifications, constitutions, and review gates shape AI-assisted work.
OpenProduction systems and reference implementations from the portfolio.
OpenThe live showcase for applications I have developed across the Spark ecosystem.
OpenThe company my wife and I founded, now live at makeboldsolutions.com.
OpenArchitecture, AI, .NET, Azure, and engineering notes from the blog.
OpenRepository activity, source code, and open-source work.
OpenEach system holds some constraints constant and changes others. MakeBoldSpark is the live showcase for the applications I have developed; this section keeps the architecture evidence close to the reasoning behind those systems.
Visit MakeBoldSparkSpec, build, validate, evolve
DevSpark is an implementation of Adaptive System Life Cycle Development (ASLCD), a full lifecycle model for building software with AI collaborators. It carries intent from specification through implementation, validation, and evolution.
Operational prompt workflows for real applications
PromptSpark.Chat explores how prompt systems behave when they become part of an application workflow. It focuses on structured conversations, reusable prompt assets, and practical integration patterns.
Documentation that becomes implementation context
DocSpecSpark frames documentation as a working system asset instead of a static afterthought. It supports the bridge from architectural intent to implementation-ready specifications.
A controlled frontend architecture comparison
TailwindSpark is a React and Tailwind implementation that consumes shared service patterns while emphasizing composition and utility-first design. Its value is clearest when compared with BootstrapSpark against the same architectural constraints.
In 2002, I founded Project Mechanics LLC to document what I'd learned about delivering complex projects. Over two decades of refinement — across consulting, enterprise, and healthcare — those lessons became a complete methodology.
It covers the full project life cycle, portfolio governance, leadership, change management, and conflict resolution. Not a textbook — a working framework I've used on real engagements.
Explore the methodologySix core disciplines: