-
Notifications
You must be signed in to change notification settings - Fork 0
Home
https://gankra.github.io/blah/text-hates-you/
http://tiarkrompf.github.io/notes/?/smooth-tree-animation/aside13
I want to have a list of conventions forming some guidelines, and a set of automated checks to verify those conventions are not broken
No black magic, inheritance, implicit behavior (middleware, attributes, weak connections), monads, dups, dependencies, implicit dependencies/events/checks/triggers
prove system correctness. Strong types and tests
Infrastructure map (how data flows through services/servers/network and how it scales)
Architectural layers map (what subsystems you have for storing/transforming data)
Bounded contexts (how your logical services are split and mapped to architecture)
Main use cases dataflows (CRUD operations, data streaming/pushes, auth, payments)
Limit the number of cross-context dependencies
Tests for main/critical use cases (ideally integration tests - starting from UI interactions)
document all different ways you can add a new feature.
limit the number of ways you can do that.
Ideally - having as few options as possible, every feature should be similar technically to others.