Reading Review

Scaling Architecture Conversationally clearly and concisely explains how and why architecture is more of a facilitated process than a top-down decision process.

Checklist Manifesto paints an facinating journey of a surgeon who discovered checklists. The book explores checklists across industries and applications, but one lesson pervades them all: use checklists to distribute power.

I read that stuckness is not a bad thing. It is avoiding our stuckness that is the problem. I think living with stuckness is part of why duck docs are so good.

Code That Fits in Your Head tackles a problem dear to my heart. Mark Seemann realized good software engineering practices are out there, but it’s hard to connect the dots between scattered sources.

Following software to it’s orgins with Alan Turing reveals some interesting trends in how ideas cycle.

Small teaching is an engaging and practical condensation of learning research into an accessible read. The book is oriented toward teachers, but is meaningful for anyone who wants to learn more effectively or understand how to share ideas.

The Software Engineering Body of Knowledge (SWEBOK) levels up our industry. It collects evidence-based standard practices that every developer is expected to know. This post will establish some background for SWEBOK, cover my high-level takeaways.

Steve McConnell is best known for Code Complete. Professional Software Development is a much lighter packaging of McConnell’s core philosophy. It establishes up a well-founded view on what the software industry is and could be. Here I’ll highlight some of my key takeaways from the book.

It’s easy to see how Domain Driven Design (DDD) by Eric Evans was such a seminal work. It presents a holistic development process that seems to have predicted the next two decades of development trends. Here are some of my key takeaways from the book.

Measurement – The types and amount of insights we extract on our students current understanding