Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Save more on your purchases now! discount-offer-chevron-icon
Savings automatically calculated. No voucher code required.
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Software Architecture for Web Developers

You're reading from   Software Architecture for Web Developers An introductory guide for developers striving to take the first steps toward software architecture or just looking to grow as professionals

Arrow left icon
Product type Paperback
Published in Oct 2022
Publisher Packt
ISBN-13 9781803237916
Length 116 pages
Edition 1st Edition
Languages
Arrow right icon
Author (1):
Arrow left icon
Mihaela Roxana Ghidersa Mihaela Roxana Ghidersa
Author Profile Icon Mihaela Roxana Ghidersa
Mihaela Roxana Ghidersa
Arrow right icon
View More author details
Toc

Table of Contents (15) Chapters Close

Preface 1. Part 1 – Getting the Grasp of Architecture
2. Chapter 1: The Role of Architecture FREE CHAPTER 3. Chapter 2: Diving into Some Common Architectural Patterns 4. Chapter 3: Myths about Architecture 5. Chapter 4: Discussing What Good Architecture Is 6. Chapter 5: Design versus Architecture 7. Part 2 – Architect: From Title to Role
8. Chapter 6: Types of Architects and Their Focus 9. Chapter 7: Leveraging Soft Skills 10. Part 3 – From Developer to Architect
11. Chapter 8: Who Codes and Who “Architects”? 12. Chapter 9: Break the Rules 13. Index 14. Other Books You May Enjoy

Leveraging Soft Skills

Since I first joined the technical world as an developer and learned the inner workings of its teams, the role of an architect was always presented as someone that had little to no interaction with the development team, someone whose decisions couldn’t be challenged, and someone who carried out the essential tasks for the product.

As a junior and in my first project ever, I didn’t even get the honor of meeting the architect. I worked on the project for over a year. So, yeah, you can imagine that when I later switched teams, and the architect had the desk closer to mine, I understood the difference between a title and a role.

The role of an architect is to be a leader most of the time and therefore, they have to work on having the best communication skills. They have to know how to shape their speech to be understood by both the technical team and the businesspeople.

In this chapter, we will discuss some of the main areas in which depending...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime