RDPCORE / SOFTWARE

Software development,
from code to release.

Follow a change from its first commit through testing and release. Explore the choices that make code easier to debug, review and maintain.

● ● ●

01const idea = {

02 curiosity: true,

03 possibilities: ∞

04};

05build(idea);▏

❯An idea is ready. Your turn.

Interactive visual demo · does not execute real code

Write Tests Around Boundaries, Not Implementation Details

Use the cent below, at and above a shipping threshold to specify behavior without coupling tests to helper calls.

Read the first bad estimate and repeated inner work before adding an index. A cheap node can be expensive when it runs thousands of times.

Old workers and new workers can coexist during a release. Keep both versions correct through expansion, backfill, read switch and cleanup.

Keep an unfinished change in place while reviewing a specific commit in another directory. Isolate the database and port as well as the checkout.

First make the duplicate invoice reproducible. Then use the good-to-bad boundary to locate and test a causal explanation.