#Architecture
18 notas · última:
10 ways to better organize and design your React Application
The page argues that React code organization affects findability, maintenance, and growth. It recommends domain-based folders, absolute paths, shared common modules, wrappers for third-party code, local code placement, and pinned dependencies.
Smart core, thin interfaces
The post argues for keeping business logic in a small, smart core and putting actor-specific handling at the edges, where inputs are sanitized and interfaces hide messy details.
Finding modules in a big ball of mud
The post argues that tangled code is normal and that modules should be found by reading dependency graphs, matrices, and domain neighborhoods rather than forcing an early architecture.
Architecting monoliths for fast, sustainable flow
The post explains that fast, sustainable flow depends on team-sized, loosely coupled, testable, deployable, observable, and evolvable systems, and shows how monoliths can meet some of those goals only with careful design.
The best of Angular: a collection of my favorite resources of 2024
The selection gathers 2024 articles about new Angular versions, Signals, Resource API, forms, interceptors, architecture, and other practices to follow the framework's evolution.
How Senior Software Engineers Document Their Project
The article argues that ADRs help teams record architectural changes, their impact, and what was learned, so future developers can understand decisions and avoid relying on memory.
I hate "Quick Wins"
The text argues that quick wins tend to generate technical debt, misalignment of goals, a worse user experience, and compromised architecture, and it defends a long-term vision and incremental delivery.
Sustainable Building Effort Reaches New Heights With Wooden Skyscrapers
Mass timber lets architects build tall with manufactured wood instead of steel and concrete, cutting emissions but carrying open questions on fire, moisture, and real carbon accounting.
Top 10 Angular Architecture Mistakes You Really Want To Avoid
Tomas Trajan catalogs ten recurring Angular architecture mistakes, from missing eager/lazy boundaries and duplicated routing patterns to skipping dependency-graph tooling and standalone components.
CQRS
CQRS — Command Query Responsibility Segregation — is a pattern first described by Greg Young. At its heart is the notion that you can use a different model to update information than the model you…
The two patterns by which agents connect sandboxes
The post describes two ways to connect agents to sandboxes: run the agent inside the sandbox for tighter coupling, or keep the agent outside and use the sandbox as a tool for easier updates and cleaner separation.
Por que não uso MediatR para CQRS
Cezary Piatek argumenta que MediatR é uma boa implementação do padrão mediator — mas o mediator pattern resolve um problema diferente do CQRS. Usar MediatR para CQRS introduz fricção desnecessária em…
Complexity is not a goal. I don't want to be remembered as an engineer of complex systems.
David Parnas, em entrevista ao perfil ACM Fellows. O contexto: Parnas critica engenheiros que se orgulham de construir sistemas grandes e complexos. Sua contribuição conhecida é o oposto — o…
Reactive programming vs. Reactive systems
The article distinguishes reactive programming from reactive systems: the first improves local asynchronous dataflow, while the second is an architectural style for resilient, elastic, message-driven distributed systems.
Why I Left the .NET Framework
The author says .NET was strong, but its defaults narrowed choice, pushed developers inward, and kept implementation details ahead of the model and business behavior.
Autodidacticism
Autodidacticism is self-directed learning, related to but distinct from informal learning. The article links it to modern education, historical cases, literature, architecture, and online learning.
Part 2 - Architecture | xamarin
The page explains that cross-platform apps should maximize code sharing through encapsulation, separation of responsibilities, and polymorphism, then maps those ideas to common application layers and mobile software patterns.
Building Cross Platform Applications | Xamarin
The guide explains how Xamarin supports cross-platform mobile apps by combining shared C# and .NET code with native UIs on iOS, Android, and Windows Phone, using a layered architecture and core library for reuse.