Five things every developer should know about software architecture by Simon Brown

Поділитися
Вставка
  • Опубліковано 12 лют 2024
  • The software development industry has made huge leaps in recent years, yet software development teams are often more chaotic than they are self-organizing, with the resulting code being more of a mess than was perhaps anticipated. Successful software projects aren't just about good code, and sometimes you need to step away from the IDE for a few moments to see the bigger picture. This aimed at software developers who want to learn more about software architecture, technical leadership and the balance with agility.
    Simon Brown
    Recorded at Jfokus 2024 in Stockholm 7th of february
    www.jfokus.se

КОМЕНТАРІ • 1

  • @IsmaelDemiddel
    @IsmaelDemiddel Місяць тому

    The last slide with the overview was not that clear, so here are the 5 points:
    1. Software architecture isn't about big design up front.
    2. Every team needs technical leadership.
    3. The software architecture role is about coding, coaching and collaboration
    4. You don't need to use UML.
    5. A good software architecture enables agility.