Software Engineering — Overview
This section covers the craft of building software that lasts: how to structure code, how to design systems that scale and survive failure, and how to work well as an engineer. Examples use Python and TypeScript (labelled in each lecture). The lectures build on each other, but each stands alone, with cross-links where ideas connect.
Roadmap
Section titled “Roadmap”- Core Principles: complexity, cohesion and coupling, SOLID, DRY/KISS/YAGNI, composition over inheritance.
- Design Patterns I: Creational: factories, builders, prototype, singleton’s problems, dependency injection.
- Design Patterns II: Structural: adapter, decorator, facade, proxy, composite, bridge, flyweight.
- Design Patterns III: Behavioral: strategy, observer, command, state, template method, iterator, chain of responsibility, visitor, mediator.
- Architecture Styles: layered, hexagonal, modular monolith vs microservices, event-driven, CQRS, event sourcing, DDD basics.
- API Design: REST, gRPC, GraphQL, versioning, idempotency, pagination, errors, OpenAPI.
- Databases & Data Modeling: normalization, indexes (B-tree, LSM), transactions and isolation, SQL vs NoSQL, query plans, migrations.
- System Design Fundamentals: requirements, estimation, latency numbers, load balancing, caching, CDNs, queues, sharding, replication.
- Distributed Systems Theory: CAP/PACELC, consistency models, consensus, clocks, failure models, sagas, exactly-once myths.
- System Design Case Studies: URL shortener, rate limiter, news feed, chat, notifications, autocomplete.
- Concurrency & Parallelism: threads, async, locks, memory models, actors, deadlocks, structured concurrency, the GIL.
- Testing & Code Quality: test pyramid, property-based and contract tests, TDD, mocks vs fakes, mutation testing, refactoring, review.
- Reliability, Performance & Security Basics: SLOs, observability, profiling, resilience patterns, OWASP, threat modeling, authn/authz.
- Engineering Practice: version control workflows, design docs and ADRs, technical debt, estimation, AI assistants, career habits.
Prerequisites
Section titled “Prerequisites”- Comfortable programming in at least one language; the examples use Python 3.11+ and TypeScript.
- Basic familiarity with Git, the command line, HTTP, and SQL.
- Elementary data structures and algorithms (hash tables, trees, Big-O). No advanced mathematics required; a little probability helps in the distributed systems and estimation material.
Suggested study plan
Section titled “Suggested study plan”About 35-45 hours for a first pass, spread over 6-8 weeks:
| Week | Lectures | Focus | Hours |
|---|---|---|---|
| 1 | 1-2 | Principles, creational patterns; refactor a small project of your own | 5-6 |
| 2 | 3-4 | Structural and behavioral patterns; implement 3-4 from memory | 6-7 |
| 3 | 5-6 | Architecture and APIs; sketch a hexagonal service and write its OpenAPI spec | 6-7 |
| 4 | 7-8 | Databases and system design fundamentals; run EXPLAIN on real queries; practice estimation |
7-8 |
| 5 | 9-10 | Distributed theory and case studies; design two systems on paper and critique them | 7-8 |
| 6 | 11-12 | Concurrency and testing; write property-based tests; reproduce a race | 6-7 |
| 7 | 13-14 | Reliability, security and practice; write an ADR and an SLO for a service you own | 5-6 |
Tips: do the exercises, since design skill comes from practice rather than reading; revisit lectures 8-10 together before system design interviews or design reviews; and treat lectures 1, 12 and 14 as habits to apply daily rather than topics to finish.