Itβs striking how many organisations still struggle to identify quality problems as early as possible. I always find it fascinating what these older books can still teach us. Itβs a reminder that while technology evolves, the fundamentals of good software engineering remain timeless. Perhaps the real challenge isnβt learning new tools, but remembering the lessons weβve already been taught. (2/2)
A while back, I was fortunate enough to find a second-hand copy of *Object-Oriented Software Engineering: A Use Case Driven Approach* which was almost as good as new. First published in 1992, the knowledge it contains remains remarkably relevant today. For example, I came across this paragraph:
(1/2)
RE: https://mastodon.social/@chrisoldwood/116413059121230026
End-to-end is further than you think π
Struggling with brittle tests that slow you down? Join my πππ₯π₯-πππ₯ππ§πππ πππ¬π-ππ«π’π―ππ§ πππ―ππ₯π¨π©π¦ππ§πworkshop on πππ² 21-22, 2026 in Antwerp! Learn how to write reliable, maintainable tests that help you think about software design and prevent defects. Early -bird tickets are available until ππ©π«π’π₯ 19.
For more information: https://principal-it.eu/training/well-balanced-test-driven-development.html
Any government that isn't right now accelerating plans to transition to 100% clean, renewable energy is either:
a. Incompetent
b. In the pockets of people who'd rather they didn't
c. a & b
"The best engineering is always borne of constraints, and the constraint of our time places limits on the cognitive load of the system that weβre willing to accept. This is what drives us to make the system simpler, despite its essential complexity."
From 'The peril of laziness lost'
https://bcantrill.dtrace.org/2026/04/12/the-peril-of-laziness-lost/
Thomas
Prof. Stefan Rahmstorf
MostlyHarmless
Jason Gorman