Shipping is the easy half. The hard half is deciding what the thing is supposed to do for someone who has never read your roadmap and does not care about your architecture.
This piece walks through how we think about it at Paycux, what we have changed our minds about, and where the sharp edges are.
What we are building
Consider what we are building. Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Setup
Setup deserves its own treatment. Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
- Choose defaults as carefully as features
- Settle the name before you ship the thing
- Ship the smallest honest version
- Say plainly what the feature does not do
Two design decisions before writing any code
Two design decisions before writing any code is where this gets concrete. Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Storing PII: createObject
Storing PII: createObject deserves its own treatment. Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Ship the smallest version that is honest about its limits.
Naming convention
Naming convention deserves its own treatment. Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Defaults are the product. Most people will never open the settings screen, which means the behaviour you chose for them is the behaviour they will experience forever.
Storing a single field
Consider storing a single field. Ship the smallest version that is honest about its limits. A feature that does one thing completely beats one that does five things with an asterisk on each.
Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Storing a full user profile
Storing a full user profile is where this gets concrete. Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Naming is design work. If the team argues about what to call something, the disagreement is usually about what it is, and shipping before that is settled means shipping the confusion to customers.
Where this leaves us
If there is one thing worth taking away, it is that the expensive decisions are the ones made implicitly. Making them on purpose costs an afternoon.
If you are working through the same problem and want to compare notes, the docs cover the mechanics and the console shows the behaviour on your own data.
Everything here, already built
Sign-in, enterprise SSO, directory provisioning, roles and an audit trail behind one API. Start with the quickstart and have a working sign-in this afternoon.