This video talks about how coding, design, and architecture are all part of one continuous process, not separate things. The speaker mentions Gregor Hope, who also believes these concepts are intertwined but uses different words. Both agree that these roles are about more than just technology; they connect business goals with how to achieve them. The speaker really likes Gregor's idea of an "architect elevator" that goes from the engine room to the boardroom.

Key Takeaways

Coding, design, and architecture are not distinct but rather a continuum with blurry boundaries.

The speaker and Gregor Hope often express similar ideas, with the speaker using terms like 'software engineers' and Gregor using 'architects.'

Both software engineering and architecture involve more than just technical aspects.

These roles bridge the gap between what needs to be achieved and how to achieve it.

The speaker finds Gregor's analogy of the 'architect elevator' from engine room to boardroom very insightful.

0:00 As I've said before, I think that

0:02 there's no real distinction between

0:04 coding, design, and architecture. This

0:07 is a continuum. The boundaries that

0:09 separate all three of these things are

0:11 rather blurry and indistinct. I was

0:13 struck in my conversation with Gregor

0:15 Hope about how much he and I often

0:17 express the same ideas, but using

0:19 slightly different language. He tends to

0:20 talk more in terms of architects and

0:23 architecture, and I tend to talk more in

0:26 terms of software engineers and software

0:28 engineering. Both though are about much

0:31 more than only the technical bits. Both

0:34 bridge the gap between what we are

0:36 trying to achieve and what it takes and

0:39 how we approach achieving it. I like

0:41 Greger's analogy of the architect

0:43 elevator from engine room to boardroom

0:45 quite a lot. And that leads me to the

0:48 first item on my list of three and

0:50 always my starting point in trying to

0:53 understand any new

This Changes How You See Software Architecture

Name: This Changes How You See Software Architecture
Channel: Continuous Delivery

Continuous Delivery

Key Takeaways

Start a conversation

This Changes How You See Software Architecture