Dive deeper into people skills in the fourth video of this acclaimed series on software architecture fundamentals from Neal Ford and Mark Richards. Programming and technology is only one side of a software architect’s skillset. Along with being an excellent developer, you also have to be a communicator and a leader. People skills help you work well within a larger corporate structure, manage teams, and ensure that technology is a first-level concern at your company.
In this video, you’ll learn how to:
- Control various types of architecture boundaries and the personalities that form them
- Work with members of your architecture team by using techniques and best practices
- Cope with meetings imposed on you and meetings you impose on others
- Become an effective technical leader by honing your skills
- Delve into the relationship between software architecture, team structure, and the impact of Conway’s Law when designing systems
- Use negotiating skills to drive consensus and understand tradeoffs with stakeholders, technologists, and team members
- Build your personal technology radar as a way to investigate new technologies in a structured way
- Crowd-source technology decisions within your organization by building a companywide technology radar
About the presenters
Neal is Director, Software Architect, and Meme Wrangler at ThoughtWorks, a global IT consultancy with an exclusive focus on end-to-end software development and delivery. Before joining ThoughtWorks, Neal was the Chief Technology Officer at The DSW Group, Ltd., a nationally recognized training and development firm.
Mark Richards is an experienced hands-on software architect involved in the architecture, design, and implementation of microservices architectures, service oriented architectures, and distributed systems in J2EE and other technologies.
About the O’Reilly Software Architecture Series
Clearing a path from developer to architect and enriching that path once you arrive.
Software architecture is a fast-moving, multidisciplinary subject where entire suites of "best practices" become obsolete practically overnight. No single path or curriculum exists, and different types of architecture—application, integration, enterprise—require different subject emphasis. Whether you’re at the outset of a career as an architect or in the midst of such a career, series editor Neal Ford has curated this collection of tools and guides for aspiring and seasoned architects alike.