I would like to invite you to my talk at the JetBrains Online Days (https://lnkd.in/deKUEXsR) on September 25th. I will be talking about Overcoming the Broken Window Syndrome and Code Verification Techniques for .NET developers. And I will especially focus on architecture erosion and how to avoid it. Architecture erosion happens when architecture rules, conventions, guidelines are only documented as text or diagrams, and not in an executable form. Therefore, architecture is only enforced during code reviews. Which has always gaps and erodes with time. We will explore different ways to make your architecture executable so you can enforce it in real time in the editor as squiggles and in your CI pipeline. See you soon!
Gael Fraiteur’s Post
More Relevant Posts
-
𝗖𝗹𝗲𝗮𝗻 𝗰𝗼𝗱𝗲 𝘁𝗶𝗽: Merge nested IF statements into one condition. This simple change can improve the readability of your code. But what is clean code in the first place? Clean code is code that's: - Easy to read - Easy to maintain - Easy to understand Writing clean code is a skill. And if it's a skill - 𝘆𝗼𝘂 𝗰𝗮𝗻 𝗹𝗲𝗮𝗿𝗻 𝗶𝘁. P.S. If you liked this, consider joining The .NET Weekly - my newsletter with 43,000+ engineers that teaches you how to improve at .NET and software architecture. Subscribe here → https://bit.ly/3SVO2Ij What do you think about pattern matching in C#? It's something I'm using more and more in my code.
To view or add a comment, sign in
-
Hi there!!! #Angular tip of the day 📣 Today, we're diving into Signals, one of the most revolutionary features introduced by the Angular team to enhance state management and improve performance. Signals are a new reactive primitive that offers more fine-grained change detection. Unlike traditional methods, Signals simplify state management and reduce the complexity that many developers face when handling large Angular codebases. Benefits of Signals: - Reduced Complexity: By eliminating the need for RxJS in state management, Signals simplify your code and make it more readable and maintainable. - Better Performance: With fine-grained reactivity, Signals ensure that only the necessary parts of your application update, leading to significant performance improvements. - Ease of Use: Signals are intuitive and easy to understand, making them accessible even to developers new to Angular. Signals vs BehaviorSubject? While both Signals and BehaviorSubjects are used for state management, Signals offer a more streamlined and efficient approach without the overhead of RxJS. This is achieved through synchronous updates and a simpler API. Consider using Signals in your next project for a more maintainable and performant Angular application. They are becoming an industry standard for good reason! Best Practices - Create Signals when the component is created: Unlike observables, which can be created on the fly, Signals should be instantiated when the component is initialized to ensure optimal performance. - Use Effects Wisely: Effects are powerful tools for logging data and syncing with `window.localStorage`, but try to avoid using them for updating state. - Minimize RxJS Usage: While RxJS is still valuable for handling events and complex scenarios, minimizing its use for state management can simplify your application. I Hope you enjoyed it!!🚀 Please let me know what you think. If you want to learn more about this subject, check out my Modern Large-scale Angular Enterprise Architecture course and learn to scale massive code-bases until infinity!🤓
To view or add a comment, sign in
-
Hello, this is my new video about Angular Clean Architecture - Part 4 - DTOs & Mappers. - I'll tell you why I think the Data Transfer Objects are important for communicating with the API. - What kinds of DTO we can distinguish - How DTOs relate to models that describe core business objects - Example of Mappers - And what can happen if don't use all these PR: https://lnkd.in/e3iWyYyJ Code: https://lnkd.in/eXzc7TED
Angular Clean Architecture Part 4 - DTOs And Mappers
https://www.youtube.com/
To view or add a comment, sign in
-
Hi there!!! #Angular tip of the day📣... Let's explore an essential principle of Angular component architecture - **Creating Smaller Components**. Why is this important? 🤔 - Maintainability: Smaller components are easier to read, understand, and maintain. - Reusability: They can be reused across different parts of your application, reducing redundancy. - Testability: Writing tests for smaller components is simpler and more efficient. - Performance: Small components can be loaded and rendered more quickly, improving the overall performance of your app. - Collaboration: Working on a codebase with smaller, well-defined components reduces merge conflicts and facilitates teamwork. Breaking down your application into smaller, focused components will lead to a more organized and scalable codebase. If you want to learn more about this subject, check out my Modern Large-scale Angular Enterprise Architecture course and learn to scale massive code-bases until infinity!🤓
To view or add a comment, sign in
-
Day-27 with #100DaysOfCode In a Node.js application, particularly when following the Model-View-Controller (MVC) architecture, *the controller folder* plays a crucial role in organizing your code and maintaining a clean separation of concerns. Here are some key points highlighting the importance of the controller folder: 1. Separation of Concerns: Isolates user input handling from data and presentation layers. 2. Modularity: Organizes related functionalities, making the codebase easier to navigate. 3. Maintainability: Simplifies updates and refactoring by localizing changes. 4. Reusability: Allows for shared logic across different parts or projects. 5. Testing: Facilitates independent unit testing of controllers. 6. Scalability: Eases the addition of new features without cluttering the structure. 7. Clarity: Enhances understanding of the application architecture for new developers. 8. Routing Management: Centralizes routing logic for streamlined request handling. #MERN #FULLSTACK #BACKEND
To view or add a comment, sign in
-
👨🚀 🚀 From aerospace schools to starry skies: choosing the right architecture for your .NET adventure! Just like an aerospace engineer carefully chooses components for a space mission, .NET developers need to choose the right architecture for their applications. Here are some popular architecture options for your .NET adventure: · Monolithic: A single application containing all components and functionalities. · Microservices: A distributed architecture where the application is divided into independent and scalable services. · Serverless: Implementation of functionalities without managing server infrastructure. · Layered architecture: Clear separation of responsibilities in different layers, such as presentation, business logic, and data access. Choosing the right architecture can determine the success of your .NET journey! Which architecture do you prefer for your .NET adventures? Share your choice in the comments! 🚀💻 ✨Get inspired, Get coding and Let's make coding life easier! 💪🏽 #codingLifeEasier #softwareDevelopment #developer #DotNet #AspNet #Architecture #CloudComputing
To view or add a comment, sign in
-
Automating Clean Architecture with a .NET and React Project Generator This generator simplifies project setup by: 1. Creating a React client project using create-react-app. 2. Structuring a .NET backend following Clean Architecture. 3. Automatically configuring references, dependencies, and skeleton files for each layer. 4. Setting up unit and integration tests to ensure a solid foundation. In just a few minutes, developers can have a scalable, maintainable, and testable project structure ready to go! 💻 Check out the article to learn more about how it works, the technologies involved, and how you can use the generator to streamline your development process. 🚀 🔗 https://lnkd.in/dN5h23h5 #DotNet #ReactJS #CleanArchitecture #FullStackDevelopment #Automation #WebDevelopment #DeveloperTools #TechInnovation #OpenSource
To view or add a comment, sign in
-
Hello, this my new video: Angular Clean Architecture Part 1 - Components With this video I start a series of videos dedicated to my vision Of Angular clear architecture. With every new video, the code base will grow, so you can see the whole thing. Perhaps in the future this will evolve into a true open source application. In this video I will talks how I deal with components on my projects: - folders structure and component naming - desktop and mobile versions - decomposition and encapsulations of components - why I no need BEM - organize code in component classes with private methods etc.
Angular Clean Architecture Part 1 - Components
https://www.youtube.com/
To view or add a comment, sign in
-
I'm excited to share my latest article on Code Maze! Explore the power of architecture tests in .NET using NetArchTest.Rules. Learn how to enforce conventions for class design, naming, and dependencies to ensure a robust and well-structured codebase. Dive in and discover effective testing techniques for your .NET applications. 🧪 Read the full article here: https://lnkd.in/g72ygbCK #csharp #dotnet #softwaretesting #softwarearchitecture
Architecture Tests in .NET with NetArchTest.Rules - Code Maze
https://code-maze.com
To view or add a comment, sign in
-
🌟"ASP.NET Core Clean Architecture" ! 🌟 Highly recommend this course for ASP.NET developers looking to master clean architecture principles. It's packed with practical insights on structuring applications for maintainability and scalability. Perfect for leveling up your skills in modern software design. Check it out and elevate your ASP.NET Core projects! 💻🚀 #AspNetCore #CleanArchitecture #Pluralsight
ASP.NET Core Clean Architecture
pluralsight.com
To view or add a comment, sign in
uQualio® - video training in the flow of work
3moBetter try to catch your talk there Gael Fraiteur