Software Engineer at Signetik. UNL School of Computing and Raikes School Design Studio alumnus ('25).
In the last post, we discussed how to apply an architectural design mindset to the process of designing greenfield systems. In this post, we cover applying the same mindset to an existing legacy system. Tackling Architecture in a Legacy System Unfortunately, most of the time, developers do not get to
In the last post, we covered common design problems that you may encounter while working on software systems. We discussed common traps that seem like good solutions to those problems, as well as the correct methods for addressing the problems. In this part, we will explore how to apply the
In the last post, we covered some of the basics of architectural vocabulary and the importance of information hiding in component design. In this part, we will discuss some concrete patterns that frequently appear in software design and how to apply information hiding to them. In this context, pattern means
“It was the best of times, it was the worst of times… it was the spring of hope, it was the winter of despair…” — Charles Dickens on writing code, probably. Anyone who has worked with a software system for a significant amount of time knows that software is a double-edged