Software Engineering
Design principles, architecture, dependency injection, concurrency, queues and testing, with trade-offs rather than rules.
Beginner
2 guidesDRY, KISS and YAGNI: clean code principles in practice
What DRY, KISS and YAGNI mean, why DRY is about knowledge rather than similar code, how naming helps, and when an abstraction costs more than duplication.
The test pyramid: unit, integration and end-to-end tests
What the test pyramid recommends and why, how unit, integration and end-to-end tests differ, what makes tests flaky, and which tests to automate in CI first.
Intermediate
3 guidesDependency injection explained, with TypeScript examples
What dependency injection is, how constructor injection works in TypeScript, how it relates to IoC and DI containers, and when a function argument is enough.
Monolith vs microservices: trade-offs and when to split
How monoliths and microservices differ in deployment, data ownership, teams and operating cost, why a modular monolith is a middle path, and when to split.
Message queues and event-driven architecture explained
Queues vs pub/sub, why at-least-once delivery needs idempotent consumers, how ordering, retries and dead-letter queues work, and when to avoid events.
Advanced
2 guidesClean architecture: the dependency rule, ports and adapters
How clean architecture keeps business rules free of frameworks: the dependency rule, use cases, ports and adapters, folder layout and when it is overkill.
Race conditions: causes, examples and how to prevent them
What a race condition is, concurrency vs parallelism, a lost-update example, and the fixes: atomic updates, locks, isolation levels and idempotency keys.
Tools for this topic
Try what these guides describe on your own URLs, domains, code or files.