Professional Engineering Practices
This path assumes you can already build a working application. It is about the decisions that determine whether that application is still pleasant to work on in three years.
Architecture is taught as trade-offs rather than patterns to apply. Every topic answers when to use something and, just as importantly, when not to — which is the guidance most material leaves out.
Prerequisites
- Experience building at least one complete application
- Comfort with interfaces and dependency injection
Technologies covered
The route
Take these in order. Each step exists because the previous one left something unresolved.
- Automated Testing
Tests that enable change rather than obstruct it.
- Software Architecture
Layering, SOLID, clean architecture, patterns and distributed trade-offs.
- Security for Developers
Defensive practice across identity, data, secrets and dependencies.
Refactor something you built
Take an earlier project and restructure it. Seeing your own code improve teaches more than reading a finished example.
Checkpoint — practice, not a course
Projects in this path
Reading alone will not get you there. These are the builds that turn the material into something you can actually do.
Document Management Platform
An architecture exercise: file storage, versioning, permissions and background processing, structured to stay maintainable.
Multi-Tenant SaaS Application
The hardest project here. Serve several customers from one system without ever leaking data between them.
Technologies in this path
Have a project worth talking through?
Tell us what you're building or what's slowing your current system down. We'll give you a direct read on scope and approach.