Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
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

Collaboration

There’s a difference between management and leadership. Management is about the tasks and concrete steps to achieving the end goal.

Leadership is about people, who you are and how you get to those people, how to inspire them, and how you show up for them.

An architect should be a leader that has a better overview, experience in diverse areas, and insights into both functional and non-functional requirements in order to contribute to the growth of the team around them. An architect should understand that each team member comes with different levels of knowledge about architecture, as it’s their responsibility to ensure common understanding.

Everyone on the development team needs to see the essence of software architecture and the consequences of not thinking about it before they start talking about things such as architecture description languages and evaluation methods. My own experience has empowered me to say that I even see the need for the...

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
Banner background image