Engineering Playbook · Open Source

Collect all eight cards

Our core software engineering protocols, boiled down to one card each. Read them over coffee, copy the rules, and enforce them across your pull requests.

The Playbook Stack

No. 01Velocity

The 14-Day MVP Rule

"Ship the core loop in two weeks or rescope the sprint."

A project that takes 6 months to see real users is dead on arrival. Cut all nice-to-haves. Build the single transaction or workflow users pay for first.

The Iron Rule

Validation in the wild beats opinions in a boardroom every single time.

No. 02Architecture

Schema-First Architecture

"Model your database constraints before drawing buttons."

A flawed database schema will haunt you for years. We enforce strict foreign keys, atomic transactions, and UTC timestamps on day one.

The Iron Rule

Fixing a database migration on a live system with 100k users is 100x more expensive than designing it right.

No. 03Frontend

Optimistic UI Updates

"Never make a user stare at a full-page spinner."

Mutate the user interface instantly on click, and reconcile with the server in the background. If the network fails, roll back gracefully.

The Iron Rule

Perceived speed is the difference between an app feeling sluggish and feeling like magic.

No. 04Mobile

Offline-First Mobile Sync

"Assume cellular data will drop mid-checkout."

Store state in a local SQLite or Hive cache first, queue mutations, and sync when connectivity restores. The app never crashes on bad signals.

The Iron Rule

An app that works on a slow 3G connection in rural India will fly anywhere in the world.

No. 05DevOps

Boring Technology Wins

"Choose tech that has been battle-tested for ten years."

Postgres over exotic niche databases. Standard Docker containers over complex multi-region Kubernetes clusters before you have 10,000 customers.

The Iron Rule

Spend your innovation tokens on your actual business logic, not on debugging infrastructure.

No. 06Engineering

End-to-End Type Safety

"Catch bugs at compile time, not in customer support."

TypeScript on the frontend, typed SQL or ORM schemas in the backend, and shared contract types so API mismatches never reach production.

The Iron Rule

A 10-second type error in development saves 3 days of customer support firefighting.

No. 07Standards

Zero Spaghetti Code Policy

"Write code so clean that any engineer can onboard in 24 hours."

Clear file structures, modular components under 200 lines, self-documenting function names, and zero undocumented clever hacks.

The Iron Rule

Code is read 10x more often than it is written. Optimize for readability.

No. 08Operations

Telemetry Over Guesswork

"If you can’t measure latency, you can’t optimize it."

Instrument every API endpoint, database query, and user funnel. Set up real-time error alerts in Slack so you fix bugs before customers report them.

The Iron Rule

The best error report is the one resolved before the customer realizes anything happened.

Protocol Downloads

Most referenced in production

rules you will thank yourself for in year two

  1. 1

    The 14-Day MVP Rule

    Ship the single paying transaction first. Rescope or cancel nice-to-haves.

    5,420 citations
  2. 2

    Schema-First Architecture

    Fixing a database migration on 100k users costs 100x more than designing constraints right.

    4,190 citations
  3. 3

    Boring Technology Wins

    Postgres over exotic multi-model databases before 10,000 paying accounts.

    3,850 citations

Need senior engineers to execute?

Rather we run the sprint for you?

The playbook is how Teklin builds software every week. If you’d rather delegate execution to a battle-tested squad, we’ll build your entire core app in a 2-week sprint.

View Sprint PricingFixed Sprints

Sprint Commit Snapshot

Teklin Sprint Architecture

Sprint Length:14 Business Days
Squad Allocation:Full-Stack Lead + Product Designer
Daily Updates:Shared Slack + Async Loom + GitHub
IP Transfer:100% Client Ownership