What do architecture and software engineering have in common?

There's a problem to solve, ideas to implement, and the result is often a usable artifact.

What has always put me off architecture is its slow nature. It might take years for big projects to go from ideation to design to construction to use. Yet tiny interventions (think small retrofits and interior designs) can be swift.

That's the joy of coding; you can formalize an idea into a usable prototype in a matter of minutes. Write code, run your program, then visualize and interact with your changes. When programming simple and interactive systems, you can see and use a functioning prototype from the early development stages.

Of course, I don't mean that it takes minutes to create complex programs, but that coding is a dynamic process that provides feedback as you make changes. Whereas large software projects might resemble architecture projects' slowness, small-scale architectural interventions might be as fun as prototyping with code.