The IT industry is either taking giant leaps ahead or it's in deep turmoil. On the one hand we're pushing forward, reinventing the way that we build software and striving for craftsmanship at every turn. On the other though, we're continually forgetting the good of the past and software teams are still screwing up on an alarmingly regular basis.
Software architecture plays a pivotal role in the delivery of successful software yet it's frustratingly neglected by many teams. Whether performed by one person or shared amongst the team, the architecture role exists on even the most agile of teams yet the balance of up front and evolutionary thinking often reflects aspiration rather than reality.
If we really do want to succeed, we need to get over our fascination with shiny new things and starting asking some questions. Does agile need architecture or does architecture actually need agile? Have we forgotten more about good software design than we've learnt in recent years? Is emergent design really just about foolishly hoping for the best? Does any of this matter if we're not fostering the software architects of tomorrow? How do we move from frustration to serenity?
YOU MAY ALSO LIKE:
- The Lost Art of Software Design (SkillsCast recorded in October 2021)
- Domain Models in Practice with Marco Heimeshoff (Online Course on 8th - 12th November 2021)
- Certified Agile Team Coaching with Ben Maynard & Jon Spruce (Online Course on 15th - 18th November 2021)
- YOW! December 2021 (Online Conference on 30th November - 1st December 2021)
- Domain-Driven Design Hands-On Workshop: A DDD-traineeship at "Carries Cars" (Online Meetup on 26th October 2021)
- Merging Kanplexity™ with LeSS (Online Meetup on 2nd November 2021)
- Understanding Microservices: A Guide for the Monolithic Developer (SkillsCast recorded in October 2021)
- F# Gives You Superpowers (SkillsCast recorded in October 2021)