Coding the Architecture - book tag

The role of a hands-on software architect

Wed, 10 Sep 2008 17:33:00 GMT

Becoming a software architect isn't something that simply happens overnight or with a promotion. It's a role, not a rank. It's an evolutionary process where you'll gradually gain the experience and confidence that you need to undertake the role. While the term "software developer" is fairly well understood, "software architect" isn't. This essay looks at the role I believe a good hands-on software architect should play on any software project.

Read the full essay in our book.

Mind the gap

Fri, 02 May 2008 10:58:03 GMT

Our industry has a love/hate relationship with the software architect role, with many organisations dismissing it because of their negative experiences of architects that dictate from "ivory towers" and aren't engaged with the actual task of building working software. This reputation is damaging the IT industry and inhibiting project success. Things need to change. This essay looks at the gap between software developers and software architects, offering some suggestions on how to reduce this gap and ensure projects are driven to a successful conclusion.

Read the full essay in our book.

What is architecture?

Fri, 02 May 2008 10:53:54 GMT

Architecture is a widely-used term within software development yet is very hard to define rigorously. Indeed, it changes meaning from domain to domain, company to company, project to project and even from employee to employee.

Read the full essay in our book.