Search icon CANCEL
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

Myth no.3: Architecture is not about coding

From what we’ve discussed, maybe with some exceptions, architecture is a part of the development process, the part that is later taken over and implemented by the team. Architecture is not about forgetting about implementation details and getting drowned in abstractions but about keeping them balanced. I think we become good architects when moving carefully from one to the other.

Software architecture is all about understanding how the system works as a whole. Going from contributing to the architecture to being responsible and making decisions to grow a product is a process. The first step of this process is being honest with our experience level and what areas we need to focus on to proceed to the next level as professionals.

We need to be aware of the differences that help us to evolve. For example, as a programmer, your constant focus is on details, while architects focus most of their time on the whole picture, and most...

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