Summary: Personal reading reactions, book notes, and reposts shared on LinkedIn. Organized by theme. Each entry captures what Noah took away from the source, not just that he read it — the value here is the synthesis between the source and his own work.

Book reactions — software & technology

Lean Software Development: An Agile Toolkit — Mary & Tom Poppendieck (2003)

"Impressive how the core lean principles — Eliminate Waste, Amplify Learning, Decide as Late as Possible, Deliver as Fast as Possible, Empower the Team, Build Integrity In — remain deeply relevant in today's Agile software development landscape. All in a book originally published in 2003, right around the time when the Agile Manifesto and Scrum framework emerged."

The seven Poppendieck principles are still load-bearing two decades later. The lineage runs straight from lean manufacturing into modern agile delivery, and the principles outlived the specific frameworks built on top of them. Connects to Neither 'Agile' nor Architecture are Going Anywhere and Framework vs Methodology vs Best Practice Key Differences in Architecture.

Practical Guide to Structured Systems Design — Meilir Page-Jones (1980, 2nd ed. 1988)

"A timeless classic that continues to shine over thirty years later. Its emphasis on modular design and structured analysis techniques remains invaluable for modern software development."

Modular design and structured analysis predate Agile, predate microservices, predate everything in the current methodology debate — and survived all of them. Connects to I Haven't Seen a New Software Development Problem in Thirty Years (different author, same observation) and DDD Model Thinking Made Easy and Practical Using Common-Sense Architectural Notations.

The Software Architect Elevator — Gregor Hohpe

"Excellent exploration of architects' evolving role in agile environments."

Foundational read for the architect-mindset cluster — connects to Zang Jing Ge The Way of the Architect, The Hands-On Architect Bridging Vision and Execution, Being an architect isn't the sum of skills. It's the product, Maker vs Multiplier.

Book reactions — leadership & culture

No Rules Rules: Netflix and the Culture of Reinvention — Reed Hastings & Erin Meyer

"Delves into Netflix's success formula of high-talent density, unfiltered candor, and autonomy (removing controls), leading to its cutting-edge achievements. While the title suggests a lack of rules, the reality is nuanced — Netflix operates under unconventional rules."

The book's framework — the freedom & responsibility vs. rules & process spectrum — is more durable than its specific Netflix prescriptions. Noah's caution: the formula isn't universally applicable, especially in profit-driven vs. purpose-driven organizations. Connects to Symptoms of a broken product culture and Adventures in ignorance.

Zero to One — Peter Thiel

"A compelling classic with bold arguments on building monopolies, uncovering the 'secrets' of success, and shaping a founder's mindset. Highly relevant not only to startups and businesses, but also to building a personal brand. While some ideological nuances may feel dated against the temporal dynamics of the past decade, it remains a thought-provoking and worthwhile read."

The "secrets" framing — that the most valuable ideas are the ones nobody else is pursuing — applies as cleanly to architectural choices and personal brand as it does to startups.

Principles for Dealing with the Changing World Order — Ray Dalio

"What a great book to close out 2025, and certainly one of the most thought-provoking books I've read in recent years. Key takeaway: history doesn't repeat itself exactly, but it rhymes in an upward spiral of productivity, GDP, and human well-being."

This reading got its own wiki article: Principles for Dealing with the Changing World Order — the anchor for the entire geopolitics cluster.

Idea reactions & quotes

"Ideas are commodity. Execution of them is not." — Michael Dell (paired with Steve Jobs on the disease of overvaluing ideas)

Steve Jobs's framing inside the post is sharper than the headline quote:

"It's the disease of thinking that a really great idea is 90 percent of the work… there's just a tremendous amount of craftsmanship in-between a great idea and a great product, and as you evolve that great idea it changes and grows… designing a product is keeping 5,000 things in your brain… It's that process that is the magic."

Connects to The Hands-On Architect Bridging Vision and Execution and Maker vs Multiplier — the idea isn't the artifact, the craftsmanship-in-between is.

Ray Dalio — "Digital Twin of One's Thinking" (Digital Ray)

"What really caught my attention is the idea of a Digital Twin of One's Thinking. With how fast AI is evolving — especially with more agentic capabilities and skill-based systems — it's been pushing my thinking in this space. Recently, I've started experimenting with building AI 'skills' that align with my own professional and personal principles. To me, this isn't just about efficiency. It's about scaling how we think, embedding principles into decision-making, and extending the impact of knowledge workers beyond traditional limits."

This is the principle behind Noah's own AI-skills experimentation — see @ttgcacustom-ai-code-analyzer and VS Code Custom AI SE Assistant. Also connects to The Learning Loop and LLMs and to Who Over What (same author, decision-architecture lens).

Ray Dalio — "Who Over What" principle

"Often times, it's not about the size or type of the job — it's about who does the work."

Noah's comment on Dalio's post got its own wiki article: Who Over What.

Benny Cheung — "Philosophy is the most underrated engineering skill"

"This got me thinking more about ontology in AI systems and engineering, a term that's becoming increasingly relevant to building with LLMs and data-driven architectures. When we work with knowledge graphs or semantic layers, one could argue this is applied philosophy in practice: defining entities, structuring relationships, deciding what 'exists' in your business. LLMs generate probabilistic outputs. Ontologies provide structure and shared meaning."

Cheung's broader argument — that fundamental AI problems (hallucinations, understanding, information loss, computational limits) were already diagnosed by Kant, Wittgenstein, Laozi, and Godel/Turing/Cook — reframes ontology work as the engineering corollary to philosophy. See Knowledge Graphs and the Five Waypoints for Cheung's structural framing of the same observation.

Methodology reactions

Spec-Driven Development Isn't Broken. It Will Collapse — Kapil Viren Ahuja

"Very insightful read I've come across recently on AI-native software delivery. As we move from deterministic / imperative programming toward probabilistic and agentic systems, disciplined software engineering does not disappear. While AI may commoditize implementation, the need for architecture thinking, delivery methodology, governance, and institutional memory matters more than ever in driving predictable and repeatable outcomes at enterprise scale. And the methodology itself should increasingly become codified as part of the system."

This is the central thesis of the wiki article Spec-Driven Development Will Collapse — Noah's framing adds the "methodology codified as part of the system" angle, which connects to how he's building his own intent-driven tooling.

Architecture-as-a-Service — Reema K. / Reema's repost

"Certainly something to ponder: leveraging Architecture-as-a-Service as the delivery model and productizing architecture as a repeatable enterprise capability."

Got its own wiki article: Architecture-as-a-Service.

Public-sector AI reactions

Alberta's $54 million → $2.64 million AI rebuild — Nate Glubish

"A truly inspiring story of AI in action within Alberta's public sector."

The full story is in They Said It Would Cost $54 Million. We Said "No Thanks.". Noah's repost is the connective tissue — this is exactly the kind of public-sector outcome the State of digital government review and Impact Engineering a review articles call for.