Brandon BrysonIntellectual Control, Developer Abstraction, and TestingEarlier this year I attended the O’Reilly Software Architecture Conference in NY. One of the keynotes was presented by George Fairbanks on…Apr 27, 2020Apr 27, 2020
Brandon BrysonAssessing Legacy Code Using Chesterton’s FenceI recently read a great article on second-order thinking that really resonated with me with regard to software development, specifically…Apr 13, 2020Apr 13, 2020
Brandon BrysonImproving with RetrospectivesI was looking through some old notes and found this great quote that I had captured from an InfoQ presentation on agile mindset by Shane…Apr 2, 2018Apr 2, 2018
Brandon BrysonIntegration Tests — Broad or Narrow?Martin Fowler recently released a new blog describing the concept of Integration Tests and how the term is used in different ways. It is a…Jan 29, 2018Jan 29, 2018
Brandon BrysonMeetings are Not Agile CollaborationI started this topic thinking about all the time technologists spend in meetings and how they impact agile delivery. I’ve come to believe…Nov 6, 2017Nov 6, 2017
Brandon BrysonRemove Dead CodeI enjoyed this article on the importance of removing dead code as part of managing technical debt. In the article, which is an interview…Oct 16, 2017Oct 16, 2017
Brandon BrysonArchitectural Simplicity Through OptionsI’ve written lately about driving architectural simplicity. One driver of simplicity that I covered in the article was understanding…Oct 2, 2017Oct 2, 2017
Brandon BrysonCode Review as Mutual LearningDan North had a great tweet the other day regarding opportunity to learn from code reviews:Sep 18, 2017Sep 18, 2017
Brandon BrysonDriving Architectural SimplicityI just posted a new article on InfoQ:Aug 20, 2017Aug 20, 2017
Brandon BrysonTechnical Debt is like a messy kitchenI saw a great metaphor for technical debt the other day in a presentation on agile architecture. The speaker likened technical debt to a…Aug 13, 2017Aug 13, 2017