Global Dev Experts’ Post

𝗦𝗸𝗶𝗹𝗹𝘀 𝗼𝗳 𝗮 𝗚𝗿𝗲𝗮𝘁 𝗦𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗔𝗿𝗰𝗵𝗶𝘁𝗲𝗰𝘁 A great software architect is more than just a master of programming languages or architectural patterns. They possess a holistic skill set that encompasses technical prowess, analytical thinking, communication finesse, and a deep understanding of both the business context and user experience. Their abilities to navigate complex challenges, lead teams, and align technical decisions with overarching objectives make them indispensable in the development process. https://buff.ly/3Y3r59X

Simplifying the Software Architecture Complexity: Initially, I assumed this ability naturally developed in all programmers over time. However, as I've taken on more leadership roles, I've realized it's a distinct skill. Some individuals can create mental models of complex domains when exposed to them. They can then communicate these models to others, highlighting crucial details while omitting irrelevant information. When asked about edge cases, they can use their mental model to explain expected system behavior or identify gaps in their understanding. Others lack this ability. I've observed this skill in various roles - Architects, Quality Engineers, Product Managers, and successful Executives. It doesn't necessarily correlate with Technical Expertise, but I believe it's crucial for Software Engineers aspiring to be Software Architects.

Having a super hard time learning - What it means to test without mocks, - Test containers and DBs for testing - E2E and integration tests without mocks The ratio of real engineering content vs rookie content over Youtube is so low, and even on the advanced side, mostly it's system design, not writing code. System design is okay, but I don't get to make big architectural decisions at my org, it's architect work, I only need enough info to efficiently put my feature on the top of existing architecture. The real thing I need is, how to sleep better when I send my code to prod.

 𝐁𝐨𝐨𝐤𝐬 𝐟𝐨𝐫 𝐬𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐞𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬 𝐚𝐧𝐝 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐬 1. 𝐂𝐥𝐞𝐚𝐧 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: A Craftsman's Guide to Software Structure and Design by Robert C. Martin    - Explore principles and practices for designing maintainable, scalable, and robust software architectures. 2. 𝐓𝐡𝐞 𝐏𝐫𝐚𝐠𝐦𝐚𝐭𝐢𝐜 𝐏𝐫𝐨𝐠𝐫𝐚𝐦𝐦𝐞𝐫: From Journeyman to Master by Andrew Hunt and David Thomas    - Uncover pragmatic approaches and timeless advice for becoming an effective and efficient software developer. 3. 𝐂𝐨𝐝𝐞 𝐂𝐨𝐦𝐩𝐥𝐞𝐭𝐞: A Practical Handbook of Software Construction by Steve McConnell    - Dive deep into the art and science of software construction, covering principles, techniques, and best practices. 4. 𝐃𝐞𝐬𝐢𝐠𝐧 𝐏𝐚𝐭𝐭𝐞𝐫𝐧𝐬: Elements of Reusable Object-Oriented Software by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides    - Master essential design patterns to solve common problems and improve the flexibility and maintainability of your codebase. 5. 𝐌𝐲𝐭𝐡𝐢𝐜𝐚𝐥 𝐌𝐚𝐧-𝐌𝐨𝐧𝐭𝐡: The Software Project Management Book by Fred Brooks    - Delve into the timeless insights on software project management, productivity, and team dynamics from a legendary figure in the field. 6. 𝐓𝐡𝐞 𝐀𝐫𝐭 𝐨𝐟 𝐀𝐠𝐢𝐥𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 by James Shore and Shane Warden    - Learn practical strategies and techniques for adopting agile practices and delivering high-quality software in a dynamic environment. 7. 𝐑𝐞𝐟𝐚𝐜𝐭𝐨𝐫𝐢𝐧𝐠: Improving the Design of Existing Code by Martin Fowler    - Discover methods for restructuring existing codebases to improve readability, maintainability, and extensibility. 8. 𝐃𝐨𝐦𝐚𝐢𝐧-𝐃𝐫𝐢𝐯𝐞𝐧 𝐃𝐞𝐬𝐢𝐠𝐧: Tackling Complexity in the Heart of Software by Eric Evans    - Explore domain-driven design principles and patterns for creating software that reflects real-world domains and business requirements. These books serve as indispensable resources for software professionals, offering a wealth of knowledge and practical guidance to help navigate the complexities of software development and architecture. Join my friend's vibrant DevOps community ⏬ https://lnkd.in/g7fEqzj3 Follow Ashish Sahu for more content #softwareengineering #systemdesign #engineering #coder #coding #programming #sql #youtube

 𝐁𝐨𝐨𝐤𝐬 𝐟𝐨𝐫 𝐬𝐨𝐟𝐭𝐰𝐚𝐫𝐞 𝐞𝐧𝐠𝐢𝐧𝐞𝐞𝐫𝐬 𝐚𝐧𝐝 𝐚𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐬 1. 𝐂𝐥𝐞𝐚𝐧 𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐞: A Craftsman's Guide to Software Structure and Design by Robert C. Martin    - Explore principles and practices for designing maintainable, scalable, and robust software architectures. 2. 𝐓𝐡𝐞 𝐏𝐫𝐚𝐠𝐦𝐚𝐭𝐢𝐜 𝐏𝐫𝐨𝐠𝐫𝐚𝐦𝐦𝐞𝐫: From Journeyman to Master by Andrew Hunt and David Thomas    - Uncover pragmatic approaches and timeless advice for becoming an effective and efficient software developer. 3. 𝐂𝐨𝐝𝐞 𝐂𝐨𝐦𝐩𝐥𝐞𝐭𝐞: A Practical Handbook of Software Construction by Steve McConnell    - Dive deep into the art and science of software construction, covering principles, techniques, and best practices. 4. 𝐃𝐞𝐬𝐢𝐠𝐧 𝐏𝐚𝐭𝐭𝐞𝐫𝐧𝐬: Elements of Reusable Object-Oriented Software by Erich Gamma, Richard Helm, Ralph Johnson, and John Vlissides    - Master essential design patterns to solve common problems and improve the flexibility and maintainability of your codebase. 5. 𝐌𝐲𝐭𝐡𝐢𝐜𝐚𝐥 𝐌𝐚𝐧-𝐌𝐨𝐧𝐭𝐡: The Software Project Management Book by Fred Brooks    - Delve into the timeless insights on software project management, productivity, and team dynamics from a legendary figure in the field. 6. 𝐓𝐡𝐞 𝐀𝐫𝐭 𝐨𝐟 𝐀𝐠𝐢𝐥𝐞 𝐃𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 by James Shore and Shane Warden    - Learn practical strategies and techniques for adopting agile practices and delivering high-quality software in a dynamic environment. 7. 𝐑𝐞𝐟𝐚𝐜𝐭𝐨𝐫𝐢𝐧𝐠: Improving the Design of Existing Code by Martin Fowler    - Discover methods for restructuring existing codebases to improve readability, maintainability, and extensibility. 8. 𝐃𝐨𝐦𝐚𝐢𝐧-𝐃𝐫𝐢𝐯𝐞𝐧 𝐃𝐞𝐬𝐢𝐠𝐧: Tackling Complexity in the Heart of Software by Eric Evans    - Explore domain-driven design principles and patterns for creating software that reflects real-world domains and business requirements. These books serve as indispensable resources for software professionals, offering a wealth of knowledge and practical guidance to help navigate the complexities of software development and architecture. Join my friend's vibrant DevOps community ⏬ https://lnkd.in/g7fEqzj3 Follow Ashish Sahu for more content #softwareengineering #systemdesign #engineering #coder #coding #programming #sql #youtube

Starting software development without a formal architecture often leads developers to fall back on a default layered approach, which can morph into a chaotic "big ball of mud." In this common scenario, the code lacks organization, with unclear roles and relationships, making the application difficult to modify and scale. It also becomes challenging to assess the application's performance and responsiveness. Selecting a specific architectural pattern is vital, as each has inherent strengths and weaknesses that impact scalability, agility, and functionality. I'll be dedicating this weekend to delve deep in software architecture patterns. As engineers/architects, our decisions must be well-informed and aligned with the project's business objectives to ensure the chosen architecture supports the application's demands effectively. Thank you Marvelous Solomon for sharing this book.

#SW #FW #Developer #CD #XP Everybody in the SW Industry that wants build better and faster should read this book, and have a fast and rielable Continuous Delivery pipeline Included Embedded SW and FW

Today I will tell you about a book that everyone in the software engineering industry must read, including software engineers, project managers, and everyone else involved in the process of building software. The book is called Accelerate and it's written by Nicole Forsgren , Jez Humble , and Gene Kim. It was first recommended to me by Dave Farley in one of our discussions. I immediately bought a copy and it was definitely the right thing to do. This book talks about one of the biggest scientific studies done on the productivity of software engineering organizations and the quality of its products. What it found is really interesting. While many organizations believe that you can either get a high quality deffect-free product or a fast delivery speed, it's not the case at all. Organizations and teams that utilize continuous delivery practices and put out production releases at frequent intervals tend to end up with better quality products. You don't necessarily have to go all the way to Extreme Programming, get rid of pull requests, avoid feature branches, etc. Branches and PRs may be fine. However, one of the biggest conclusions from this study is that you should have a reliable CI/CD pipeline and you should merge your code changes into the trunk daily. What you definitely don't need are the PRs that take days to merge and a long multi-layered change approval process. But the best thing about this book is that, for a book of this kind, it's surprisingly easy to read. I read the whole thing in two sittings.

Just finished Dave Farley's "new" book. HIGHLY recommend. SO many great points, though the TDD part is probably something where I am still not completely onboard. In my view the CI and high frequency delivery and resulting behaviour and processes actually realise most of the gains. TDD and granular unit tests may add to those gains, but I am still not entirely convinced of the impact of having a granular test suite actually provides enough value compared to the maintenance overhead. Assuming you write you code to be easily testable. Maybe TDD as a design tool and just delete the tests afterwards. I.e. TDD as scaffolding while building but most, if not all, removed after "finished" building. Anyone know of people trying that? https://lnkd.in/d5H4gmJQ

3 Things I Wish I Knew Before Becoming a Software Architect. In the video snippet taken from long video , Ahsan Alam, Ram Ramamoorthy and I discuss what things we wish we had known before becoming software architects. 1. The Paramount Importance of Business Knowledge: It’s about solving business problems and providing business solutions, not just technical fixes. 2. The Art of Selling Your Solutions: Learn how to effectively communicate and sell your architectural solutions to management, business stakeholders, and technical implementers. 3. The Value of People: Understand the importance of building and enhancing your interpersonal skills to thrive in an architectural role. 📺 [Watch the Video Snippet Here] https://lnkd.in/gzWkyaVa 📽️ [Here’s the Full Video Link] Blueprints to Success: How to become a Software Architect https://lnkd.in/gqQ6Hy8W This content is not just a reflection of our journeys but a roadmap for aspiring architects who aim to build meaningful, solution-oriented careers in technology. It’s about navigating the business landscape, understanding the human element in tech roles, and mastering the art of persuasion and communication. #SoftwareArchitecture #BusinessAcumen #Leadership #CareerDevelopment #TechnologyLeadership