# Software Design Published articles for Software Design. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Why Tech Companies Hid the "Log Out" Button (And How to Win It Back) DevFeed: [Why Tech Companies Hid the "Log Out" Button (And How to Win It Back)]() Original publisher: [Read original article]() Author: Simon Sterne Published: 2026-09-01T12:33:00Z Content type: opinion Language: en Sources: [Web Designer Depot]() Topics: [User interface design]() Tags: [app-addiction](), [attention-economy](), [behavioral-design](), [dark-patterns](), [digital-minimalism](), [digital-wellbeing](), [internet-culture](), [logout-button](), [online-privacy](), [persuasive-technology](), [product-design](), [social-media](), [software-design](), [tech-industry](), [technology](), [ui](), [ui-design](), [user-autonomy](), [user-experience](), [ux](), [ux-design](), [ux-usability](), [web-design]() ### AI overview An opinion piece arguing that platforms make logging out deliberately difficult to prioritize engagement, tracking, and business metrics over user choice. ### Source excerpt Ever noticed that signing in takes one tap, but logging feels like solving a puzzle?That's not bad design. It's a business strategy. The modern internet has quietly turned "leave" into the hardest button to find--and most people never realized it was happening. ## 15 Common Software Design Patterns Explained with Java Examples DevFeed: [15 Common Software Design Patterns Explained with Java Examples]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-08-25T04:01:49Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Architecture & Design](), [Software Engineering](), [Java](), [Programming]() Tags: [article](), [code](), [design](), [design-patterns](), [java](), [programming](), [software-design]() ### AI overview This tutorial explains 15 commonly used software design patterns, covering their categories and practical use cases. It uses Java code examples and discusses patterns including Singleton, Builder, and Factory Method, along with cautions about global access and hidden dependencies. ### Source excerpt In this article, I'll break down 15 of the most important design patterns I've come across in interviews and throughout my 9+ years as a Software Engineer. ## The Complete Guide to Writing Effective Software Design Documents DevFeed: [The Complete Guide to Writing Effective Software Design Documents]() Original publisher: [Read original article]() Author: ERDINC MUTLU, PRINCIPAL ENGINEER @ TOPTAL Published: 2026-08-25T04:00:00Z Content type: article Language: en Sources: [Toptal Blog]() Topics: [Architecture & Design](), [Software Engineering](), [coding]() Tags: [architecture](), [design](), [documentation](), [guide](), [software-design](), [software-engineering](), [writing]() ### AI overview A practical guide to writing software design documents that translate high-level requirements into technical blueprints before implementation. It covers the purpose, structure, key sections, common pitfalls, and the role of design documents in creating shared understanding among project stakeholders. ### Source excerpt A software design document turns high-level requirements into a technical blueprint before coding starts. This SDD guide offers writing tips, explains key sections, and flags common pitfalls. ## How to Learn Low-Level Design: A Roadmap for Study and Interviews DevFeed: [How to Learn Low-Level Design: A Roadmap for Study and Interviews]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-08-09T10:46:58Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [Architecture & Design](), [Software Engineering](), [Programming](), [interfaces](), [Polymorphism]() Tags: [article](), [code](), [how-to](), [learn](), [programming](), [software-design](), [system-design]() ### AI overview This tutorial presents a step-by-step roadmap for learning low-level design (LLD), including what to study, the order of topics, interview preparation, and linked learning resources. It explains how LLD differs from high-level system design and describes common interview formats such as object-oriented design, machine coding, and concurrency design. ### Source excerpt In this article, I'll give you a complete step-by-step roadmap to learn Low-Level Design or LLD from scratch covering exactly what to learn, the right order to learn it, and how to prepare effectively for low level design interviews. ## Let Koin Shape your Application Architecture DevFeed: [Let Koin Shape your Application Architecture]() Original publisher: [Read original article]() Author: Gabriel Bronzatti Moro Published: 2026-07-06T12:01:01Z Content type: tutorial Language: en Sources: [Koin developers - Medium]() Topics: [Architecture & Design](), [Software Engineering](), [coding](), [Software](), [Ktor]() Tags: [architecture](), [clean-architecture](), [developer](), [koin](), [kotlin](), [ktor](), [software](), [software-architecture](), [software-design]() ### AI overview This tutorial explains how Koin can support application architecture based on Clean Architecture and software design practices. It describes using Koin to create and manage object instances, including singleton and factory definitions, with Ktor's HttpClient as an example. ### Source excerpt Hey, friends! 👋 Today we're going to explore application architecture and how Koin can help us build scalable, maintainable applications by applying the principles of Clean Architecture and other software design best practices. Application architecture is a fundamental skill for every software engineer. A well-designed architecture makes applications easier to understand, test, extend, and maintain as they grow over time. A collection of LEGO towers in various stages of construction -- Unsplash by richard_heFoundation When we think about software architecture, we often picture layered diagrams -- data, domain, and presentation -- along with classes such as use cases, handlers, repositories, and helpers. But how do all these components work together? How do we establish a reliable communication protocol between them? Architecture is more than just organizing classes into packages. It's about defining how objects communicate and collaborate working toward a common goal. With that in mind, let's begin our journey with a simple principle: Every object instance should be created by Koin. My only responsibility as a developer is to describe how each object should be instantiated, while Koin takes care of the creation process.SingletonSingleton Café generated by ChatGPT Koin makes it easy to define singletons, whether you're using the @Single annotation or the single { ... } DSL. By declaring a singleton, you're telling Koin to create and manage a single instance of that object for the lifetime of the application. In the example below, we define an HttpClient as a singleton: @Module class NetworkModule { @Single fun provideHttpClient(): HttpClient { return HttpClientBuilder.build( baseUrl = BuildKonfig.HOST, ) } ... } HttpClient is a class provided by Ktor, and it should typically be instantiated only once. By declaring it as a singleton, Koin ensures that the same HttpClient instance is shared throughout the application. The Singleton pattern is commonly used for objects tha ## Rethinking The Experience Of System Tools DevFeed: [Rethinking The Experience Of System Tools]() Original publisher: [Read original article]() Author: hello@smashingmagazine.com (Kyrylo Levashov) Published: 2026-05-05T08:00:00Z Content type: article Language: en Sources: [Articles on Smashing Magazine -- For Web Designers And Developers]() Topics: [Utility Software](), [User experience (UX)](), [Software Engineering](), [Software]() Tags: [article](), [design](), [software](), [software-design](), [tools](), [user-experience](), [ux]() ### AI overview The article argues that utility and maintenance software should evolve beyond purely functional, chore-like experiences. Drawing comparisons to redesigned physical products, it advocates more intelligent, human, and emotionally engaging UX for system tools. ### Source excerpt Design always starts with function -- function shapes form. But if that function can't be made completely invisible and people still have to interact with it, it inevitably becomes part of their experience. In this article, Kyrylo Levashov shares four common software design assumptions. ## Ultimate Go Software Design LIVE: Ep.63 DevFeed: [Ultimate Go Software Design LIVE: Ep.63]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2026-01-06T00:00:00Z Content type: article Language: en Sources: [Carlos Becker]() Topics: [Go Language](), [Architecture & Design](), [Ardan Labs]() Tags: [ardan-labs](), [coding](), [design](), [go](), [live](), [software-design]() ### AI overview A live coding stream featuring Bill Kennedy, Kevin Enriquez, Andrey Nering, and the author, focused on adding support for Ardan Labs' Kronk to Charm's fantasy. ### Source excerpt A live coding stream with Bill Kennedy, Kevin Enriquez, Andrey Nering, and me. ## IDC study says the global workforce engaged in software design is expanding DevFeed: [IDC study says the global workforce engaged in software design is expanding]() Original publisher: [Read original article]() Author: Figma Published: 2025-09-03T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [idc](), [User experience (UX)](), [Figma](), [Generative AI](), [software-development]() Tags: [2025](), [design](), [figma](), [genai](), [idc](), [product-development](), [software-design](), [ux](), [ux-design]() ### AI overview An IDC study forecasts that the global workforce involved in software design and development will grow by more than 30%, from 107 million workers in 2025 to 144 million in 2029. UX design is expected to grow faster than other knowledge-worker categories, while generative AI accelerates product development and raises expectations for usable, visually appealing AI features. ### Source excerpt IDC forecasts that the number of people involved in software design will increase by more than 30% from 2025 to 2029--signaling the rising importance of design as a competitive differentiator. ## Tactical Coding Assistants DevFeed: [Tactical Coding Assistants]() Original publisher: [Read original article]() Author: Pieter Tolsma Published: 2025-07-03T08:53:09Z Content type: opinion Language: en Sources: [Booking.com Development - Medium]() Topics: [Large Language Model](), [Development](), [Software Engineering](), [Architecture & Design](), [Refactoring](), [Claude](), [Artificial Intelligence]() Tags: [ai](), [claude](), [coding](), [coding-assistant](), [complexity](), [design](), [development](), [genai](), [llm](), [refactor](), [review](), [software-design]() ### AI overview The article compares tactical and strategic programming and applies that distinction to coding assistants. Drawing on the author's experience, it argues that assistants such as Gemini 2.5 Pro and Claude 3.7 can implement clearly specified tasks effectively, but may produce excessive complexity, duplicated behavior, and difficult-to-maintain code when used without architectural review. ### Source excerpt Over the past 15 months I have been actively working with LLM's in my job as a software engineer. I have had many moments where I thought singularity was here, but then almost immediately after I would see the agent fall flat on its face. I have become interested in figuring out when and why these new tools fail, in the hope that it can help me use these tools to their maximum potential while still keeping control over the quality of what I commit. In this short article, I want to expand on a recent observation. Generated using Gemini Imagen 4 In the book 'A Philosophy of Software Design' by John K. Ousterhout, a great analogy is made between two different modes of development: tactical and strategic programming. Tactical programming: this is a shortsighted approach focused on completing the immediate task as quickly as possible. Here, the primary goal is to make a feature or bug fix work in the most direct way. You can imagine what will happen if you have a team of engineers that only works like this: technical debt will pile up fast. Generated using Gemini Imagen 4 On the other side there is strategic programming: this involves a higher level of thinking. A strategic programmer is not finished when the feature is implemented. They take a step back and review the architecture, to see if any abstractions can be made. Does the current approach overcomplicate things? Can we refactor things? The focus here is on design, where the engineers main goal is to keep complexity at bay. These two analogies hooked onto what I thought about the current state of coding assistants. In my experience, some of the current (mid-2025) state of the art coding assistants (Gemini 2.5 pro, Claude 3.7) are extremely adept tactical programmers. Assuming you give them a clear description of what you need implemented, they will go ahead and do it for you (with quite a high success rate in my experience). We humans are limited by many things, such as the speed at which we can physically press k ## Config 2025: Pushing design further DevFeed: [Config 2025: Pushing design further]() Original publisher: [Read original article]() Author: Dylan Field Published: 2025-05-07T00:00:00Z Content type: article Language: en Sources: [Figma Blog]() Topics: [Figma](), [Artificial Intelligence](), [Code]() Tags: [2025](), [ai](), [design](), [figma](), [generation](), [prototypes](), [software-design](), [workflows]() ### AI overview Figma's Config 2025 recap introduces Figma Make, a prompt-to-app capability for exploring, iterating on, and refining designs. It supports prompts from phrases or Figma files, targeted prototype edits using natural language, high-fidelity prototypes, and work spanning design and code. ### Source excerpt Dylan Field runs down everything we launched at Config 2025 and explains why pushing design further matters more now than ever. ## 2025 Technical Steering Committee DevFeed: [2025 Technical Steering Committee]() Original publisher: [Read original article]() Author: Fred Schott Published: 2025-04-18T00:00:00Z Content type: news Language: en Sources: [The Astro Blog]() Topics: [Astro](), [Maintainers](), [Architecture & Design](), [GitHub]() Tags: [2025](), [astro](), [community](), [contributors](), [core](), [development](), [github](), [governance](), [maintainers](), [open](), [software-design]() ### AI overview The Astro project announces its 2025 Technical Steering Committee, adding Emanuele Stoppa, Florian Lefebvre, and Matt Kane alongside continuing member Matthew Phillips. Matt Kane will also lead the Astro framework team. The article explains how the committee supports technical decision-making, governance, and the long-term health of the Astro codebase. ### Source excerpt Meet Astro's 2025 Technical Steering Committee and learn how our open governance model supports the framework's growth, performance, and community-led development. ## Seven Software Architectural Patterns: A Plain-English Guide DevFeed: [Seven Software Architectural Patterns: A Plain-English Guide]() Original publisher: [Read original article]() Author: Nelson Djalo Published: 2025-04-16T16:00:23Z Content type: tutorial Language: en Sources: [Amigoscode Newsletter]() Topics: [Architecture & Design](), [Software Engineering](), [Microservice]() Tags: [architecture](), [guide](), [microservices-architecture](), [monolithic-architecture](), [patterns](), [software-design]() ### AI overview A plain-English guide to seven software architectural patterns: monolithic, layered, microservices, SOA, MVC, event-driven, and master-slave. It explains how these patterns organize software and discusses tradeoffs such as simplicity, scalability, complexity, and collaboration. ### Source excerpt A simple guide to 7 software architectural patterns -- monolithic, layered, microservices, SOA, MVC, event-driven, and master-slave -- explained in plain English. ## Design is about the abstractions DevFeed: [Design is about the abstractions]() Original publisher: [Read original article]() Author: Mike Published: 2024-08-05T15:55:48Z Content type: article Language: en Sources: [Dev Details]() Topics: [abstraction](), [Architecture & Design](), [software-architecture](), [API](), [interfaces]() Tags: [abstraction](), [api](), [architecture](), [interface](), [software-architecture](), [software-design](), [software-engineering]() ### AI overview The article explains how abstraction helps software and house design by hiding implementation details, defining interfaces and APIs, and indicating when a design contains enough detail to stop. ### Source excerpt Abstractions simplify designs and tell us when to stop designing. ## Ep. 9: Go Package Design: Authorization and API Structures DevFeed: [Ep. 9: Go Package Design: Authorization and API Structures]() Original publisher: [Read original article]() Published: 2024-07-17T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Authorization](), [rego](), [Software Engineering]() Tags: [access-control](), [api-structures-in-go](), [authentication](), [authorization](), [clean-code-go](), [context-in-go-middleware](), [efficient-go-code](), [error-handling-patterns-go](), [exported-and-unexported-apis-go](), [go](), [go-api-best-practices](), [go-api-readability](), [go-authorization](), [go-authorization-logic](), [go-development-practices](), [go-error-management](), [go-middleware-handlers](), [go-package-design](), [go-package-organization](), [go-package-tutorials](), [go-software-architecture](), [go-software-tips](), [intuitive-go-codebase](), [maintainable-go-code](), [rego](), [rego-scripts-for-go](), [role-based-authorization-in-go](), [scalable-go-software-design](), [secure-access-control-go](), [software-design](), [user-claims-context-go]() ### AI overview This episode explains how to design Go packages that support role-based authorization with Rego, clearly separate exported and unexported APIs, manage errors consistently, and pass information through context between middleware and handlers. ### Source excerpt Introduction: Welcome to Episode 9 of our Ultimate Software Design series! In this episode, Bill delves into the intricacies of implementing robust authorization and API structure within Go packages, offering invaluable insights for developers aiming to build scalable and maintainable software systems. Implement role-based authorization logic for secure and precise access control using Rego scripts. Learn best practices for structuring exported and unexported APIs to maintain a clean, intuitive, and maintainable codebase. ## RAG Trick: Embeddings are Spheres DevFeed: [RAG Trick: Embeddings are Spheres]() Original publisher: [Read original article]() Published: 2024-07-10T00:00:00Z Content type: tutorial Language: en Sources: [Tim Kellogg]() Topics: [Embeddings](), [Retrieval Augmented Generation (RAG)](), [Software Engineering]() Tags: [embeddings](), [make](), [model](), [rag](), [software-design]() ### AI overview This tutorial explains that normalized embeddings lie on a hypersphere and shows how that simplifies similarity calculations. It recommends dot product over other distance measures, notes that cosine similarity is equivalent for normalized vectors, and relates average embeddings to logistic regression. ### Source excerpt This post offers some helpful simplifications you can make when working with RAG or embeddings that help build a working mental model around them. Embeddings typically form a (hyper)sphere, because they're normalized. ## Craft in design: What it is & why it matters DevFeed: [Craft in design: What it is & why it matters]() Original publisher: [Read original article]() Author: andyacevedo Published: 2024-06-26T17:25:44Z Content type: article Language: en Sources: [Slack Design]() Topics: [User Experience](), [Usability](), [User interface design](), [Software Engineering](), [Slack]() Tags: [article](), [design](), [experience](), [slack](), [software](), [software-design](), [uncategorized](), [usability](), [user-experience]() ### AI overview The article defines craft in software design and explains how it complements utility and usability. Using Slack's product principles, it argues that craft shapes how a product feels, supports intuitive and dependable experiences, and can contribute to positive emotional responses and customer loyalty. ### Source excerpt In software design we have all heard the phrase "well-crafted user experience." It may have come up in conversation, in an article or in a job interview. Indeed, conversation and debate about craft, what it is and why it matters, has been a through-line during my 20+ years in tech. I've worked at companies that [...] The post Craft in design: What it is & why it matters appeared first on Slack Design. ## The Soft Side of Software Design DevFeed: [The Soft Side of Software Design]() Original publisher: [Read original article]() Author: Dariusz Sadowski Published: 2024-06-01T11:11:37Z Content type: article Language: en Sources: [Thinking in Tech]() Topics: [Architecture & Design](), [Software Engineering](), [Software]() Tags: [design](), [good-practices](), [soft-skills](), [software](), [software-design](), [systems]() ### AI overview The article argues that software design, like soft skills, is difficult to evaluate objectively because its quality depends on context, communication, personal judgment, and real-world outcomes. It questions whether conventions such as readable code, established practices, or TDD reliably define good design. ### Source excerpt How to build systems in the real world ## Ep. 3: Mastering Kubernetes: Setting Up Environments with Kind DevFeed: [Ep. 3: Mastering Kubernetes: Setting Up Environments with Kind]() Original publisher: [Read original article]() Published: 2024-05-28T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Kubernetes](), [Docker](), [configuration](), [Deployment](), [networking](), [Command-line interface](), [Development]() Tags: [cli](), [clusters](), [code-modularity](), [configuration](), [cpu](), [deployment](), [docker](), [go](), [go-development](), [go-projects](), [guides](), [how-to](), [kubernetes](), [memory](), [networking](), [package-architecture](), [software-design](), [troubleshooting](), [video]() ### AI overview This video tutorial explains how to set up and manage a Kubernetes development environment using kind, Kubernetes inside Docker. It covers clusters, nodes, pods, resource allocation, networking, asynchronous operations, deployment monitoring, and troubleshooting for Go applications. ### Source excerpt Introduction: In this installment of the Ultimate Software Design series, Bill guides us through setting up a Kubernetes environment using Kubernetes inside Docker (kind). He breaks down the structure of Kubernetes and offers insights into effective cluster management, ensuring a robust and efficient development environment. Effective Cluster Management: Learn the basics of setting up and managing a Kubernetes cluster, essential for maintaining scalable and resilient Go applications. Pod and Node Configuration: Understand how to configure pods and nodes to optimize compute resources and ensure seamless application deployment. ## Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development DevFeed: [Ep. 2: Elevating Software Design in Go: Package Architecture in Modern Development]() Original publisher: [Read original article]() Published: 2024-05-21T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Software Engineering](), [Architecture & Design](), [Code]() Tags: [api-design](), [code-modularity](), [dependencies](), [go](), [go-development](), [go-projects](), [integrity](), [modularity](), [package-architecture](), [scalability](), [software-design]() ### AI overview This video episode explains package architecture in Go. It emphasizes clear boundaries between components, focused package functionality, avoiding generic packages such as "Utils" or "Common," and the role of robust type systems in maintainable software. ### Source excerpt Introduction: In this insightful episode, Bill dives deep into the realm of package design, shedding light on its crucial role in software development. Here are three key takeaways for Go developers: Code Modularity: Learn how Go's packaging system creates essential firewalls between program components, enhancing maintainability. Focused Functionality: Discover the importance of designing packages that provide specific functionality, fostering code clarity. Avoiding Pitfalls: Bill warns against common package design mistakes like centralized "common" packages, promoting a layered approach to maintainable code. ## Ep. 1: Mastering Software Design: Architectural Layers and Coding Modes DevFeed: [Ep. 1: Mastering Software Design: Architectural Layers and Coding Modes]() Original publisher: [Read original article]() Published: 2024-05-14T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Software Engineering](), [Go Language](), [Architecture & Design](), [Refactoring](), [Software]() Tags: [coding-modes](), [go](), [go-development](), [go-projects](), [maintainability](), [readability](), [refactoring](), [software-design](), [software-development](), [ultimate-software-design-series](), [writing-code]() ### AI overview This episode of the Ultimate Software Design series explains how to create clear, precise, robust, and maintainable code in Go. It covers readability, semantic precision in components, functions, and variables, the distinction between programming and engineering modes, and systematic refactoring focused on precision, testability, and readability. ### Source excerpt Introduction: Embark on a journey into the heart of software design with the Ultimate Software Design series, where Bill navigates through the intricacies of crafting robust and maintainable code in Go. Understand the importance of prioritizing clarity over brevity in code, fostering better understanding and collaboration among Go developers. Learn how to ensure precision in every aspect of Go development, emphasizing the necessity for precise semantic meanings in components, functions, and variables. ## 4 Software Design Principles I Learned the Hard Way DevFeed: [4 Software Design Principles I Learned the Hard Way]() Original publisher: [Read original article]() Author: Engineer's Codex Published: 2024-04-22T19:03:53Z Content type: article Language: en Sources: [Engineer's Codex]() Topics: [Software Engineering](), [Architecture & Design](), [Software](), [Code]() Tags: [code](), [design](), [software-design](), [software-engineering](), [source-of-truth](), [synchronization]() ### AI overview An experienced software engineer shares design principles drawn from building and launching a large service. The article argues for maintaining one source of truth, deriving values instead of storing duplicate state when practical, and selectively repeating code rather than forcing unsuitable abstractions. It emphasizes that these principles require context and tradeoffs. ### Source excerpt If there's two sources of truth, one is probably wrong. And yes, please repeat yourself. ## Design context is more important than a detailed solution DevFeed: [Design context is more important than a detailed solution]() Original publisher: [Read original article]() Author: Mike Published: 2023-12-10T06:29:25Z Content type: opinion Language: en Sources: [Dev Details]() Topics: [context](), [implementation](), [Software Engineering](), [Requirements]() Tags: [autonomy](), [context](), [decision-making](), [flexibility](), [implementation](), [software-design]() ### AI overview The article argues that software design should prioritize sufficient context over detailed, rigid solutions. Because requirements and knowledge change during implementation, lightweight design documents should align stakeholders, explain the problem and expected outcomes, and give teams enough direction to adapt autonomously. ### Source excerpt We will never have enough information before implementation to be able to design a perfect solution. Inevitably, what we know will change as we implement. ## Benefits of Collaboration DevFeed: [Benefits of Collaboration]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-11-04T04:00:00Z Content type: opinion Language: en Sources: [Tobias Mende]() Topics: [Software Engineering](), [meetings]() Tags: [asynchronous](), [code-reviews](), [collaboration](), [collaboration-developer-experience-developer-productivity-team-programming-engineering-excellenc](), [communication](), [meetings](), [software-design](), [teamwork]() ### AI overview The article argues that collaboration should be the standard way of working for software teams. It describes benefits including on-the-job team building, better decisions, knowledge sharing, improved communication, and more effective problem-solving. It also argues that synchronous collaboration can improve later asynchronous communication. ### Source excerpt Benefits of Collaboration In my career, I've seen many "teams" that mainly collaborate only when the work gets tough or if someone has been stuck for days. In these cases, teamwork is more of an exception than a regular practice. This approach is backward. Collaboration should be the standard way of working, and we should only choose to work independently for good reasons. ## Driving software design forward DevFeed: [Driving software design forward]() Original publisher: [Read original article]() Author: Mike Published: 2023-07-20T05:10:27Z Content type: opinion Language: en Sources: [Dev Details]() Topics: [Architecture & Design](), [software-architecture](), [Software Engineering](), [decision-making]() Tags: [architect](), [architecture](), [decision-making](), [engineering](), [software-architecture](), [software-design]() ### AI overview The article argues that architects should facilitate the software architecture process rather than own most design work. Engineers should drive designs according to their scope, with one Driver responsible for moving the project forward, coordinating decision-making, and aligning participants on problems, needs, constraints, risks, solutions, and impacts. ### Source excerpt The last person I'd let design is me, the Architect [Next page]()