Ahmed Eldeeb’s Post

𝐀𝐫𝐜𝐡𝐢𝐭𝐞𝐜𝐭𝐮𝐫𝐚𝐥 𝐖𝐢𝐳𝐚𝐫𝐝𝐫𝐲: 𝐂𝐫𝐚𝐟𝐭𝐢𝐧𝐠 𝐒𝐲𝐬𝐭𝐞𝐦𝐬 𝐰𝐢𝐭𝐡 𝐚 𝐓𝐨𝐮𝐜𝐡 𝐨𝐟 𝐌𝐚𝐠𝐢𝐜! Ever wondered about the mystical realm of software architecture❓ It's like the grand storyteller, spinning tales about the high-level structures and dance of interactions within a system. 𝐁𝐮𝐭 it's not just about functionality – it dives deep into the organizational, technical, business, and quality aspects, casting a spell on the very skeleton of the system. 𝐍𝐨𝐰, let's talk 𝐝𝐞𝐬𝐢𝐠𝐧 – the hands-on enchantment that shapes the parts and components of a system. It's like being the master conductor orchestrating a symphony of code and modules. 𝐐𝐮𝐞𝐬𝐭𝐢𝐨𝐧𝐬 𝐚𝐛𝐨𝐮𝐧𝐝: ☑ How to slice the code into modules? ☑ What's the perfect organization dance for them? ☑ Which functionalities go where? ☑ And, oh, the design patterns – like choosing the right spell for a magical class "C"! 𝐉𝐨𝐢𝐧 𝐭𝐡𝐞 𝐚𝐝𝐯𝐞𝐧𝐭𝐮𝐫𝐞 𝐚𝐬 𝐰𝐞 𝐮𝐧𝐫𝐚𝐯𝐞𝐥 𝐭𝐡𝐞 𝐬𝐞𝐜𝐫𝐞𝐭𝐬: ✅ How do objects play together at runtime? ✅ What messages do they exchange, and how do we choreograph this mystical interaction? #systemdesign #systemsengineering #systemanalyst #systemarchitecture #softwarearchitecture #softwaredevelopment #softwareengineering #softwaredesign

Be honest: the way you're filtering design review feedback today is in a spreadsheet, right? Hey, we get it. Our rough estimation is that 99% of the engineering world is run on spreadsheets 😉 But, there's a better way. Engineering teams need to be able to: 👉 Filter design review feedback 👉 See those comments with all the accompanying metadata, like who created it? And who is this assigned to? 👉 Click any comment and be brought to the exact context of that comment Feedback filtering in a spreadsheet is Design Review 1.0 Real-time feedback filtering in the context of the model is Design Review 2.0 #engineeringdesignreview

I finally finished my free strategic Domain-Driven Design book! 📖 The idea came to my mind after discussions with conference audiences and colleagues. The question that was regularly repeated was: "Ok, that's theory. But how do we approach strategic DDD concepts in real life?"🤔 I started planning to write a free ebook to explain it from the practical approach based on a concrete, real-world example. The plan was to have it completed by the end of September 2023. Plans like to change - the new date was set till the end of 2023 and again failed 😢 But today is the day - here it comes. While reading the book, you will learn about: ➡ Methods and techniques to approach business analysis of a domain ➡ Project Paradox and how is it related to your knowledge at the beginning of a project ➡ Event Storming and its big-picture and process levels ➡ How do you divide domains into smaller parts called subdomains? ➡ How do you use domain charts to map subdomains? ➡ What are subdomain types, and how do you define them? ➡ How can a subdomain become a separate domain? ➡ How do you approach setting up bounded contexts using Bounded Context Canvas? ➡ How do you use Context Map to define integration and relationships between bounded contexts, third-party systems, and teams? What do you need to do to get it? Now is the best point - it's completely FREE. There are no newsletters, no emails, and no fees. You need to go to the link and click download, and that's it. It is in PDF format👇 https://lnkd.in/dFnbUudV Please share it with others - it will help me to pass this knowledge to as many people as possible. Thanks a lot!🔥 #ddd #domaindrivendesign #softwaredevelopment #softwarearchitecture

A good read. If you are already in DDD, need a refresher, or want to master it, try reading this. The writing is short and direct. #wellDone Maciej Jedrzejewski #DDD

Have you wondered why Claude 3.5 Sonnet is so good? Well, the answer just leaked... The FULL system prompt is now available for all to see. See the first comment for a link to the full prompt. 🔗 Comment "𝗙𝘂𝗹𝗹 𝗕𝗿𝗲𝗮𝗸𝗱𝗼𝘄𝗻" to get my complete analysis and insights. Anthropic's team puts on a masterclass on prompt engineering. The new Artifacts feature of Claude has blown everyone away. It allows you to code and generate content iteratively. Now we can see what's driving its success. 1. 𝗛𝗶𝗱𝗱𝗲𝗻 𝗖𝗵𝗮𝗶𝗻-𝗼𝗳-𝗧𝗵𝗼𝘂𝗴𝗵𝘁 𝗥𝗲𝗮𝘀𝗼𝗻𝗶𝗻𝗴 🔹 Claude includes reasoning steps and hides them on the front end. 2. 𝗙𝘂𝗹𝗹 𝗙𝗲𝘄-𝗦𝗵𝗼𝘁 𝗟𝗲𝗮𝗿𝗻𝗶𝗻𝗴 🔹 Claude provides detailed good and bad examples 3. 𝗨𝘀𝗲𝗿-𝗙𝗼𝗰𝘂𝘀𝗲𝗱 𝗗𝗲𝘀𝗶𝗴𝗻 🔹 Claude details exactly how the user experience should play out 4. 𝗟𝗼𝗴𝗶𝗰 𝗮𝗻𝗱 𝗧𝗮𝘀𝗸 𝗙𝗼𝗰𝘂𝘀 🔹 One of the most impressive capabilities of Artifacts is that it generates unabridged code due to clear instruction 6. 𝗡𝗲𝘄 𝗥𝗼𝗹𝗲 𝗠𝗼𝗱𝗲𝗹𝗶𝗻𝗴 𝗧𝗲𝗰𝗵𝗻𝗶𝗾𝘂𝗲 🔹 Claude never uses "You are" and prefers using "The Assistant" throughout Want my complete analysis and detailed insights on this prompt? Comment "𝗙𝘂𝗹𝗹 𝗕𝗿𝗲𝗮𝗸𝗱𝗼𝘄𝗻" + connect with me, and I'll DM it to you! --- What do you think of this system prompt by Claude? Is it the best prompt you've seen in 2024? Leave a comment below with your thoughts. Repost ♻️ if you found this useful Follow me, hit the 🔔Mark Fulton

Grab your free copy of Mastering Strategic DDD 😉

Does your Design Process have flowdiagraming? I was recently reminded of how awesome this can be for your team. As I was working on enhancing our Design Process at MetLife Legal Plans with Efrain Ferrer, we decided to level up our game. Beyond the usual wires, we introduced flow diagraming at the top of the funnel—a game-changer for sure! Imagine sitting down with stakeholders, building a flow diagram for a potential feature together. The result? -> Group consensus on solutions before diving in! -> identifying knowledge gaps and edge cases upfront. No more surprises down the road. -> Developers loved it! Our flow diagrams became the universal language, reducing friction and earning a big thumbs up. Initially seen as "extra work," it turned out to be our efficiency booster. Less rework, quicker final designs, and a smoother, collaborative process. Flow diagrams not only streamlined our process but brought everyone to the table. If you are not doing this for your team, you need to get on it asap! #FlowDiagrams #DesignProcess #CollaborativeMagic

INVEST from FEEDBACK on story in DEEP, then you'll get PANCAKE Invest: Independent Negotiable Valuable Estimable Small Testible From: Flow Effort Entry Data Operation (Read, Update, Delete) Business Rules Alternative Complexity Knowledge on Story in: Detailed Estimated Eemergent Prioritized then you'll have Puzzles Appreciations News Challenges Aspirations Knowledges Endorsements https://lnkd.in/guAFPf7M #designthinking #productdevelopment.

During my exploration of system design, I often encountered content that directly jumped on the solutions in general without discussing the problems also there was no discussion of why we were adding all this complexity, and what's the requirements behind that. But what I wanted was content that explained why and when these concepts are needed. I wanted a journey that starts with a basic design for a small application and then, based on the requirements, adds complexity to it to fit the needs. So, I put together an article in a storytelling format: 1. The article begins with a simple setup. 2. We talk about the problems with this setup using the 𝐒𝐓𝐀𝐑 method (Situation, Task, Action, Result), which is important in behavioral discussions. 3. Each step includes diagrams that you can 𝐜𝐥𝐢𝐜𝐤 to get more details. Check out the article here: https://lnkd.in/gnUiw8sP And for more, visit the landing page: https://lnkd.in/dSfJGvdQ #systemdesign #softwaredevelopment #fundamentals

🔍Activity Diagrams vs. Sequence Diagrams 🔍 In the world of software development and system analysis, understanding the nuances between various types of diagrams is crucial. Today, let's delve into the distinctions between Activity Diagrams and Sequence Diagrams. 🤔💻 🌀 Activity Diagrams: These diagrams serve as a powerful tool for visualizing workflows, business processes, and the overall flow of activities within a system. Picture it as a roadmap guiding you through various steps and decisions within a process. It's fantastic for capturing the "what" of a system—what actions are performed and in what order. 🛣️✨ 🔄 Sequence Diagrams: On the other hand, Sequence Diagrams zoom in on the interaction between different components or objects within a system. They're like a choreographed dance, showcasing the dynamic exchange of messages between actors over time. It's a fantastic tool for understanding the "how" of a system—how components collaborate and communicate. 💬⏳ While both diagrams are incredibly valuable in their own right, they cater to different aspects of system analysis and design. Activity Diagrams shine when we need to map out complex processes and workflows, providing a bird's-eye view of the entire system. Meanwhile, Sequence Diagrams excel in depicting the precise interactions between components, helping us grasp the finer details of system behavior. Understanding when to use each diagram is key to effective communication and problem-solving in software development projects. By leveraging the strengths of both Activity and Sequence Diagrams, we can gain a comprehensive understanding of our systems and pave the way for smoother development journeys. 💡🚀 What are your experiences with Activity and Sequence Diagrams? Which do you find more helpful in your projects, and why? Let's keep the conversation flowing in the comments below! 🗣️💬 #SoftwareDevelopment #SystemAnalysis #Diagramming #TechTalks #UMLDiagramming #ProcessModeling #WorkflowVisualization #SystemDesign #SoftwareArchitecture #DiagrammingTools #ObjectInteraction #VisualizeComplexity #SystemAnalysisAndDesign #TechnicalDocumentation #CommunicationTools #DeveloperResources #CodeVisualization #SoftwareEngineering #ProgrammingPatterns #SystemBehavior #CollaborativeDevelopment #AgileMethodology #ProblemSolvingTechniques