diff --git a/roadmaps/software-architect/content/acid-cap-theorem@bbKEEk7dvfFZBBJaIjm0j.md b/roadmaps/software-architect/content/acid-cap-theorem@bbKEEk7dvfFZBBJaIjm0j.md index bbf7dc146..7fa0fcf0d 100644 --- a/roadmaps/software-architect/content/acid-cap-theorem@bbKEEk7dvfFZBBJaIjm0j.md +++ b/roadmaps/software-architect/content/acid-cap-theorem@bbKEEk7dvfFZBBJaIjm0j.md @@ -1,5 +1,5 @@ # ACID, CAP Theorem - + ACID describes the guarantees a database transaction provides: atomicity, consistency, isolation, and durability, ensuring reliable operations even under failure. The CAP theorem states that a distributed system can only guarantee two of three properties at once: consistency, availability, and partition tolerance. Architects use both concepts to reason about the trade offs involved in choosing databases and designing distributed systems. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/application-architecture@Lqe47l4j-C4OwkbkwPYry.md b/roadmaps/software-architect/content/application-architecture@Lqe47l4j-C4OwkbkwPYry.md index 8b90711a9..924dbe625 100644 --- a/roadmaps/software-architect/content/application-architecture@Lqe47l4j-C4OwkbkwPYry.md +++ b/roadmaps/software-architect/content/application-architecture@Lqe47l4j-C4OwkbkwPYry.md @@ -1,5 +1,5 @@ # Application Architecture - + Application architecture focuses on the internal structure of a single software application: its modules, layers, and the patterns used to organize code. It determines how the application handles concerns like data access, business logic, and user interface separation. Decisions made here affect how easy the application is to test, extend, and maintain over time. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/atlassian-tools@3bpd0iZTd3G-H8A7yrExY.md b/roadmaps/software-architect/content/atlassian-tools@3bpd0iZTd3G-H8A7yrExY.md index 1caa389ac..84ad41d7e 100644 --- a/roadmaps/software-architect/content/atlassian-tools@3bpd0iZTd3G-H8A7yrExY.md +++ b/roadmaps/software-architect/content/atlassian-tools@3bpd0iZTd3G-H8A7yrExY.md @@ -1,5 +1,5 @@ # Atlassian Tools - + Atlassian tools, including Jira and Confluence, support project tracking and documentation for software teams at scale. Jira manages tasks, sprints, and issues in agile workflows, while Confluence stores documentation and design discussions. Many enterprise teams standardize on these tools for both day to day work tracking and long term knowledge management. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/auth-strategies@KiwFXB6yd0go30zAFMTJt.md b/roadmaps/software-architect/content/auth-strategies@KiwFXB6yd0go30zAFMTJt.md index 23cfa0886..aa50e5c0e 100644 --- a/roadmaps/software-architect/content/auth-strategies@KiwFXB6yd0go30zAFMTJt.md +++ b/roadmaps/software-architect/content/auth-strategies@KiwFXB6yd0go30zAFMTJt.md @@ -1,5 +1,5 @@ # Auth Strategies - + Authentication and authorization strategies determine how a system verifies who a user is and what they are allowed to do. Common approaches include session based authentication, token based methods like JWT, and protocols like OAuth for delegated access. Choosing the right strategy affects both security and how easily a system integrates with other services. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/balance@otHQ6ye1xgkI1qb4tEHVF.md b/roadmaps/software-architect/content/balance@otHQ6ye1xgkI1qb4tEHVF.md index 60f092c6e..9ee419962 100644 --- a/roadmaps/software-architect/content/balance@otHQ6ye1xgkI1qb4tEHVF.md +++ b/roadmaps/software-architect/content/balance@otHQ6ye1xgkI1qb4tEHVF.md @@ -1,5 +1,5 @@ # Balance - + Balance refers to weighing competing priorities such as speed versus quality, or innovation versus stability. An architect regularly makes trade offs between what is technically ideal and what is practical given time and budget constraints. Finding the right balance keeps a project moving without accumulating excessive technical debt. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/communication@Ac49sOlQKblYK4FZuFHDR.md b/roadmaps/software-architect/content/communication@Ac49sOlQKblYK4FZuFHDR.md index e9a2b75c7..b0265ab59 100644 --- a/roadmaps/software-architect/content/communication@Ac49sOlQKblYK4FZuFHDR.md +++ b/roadmaps/software-architect/content/communication@Ac49sOlQKblYK4FZuFHDR.md @@ -1,5 +1,5 @@ # Communication - + Communication is central to the architect role, since decisions need to be explained to developers, managers, and other stakeholders with different levels of technical understanding. An architect translates business goals into technical direction and also feeds technical constraints back into business conversations. Without strong communication, even a well designed architecture can fail to be adopted correctly by the team. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/consult--coach@LSWlk9A3b6hco9Il_elao.md b/roadmaps/software-architect/content/consult--coach@LSWlk9A3b6hco9Il_elao.md index af3706041..09a146888 100644 --- a/roadmaps/software-architect/content/consult--coach@LSWlk9A3b6hco9Il_elao.md +++ b/roadmaps/software-architect/content/consult--coach@LSWlk9A3b6hco9Il_elao.md @@ -1,5 +1,5 @@ # Consult & Coach - + Consulting and coaching means guiding developers and teams toward better technical practices without necessarily writing the code themselves. Architects often review designs, answer technical questions, and mentor less experienced engineers on patterns and standards. This skill turns an architect's individual knowledge into improvements across the whole team. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/cqrs-eventual-consistency@RsnN5bt8OhSMjSFmVgw-X.md b/roadmaps/software-architect/content/cqrs-eventual-consistency@RsnN5bt8OhSMjSFmVgw-X.md index f65a37c59..67d1b7938 100644 --- a/roadmaps/software-architect/content/cqrs-eventual-consistency@RsnN5bt8OhSMjSFmVgw-X.md +++ b/roadmaps/software-architect/content/cqrs-eventual-consistency@RsnN5bt8OhSMjSFmVgw-X.md @@ -1,5 +1,5 @@ # CQRS, Eventual Consistency - + CQRS, or Command Query Responsibility Segregation, separates the operations that change data from the operations that read data, often using different models for each. This separation pairs naturally with eventual consistency, where updates propagate across a system over time instead of instantly. These patterns are common in distributed systems where strict, immediate consistency would hurt performance or scalability. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/ddd@IIelzs8XYMPnXabFKRI51.md b/roadmaps/software-architect/content/ddd@IIelzs8XYMPnXabFKRI51.md index 07d773b94..d4e954224 100644 --- a/roadmaps/software-architect/content/ddd@IIelzs8XYMPnXabFKRI51.md +++ b/roadmaps/software-architect/content/ddd@IIelzs8XYMPnXabFKRI51.md @@ -1,5 +1,5 @@ # DDD - + Domain driven design structures software around the business domain it serves, using a shared language between developers and domain experts called the ubiquitous language. It introduces concepts like bounded contexts and aggregates to manage complexity in large systems. DDD is especially useful when building software for complex business domains where getting the model right matters more than technical novelty. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/decision-making@MSDo0nPk_ghRYkZS4MAQ_.md b/roadmaps/software-architect/content/decision-making@MSDo0nPk_ghRYkZS4MAQ_.md index b889774e4..2518a9ec3 100644 --- a/roadmaps/software-architect/content/decision-making@MSDo0nPk_ghRYkZS4MAQ_.md +++ b/roadmaps/software-architect/content/decision-making@MSDo0nPk_ghRYkZS4MAQ_.md @@ -1,5 +1,5 @@ # Decision Making - + Decision making covers evaluating trade offs and choosing a direction when there is no single obviously correct answer. Architects constantly weigh factors like cost, performance, team skill, and time to market when picking a technology or pattern. Good decision making relies on gathering enough information without getting stuck waiting for a perfect answer that may never come. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/design--architecture@fBd2m8tMJmhuNSaakrpg4.md b/roadmaps/software-architect/content/design--architecture@fBd2m8tMJmhuNSaakrpg4.md index 13e82342b..ec9a171b5 100644 --- a/roadmaps/software-architect/content/design--architecture@fBd2m8tMJmhuNSaakrpg4.md +++ b/roadmaps/software-architect/content/design--architecture@fBd2m8tMJmhuNSaakrpg4.md @@ -1,5 +1,5 @@ # Design & Architecture - + This skill covers applying design principles and architectural patterns to real systems, not just knowing them in theory. It means knowing when to use a microservices approach versus a monolith, or when a simple layered design is enough. Strong design and architecture skills come from experience applying patterns across different kinds of projects and learning from what worked and what did not. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/estimate-and-evaluate@m0ZYdqPFDoHOPo18wKyvV.md b/roadmaps/software-architect/content/estimate-and-evaluate@m0ZYdqPFDoHOPo18wKyvV.md index dd48a4e25..480ce2109 100644 --- a/roadmaps/software-architect/content/estimate-and-evaluate@m0ZYdqPFDoHOPo18wKyvV.md +++ b/roadmaps/software-architect/content/estimate-and-evaluate@m0ZYdqPFDoHOPo18wKyvV.md @@ -1,5 +1,5 @@ # Estimate and Evaluate - + Estimating and evaluating involves judging the time, cost, and effort a technical solution will require, as well as assessing whether an existing system meets its goals. Architects use this skill when planning new projects and when reviewing whether current systems are still fit for purpose. Accurate estimates depend on experience and an honest understanding of a team's capabilities. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/git@ZEzYb-i55hBe9kK3bla94.md b/roadmaps/software-architect/content/git@ZEzYb-i55hBe9kK3bla94.md index a3db97c05..a0140914c 100644 --- a/roadmaps/software-architect/content/git@ZEzYb-i55hBe9kK3bla94.md +++ b/roadmaps/software-architect/content/git@ZEzYb-i55hBe9kK3bla94.md @@ -1,5 +1,5 @@ # Git - + Git is a distributed version control system that tracks changes to code over time and allows multiple developers to work on the same project without overwriting each other's work. It supports branching and merging workflows that let teams develop features in isolation before combining them. Almost every modern software project relies on Git as its foundation for source control. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/how-to-code@77KvWCA1oHSGgDKBTwjv7.md b/roadmaps/software-architect/content/how-to-code@77KvWCA1oHSGgDKBTwjv7.md index 4adab4c54..6342f78cb 100644 --- a/roadmaps/software-architect/content/how-to-code@77KvWCA1oHSGgDKBTwjv7.md +++ b/roadmaps/software-architect/content/how-to-code@77KvWCA1oHSGgDKBTwjv7.md @@ -1,5 +1,5 @@ # How to Code - + An architect needs strong coding skills to design realistic solutions and earn credibility with the development team. Writing code themselves helps them understand the practical constraints of the technologies they choose and spot problems before they become costly. Staying hands on also keeps their architectural decisions grounded in real implementation experience rather than theory alone. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/http-https@Nq6o6Ty8VyNRsvg-UWp7D.md b/roadmaps/software-architect/content/http-https@Nq6o6Ty8VyNRsvg-UWp7D.md index 2042f0f0a..68e9dddb5 100644 --- a/roadmaps/software-architect/content/http-https@Nq6o6Ty8VyNRsvg-UWp7D.md +++ b/roadmaps/software-architect/content/http-https@Nq6o6Ty8VyNRsvg-UWp7D.md @@ -1,5 +1,5 @@ # HTTP, HTTPS - + HTTP is the protocol that underlies most communication on the web, defining how clients and servers exchange requests and responses. HTTPS adds encryption on top of HTTP using TLS, protecting data in transit from being read or altered by third parties. Nearly every modern web architecture relies on a solid understanding of how these protocols handle requests, headers, and status codes. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/important-skills-to-learn@lBtlDFPEQvQ_xtLtehU0S.md b/roadmaps/software-architect/content/important-skills-to-learn@lBtlDFPEQvQ_xtLtehU0S.md index b8ea4464a..64779ae79 100644 --- a/roadmaps/software-architect/content/important-skills-to-learn@lBtlDFPEQvQ_xtLtehU0S.md +++ b/roadmaps/software-architect/content/important-skills-to-learn@lBtlDFPEQvQ_xtLtehU0S.md @@ -1,3 +1,3 @@ # Important Skills to Learn - + Beyond technical knowledge, a software architect needs skills like clear communication, sound decision making, and the ability to simplify complex problems. These skills help them lead teams, justify technical choices to non technical stakeholders, and keep projects moving forward. Building these skills alongside technical expertise is what separates a senior developer from an effective architect. \ No newline at end of file diff --git a/roadmaps/software-architect/content/javascript--typescript@bhP5gMpRVebSFpCeHVXBj.md b/roadmaps/software-architect/content/javascript--typescript@bhP5gMpRVebSFpCeHVXBj.md index d449f2182..039ee7c5a 100644 --- a/roadmaps/software-architect/content/javascript--typescript@bhP5gMpRVebSFpCeHVXBj.md +++ b/roadmaps/software-architect/content/javascript--typescript@bhP5gMpRVebSFpCeHVXBj.md @@ -1,5 +1,5 @@ # JavaScript / TypeScript - + JavaScript is the primary language of the web, running in browsers and, through Node.js, on servers as well. TypeScript adds static typing on top of JavaScript, catching errors earlier and making large codebases easier to maintain. Architects working on web or full stack projects need to understand both languages to evaluate frontend and backend technology choices. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/levels-of-architecture@2sR4KULvAUUoOtopvsEBs.md b/roadmaps/software-architect/content/levels-of-architecture@2sR4KULvAUUoOtopvsEBs.md index 45098da86..b76ba642b 100644 --- a/roadmaps/software-architect/content/levels-of-architecture@2sR4KULvAUUoOtopvsEBs.md +++ b/roadmaps/software-architect/content/levels-of-architecture@2sR4KULvAUUoOtopvsEBs.md @@ -1,3 +1,3 @@ # Levels of Architecture - + Architecture can be described at different levels of scope, ranging from a single application to an entire organization. Application architecture deals with the internals of one system, solution architecture connects several systems to solve a business problem, and enterprise architecture aligns technology strategy across a whole company. Each level requires a different set of concerns and a different audience. \ No newline at end of file diff --git a/roadmaps/software-architect/content/marketing-skills@YW6j3Sg511dXToTcwSnOS.md b/roadmaps/software-architect/content/marketing-skills@YW6j3Sg511dXToTcwSnOS.md index 758b3f530..706307ea9 100644 --- a/roadmaps/software-architect/content/marketing-skills@YW6j3Sg511dXToTcwSnOS.md +++ b/roadmaps/software-architect/content/marketing-skills@YW6j3Sg511dXToTcwSnOS.md @@ -1,5 +1,5 @@ # Marketing Skills - + Marketing skills help an architect present and sell technical ideas internally, convincing stakeholders and teams to adopt a proposed direction. This includes framing technical benefits in terms that matter to business decision makers, such as cost savings or reduced risk. Even the best architectural design needs buy in to actually get implemented. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/mvc-mvp-mvvm@jj5otph6mEYiR-oU5WVtT.md b/roadmaps/software-architect/content/mvc-mvp-mvvm@jj5otph6mEYiR-oU5WVtT.md index 20b4c91e0..a283ce67a 100644 --- a/roadmaps/software-architect/content/mvc-mvp-mvvm@jj5otph6mEYiR-oU5WVtT.md +++ b/roadmaps/software-architect/content/mvc-mvp-mvvm@jj5otph6mEYiR-oU5WVtT.md @@ -1,5 +1,5 @@ # MVC, MVP, MVVM - + MVC, MVP, and MVVM are patterns for separating an application's data, logic, and user interface into distinct layers. MVC splits responsibilities between model, view, and controller, MVP replaces the controller with a presenter that handles view logic, and MVVM introduces a view model that binds data to the view automatically. Choosing between them depends on the platform and how much automatic data binding a framework supports. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/net-framework-based@D1IXOBUrrXf5bXhVu9cmI.md b/roadmaps/software-architect/content/net-framework-based@D1IXOBUrrXf5bXhVu9cmI.md index a32ea84cb..e4108a3d4 100644 --- a/roadmaps/software-architect/content/net-framework-based@D1IXOBUrrXf5bXhVu9cmI.md +++ b/roadmaps/software-architect/content/net-framework-based@D1IXOBUrrXf5bXhVu9cmI.md @@ -1,5 +1,5 @@ # .NET Framework Based - + The .NET ecosystem, built around languages like C#, is widely used for enterprise applications, especially in Windows centric environments. It provides a large set of libraries and tools for building web, desktop, and cloud applications. An architect working in enterprise settings often needs to understand .NET's strengths around tooling, performance, and integration with Microsoft infrastructure. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/oop@AMDLJ_Bup-AY1chl_taV3.md b/roadmaps/software-architect/content/oop@AMDLJ_Bup-AY1chl_taV3.md index 580fe08a6..46a4468c3 100644 --- a/roadmaps/software-architect/content/oop@AMDLJ_Bup-AY1chl_taV3.md +++ b/roadmaps/software-architect/content/oop@AMDLJ_Bup-AY1chl_taV3.md @@ -1,5 +1,5 @@ # OOP - + Object oriented programming organizes code around objects that combine data and behavior, using concepts like encapsulation, inheritance, and polymorphism. It helps model real world entities and relationships in a way that keeps related code together and reusable. Most enterprise architecture patterns and languages rely on object oriented principles as a foundation. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/react-vue-angular@mCiYCbKIOVU34qil_q7Hg.md b/roadmaps/software-architect/content/react-vue-angular@mCiYCbKIOVU34qil_q7Hg.md index 8dea8b2a7..62aca4b4d 100644 --- a/roadmaps/software-architect/content/react-vue-angular@mCiYCbKIOVU34qil_q7Hg.md +++ b/roadmaps/software-architect/content/react-vue-angular@mCiYCbKIOVU34qil_q7Hg.md @@ -1,5 +1,5 @@ # React, Vue, Angular - + React, Vue, and Angular are popular JavaScript frameworks and libraries for building interactive web user interfaces through reusable components. React focuses on a flexible component model with a large ecosystem, Vue emphasizes simplicity and gradual adoption, and Angular provides a more complete, opinionated framework out of the box. An architect chooses between them based on team experience, project scale, and how much structure the framework should enforce. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/responsibilities@rUxbG2S2nJuA1YVY6sjiX.md b/roadmaps/software-architect/content/responsibilities@rUxbG2S2nJuA1YVY6sjiX.md index 3ea9a2750..7e2f136b0 100644 --- a/roadmaps/software-architect/content/responsibilities@rUxbG2S2nJuA1YVY6sjiX.md +++ b/roadmaps/software-architect/content/responsibilities@rUxbG2S2nJuA1YVY6sjiX.md @@ -1,5 +1,5 @@ # Responsibilities - + A software architect's responsibilities include defining system structure, choosing technologies, setting technical standards, and reviewing code for architectural consistency. They also assess risks, plan for scalability, and mentor developers on best practices. Beyond technical work, they communicate decisions to stakeholders and balance competing demands like cost, time, and quality. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/simplifying-things@lrtgF1RTaS4TCKww0aY6C.md b/roadmaps/software-architect/content/simplifying-things@lrtgF1RTaS4TCKww0aY6C.md index 8ecaa5f20..c5a9dbe8b 100644 --- a/roadmaps/software-architect/content/simplifying-things@lrtgF1RTaS4TCKww0aY6C.md +++ b/roadmaps/software-architect/content/simplifying-things@lrtgF1RTaS4TCKww0aY6C.md @@ -1,5 +1,5 @@ # Simplifying Things - + Simplifying things means reducing complex problems and systems into clear, manageable parts that others can understand and act on. Architects often deal with many moving pieces, and the ability to cut through unnecessary complexity leads to designs that are easier to build, test, and maintain. This skill also helps when explaining technical decisions to people without a deep technical background. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/solid@QNG-KP01WQnq8o1-In1-n.md b/roadmaps/software-architect/content/solid@QNG-KP01WQnq8o1-In1-n.md index 396f77d5f..c9e4b2037 100644 --- a/roadmaps/software-architect/content/solid@QNG-KP01WQnq8o1-In1-n.md +++ b/roadmaps/software-architect/content/solid@QNG-KP01WQnq8o1-In1-n.md @@ -1,5 +1,5 @@ # SOLID - + SOLID is a set of five object oriented design principles: single responsibility, open closed, Liskov substitution, interface segregation, and dependency inversion. Following these principles leads to code that is easier to extend, test, and maintain as a system grows. Architects use SOLID as a checklist when reviewing designs for long term maintainability. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/solution-architecture@uGs-9xE3DMJxKhenltbFK.md b/roadmaps/software-architect/content/solution-architecture@uGs-9xE3DMJxKhenltbFK.md index b1e28dad4..65ac9ebbb 100644 --- a/roadmaps/software-architect/content/solution-architecture@uGs-9xE3DMJxKhenltbFK.md +++ b/roadmaps/software-architect/content/solution-architecture@uGs-9xE3DMJxKhenltbFK.md @@ -1,5 +1,5 @@ # Solution Architecture - + Solution architecture designs how multiple applications and systems work together to satisfy a specific business need. It sits between application architecture and enterprise architecture, dealing with integration points, data flow, and technology choices across several components. A solution architect often works closely with project stakeholders to make sure the combined systems meet both technical and business goals. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/technical-skills@hFx3mLqh5omNxqI9lfaAQ.md b/roadmaps/software-architect/content/technical-skills@hFx3mLqh5omNxqI9lfaAQ.md index 1e2af1397..e7eff0153 100644 --- a/roadmaps/software-architect/content/technical-skills@hFx3mLqh5omNxqI9lfaAQ.md +++ b/roadmaps/software-architect/content/technical-skills@hFx3mLqh5omNxqI9lfaAQ.md @@ -1,3 +1,3 @@ # Technical Skills - + Technical skills cover the practical, hands on knowledge an architect needs, including programming languages, design patterns, tools, and infrastructure concepts. These skills give an architect the credibility and depth needed to make informed decisions rather than relying only on theory. The following sections break this knowledge down into specific areas like languages, patterns, and tools. \ No newline at end of file diff --git a/roadmaps/software-architect/content/trello@a6joS9WXg-rbw29_KfBd9.md b/roadmaps/software-architect/content/trello@a6joS9WXg-rbw29_KfBd9.md index aadbd144e..048bda1f2 100644 --- a/roadmaps/software-architect/content/trello@a6joS9WXg-rbw29_KfBd9.md +++ b/roadmaps/software-architect/content/trello@a6joS9WXg-rbw29_KfBd9.md @@ -1,5 +1,5 @@ # Trello - + Trello is a visual project management tool based on boards, lists, and cards that represent tasks moving through stages of work. Its simplicity makes it popular for smaller teams or lightweight project tracking compared to more complex tools. Architects may use it to track technical debt items or smaller initiatives outside a full project management system. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/understand-the-basics@4zicbh7Wg2lmKSRhb6E-L.md b/roadmaps/software-architect/content/understand-the-basics@4zicbh7Wg2lmKSRhb6E-L.md index 826d97c81..a55fb367a 100644 --- a/roadmaps/software-architect/content/understand-the-basics@4zicbh7Wg2lmKSRhb6E-L.md +++ b/roadmaps/software-architect/content/understand-the-basics@4zicbh7Wg2lmKSRhb6E-L.md @@ -1,3 +1,3 @@ # Understand the Basics - + Understanding the basics means knowing what software architecture is, what a software architect does, and how architectural decisions are structured across different levels of a system. It covers the terminology and mental models an architect uses before diving into any specific pattern or tool. This foundation shapes how later, more technical topics fit into the bigger picture. \ No newline at end of file diff --git a/roadmaps/software-architect/content/what-is-a-software-architect@eG38hT0rotYJ3G-t9df9R.md b/roadmaps/software-architect/content/what-is-a-software-architect@eG38hT0rotYJ3G-t9df9R.md index c00e69b4d..fee1cdc5e 100644 --- a/roadmaps/software-architect/content/what-is-a-software-architect@eG38hT0rotYJ3G-t9df9R.md +++ b/roadmaps/software-architect/content/what-is-a-software-architect@eG38hT0rotYJ3G-t9df9R.md @@ -1,5 +1,5 @@ # What is a Software Architect - + A software architect is the person responsible for making high level technical decisions on a project, including choosing technologies, defining system structure, and setting coding standards. They act as a bridge between business requirements and the engineering team, translating goals into a technical roadmap. The role combines deep technical knowledge with communication skills, since decisions need to be explained to both developers and stakeholders. Visit the following resources to learn more: diff --git a/roadmaps/software-architect/content/what-is-software-architecture@EGG99VA-PEdWdVxNDLtG_.md b/roadmaps/software-architect/content/what-is-software-architecture@EGG99VA-PEdWdVxNDLtG_.md index 35c5e2d73..ca7739dcb 100644 --- a/roadmaps/software-architect/content/what-is-software-architecture@EGG99VA-PEdWdVxNDLtG_.md +++ b/roadmaps/software-architect/content/what-is-software-architecture@EGG99VA-PEdWdVxNDLtG_.md @@ -1,5 +1,5 @@ # What is Software Architecture - + Software architecture is the high level structure of a software system: how it is divided into components, how those components interact, and the principles that guide their design. It defines the technical decisions that are hard to change later, such as how data flows between services or which technology stack underpins the system. Good architecture balances functional requirements with qualities like performance, scalability, and maintainability. Visit the following resources to learn more: