liveBook · Manning

Software architect

As explained in Lead Developer Career Guide

A professional who designs the high-level structure, technical direction, and integration of software systems.

A software architect plans the technical structure of a system and how to build it, including how its components connect. section 2.1.3

Unlike a lead developer, an architect may plan without implementing the system or writing code; some organizations combine the roles. section 2.1.3

Table 2.2 Lead developer vs. lead architect skills (view table figure)

Lead developer

Lead architect

Create technical architecture diagrams

✓

✓

Explain how the technical architecture will be built

✓

✓

Illustrate component/module/feature relationships

✓

✓

Estimate technical tasks

✓

Develop infrastructure and features

✓

Mentor the development team

✓

Compare which planning, implementation, estimation, and mentoring responsibilities are shared or assigned to each role. section 2.1.3

How Lead Developer Career Guide covers it

How deep it goes
Details architecture diagrams and build planning, while distinguishing the architect’s expertise from a lead developer’s broader technical expertise.
Examples
Uses diagrams of component connections and a skills comparison between lead architects and lead developers.
What you can do after
Understand how architecture planning differs from implementation and coding responsibilities.
How it connects
Contrasts the lead architect with the lead developer, who also executes plans and writes code.

Also explained in

Compare how 2 books explain software architect →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Lead Developer Career Guide. The section links point to the parts of the book it draws on.