Articles & Blogs
What's the best way to prevent software disasters? This article proposes that we should look to the X-Ray as a metaphor for analyzing our software systems.
Ginny Hendry argues that the code you leave behind is your legacy, which is why you should code with pride.
The folks over at Stride give four different scenarios to help figure out when it makes business sense to pay down technical debt.
What to shantytowns have in common with spaghetti code? More than you'd think. In this paper, Brian Foote and Joseph Yoder explore "casually, even haphazardly, structured systems", which they call the "Big Ball of Mud".