Anibal Scott’s Post

Got my attention: What we talk about when we talk about System Design (https://lnkd.in/gvqzUdDZ)

Really great talk about software design: Some of my Key takeaways: - Design should be done in tandem with the development and not thought of right at the start hoping it will be enough for all possible future constrains - Having an effective glosaary of words and enforcing that they mean what they mean, which means if words are started to be used differently than what it says in the glossary either glossary or their use needs to be updated - Avoid heronaming, as it tells us nothing about the context, i.e naming a service “flash” has no bearing if the role/signature/design of the services changes tomorrow, it could still be named “flash” without giving an indication of something changing. - Asking questions frequently, tells about the socratic method but I feel this is a general good idea, but what the socratic method does its that the questions also asks reflectively about what and how we are thinking in the first place - The key outcome and goal of design is advancing our understanding and knowledge which can be quantified asking questions as in the last point - Design is not monotonic and there will be times when it will make us take a step back and backtrack, however at this point we will have gained something insightful - X/Y problem A big section also talks about how to make design more actionable/agendaizable and touches on a lot wrt dev stories and how to remain flexible in that. There are many more things it touches on, this is not really a strict algorithm on how to do design, but its a good collection of a few patterns. Definitely worth watching https://lnkd.in/gRDR9pAC

Delivering design solutions to production is one of the key challenges for designers. Successful interface solutions necessitate reusability from both design and development angles. They should be based on common patterns.

A thorough list of resources for your Design System journey! Thanks to Justine Montgomery for putting this together.

Good Morning Designers, Making my way through 2024 reading list, this time with "How to Make Sense of Any Mess". I found the book thoughtful, well-organized, and a good reference for different stages of sense-making. Key takeaways and favorite quotes are below: ⚡ Nothing is set in stone. If there's a better way to organize it, that's where our power lies. 🗺 Before making diagrams, consider the scope (clearly stated purpose), and scale (relative size of the diagram, what it captures). This can help define what your diagram seeks to help people understand, what it encompasses and what it does not (and why). 🤓 Make sure the language is clear. If there is a shared language between stakeholders and users, exploring solutions is much easier. 👥 Design with, not for. This means looping in stakeholders and users early and often during the design process, setting the stage for better buy-in later on. 📈 Indicators can help a lot, even if we don't have them yet. Ask yourself: "What can you measure?" "What could you measure if things changed?" "What signs would tell you if you're moving in the right direction?" 💭 Fuzzy is normal: "Fuzzy as your lens can seem, setting goals with incomplete data is still a good way to determine if you're moving in the right direction." 🤓 "Ambiguity costs clarity; exactitude costs flexibility." 💤 "Don't procrastinate. Messes only grow with time." ✅ "Perfection isn't possible, but progress is." 🔦 "Shed light on the messes that people see but don't talk about." 👍 "Make sure everyone agrees on the intent behind the work you're doing together." 💪 "Help people choose a direction and define goals to track your progress." Like many topics in design, it all comes down to people. None of us can untangle a mess by ourselves, we need to loop our team in on how things got to be what they are, what the vision is, and how to measure success when we get there. See link below to the website where the book is, each title is clickable! https://lnkd.in/ewi5fGtH

Blueprints aren't just for buildings. They're crucial in software, too: In the realm of Domain-Driven Design, Tactical Design and Tactical Patterns are cornerstone concepts. While Tactical Design is akin to creating a detailed blueprint for a building, outlining the architecture and vision, Tactical Patterns are the specific tools and components that bring this vision to life. Think of it as the difference between planning the layout of a house and selecting the bricks, mortar, and tools to construct it. Tactical Patterns include: - Entities - Value Objects - Aggregates - Domain Services - Factories - Repositories - Domain Events These are the building blocks to tackle complex problems, modeling them in an efficient and scalable way. ✍️ I'm curious to learn from the community: how have you implemented Tactical Patterns in your projects? #softwareengineering #softwaredevelopment #softwaredesign

Designing a well-defined system is like solving a jigsaw puzzle. When all the right pieces come together, the design in front of your eyes will fulfil all the business requirements and possibly be also extensible. A well-designed system is definitely an end goal, and the starting point is to understand fundamentals of system design. Here is a blog I wrote about the same which should provide you some pointers to get started! #systemdesign #design #fundamentals #softwarearchitecture

"Design systems are the backbone of scalable designs. 📈 - Do you have a design system in place? - How has it helped your workflow? - What advice would you give to someone building a design system from scratch? Join the conversation and let's learn from each other's experiences!

System Design is a complex area and not usually straightforward to define or create. That’s why we need templates and frameworks to guide us through this practice. #systemintegrators #systemanalyst #systemsengineering #design