Clean architecture
Point source dependencies inward to protect application policy.
Open field noteA field guide for your next project
Catalog
Learning resources for understanding and comparing concepts and choices. Choose a category to explore examples and tradeoffs.
Search within: Catalog
78 field notes
Architecture boundaries & dependencies
Service decomposition
Microservices
Deploy capabilities independently when operational independence justifies coordination.
Open field note
Modular monolith
Enforce module ownership while retaining one deployment unit.
Open field note
Monolith
Deploy together when simple operations outweigh independent releases.
Open field noteAI development workflows
No additional skills
Use existing agent instructions and checks when extra workflow setup adds little value.
Open field note
OpenSpec
Keep current specifications alongside reviewed change proposals and deltas when evolving agreed behavior.
Open field note
Spec Kit
Track requirements through a specification, plan, tasks, and implementation checks when shared rules need durable agreement.
Open field note
Superpowers
Use composable development skills when repeatable design, testing, debugging, and review steps are the priority.
Open field noteStatic site generators
Web UI development tools
React
Build interfaces from components and state, suited to teams that want JavaScript-driven rendering and explicit state ownership.
Open field note
Svelte
Compile declarative components when concise reactive authoring matters.
Open field note
Vue
Bind templates to reactive state for template-oriented authoring.
Open field noteGame engines
Version control systems
Git
Distributed history and branches for local work with a separate choice of hosting.
Open field note
Mercurial
Distributed version control with sharing phases, suited to an established hg workflow.
Open field note
Perforce P4
Version control suited to asset workflows that need configured exclusive file editing.
Open field note
Apache Subversion
Centralized version control for teams retaining an established SVN repository and workflow.
Open field noteRepository hosting
Azure Repos
Repository collaboration with branch policies inside an existing Azure DevOps workflow.
Open field note
Bitbucket
Git hosting with Jira-linked development work for teams using Bitbucket Cloud.
Open field note
Codeberg
Community-operated Git hosting for projects aligned with a nonprofit free-software mission.
Open field note
Gitea
Self-hostable Git collaboration for teams willing to own service operations.
Open field note
GitHub
Git hosting and pull-request collaboration where contributors already work on GitHub.
Open field note
GitLab
Git collaboration connecting merge requests and configured CI in one workflow.
Open field noteHosting execution models
Always-on server
Keep a process listening for requests, with runtime control and responsibility for capacity, supervision and recovery.
Open field note
Serverless functions
Run event-triggered work without owning long-lived compute processes.
Open field note
Static hosting
Serve prebuilt public files with minimal application operations.
Open field noteLayout
List layout
Repeated rows align text and metadata when scanning comparable fields matters more than image variety.
Open field note
Masonry
Pack varied-height items into short columns when preserving image proportions matters more than shared rows.
Open field note
Multi-region layout
Coordinate navigation, active content and context in distinct regions when they must be seen together.
Open field note
Single-column layout
One vertical reading stream suits content whose next step should be unambiguous.
Open field note
Sidebar layout
Keep navigation, filters or supporting information beside the main content so both remain available.
Open field note
Uniform grid
Equal-width cards and shared rows support fair comparison of similarly structured items.
Open field noteStyles
Brutalism
Raw typography and exposed structure suit an intentionally utilitarian visual voice.
Open field note
Flat design
Solid surfaces and explicit labels establish hierarchy when simulated depth adds little value.
Open field note
Glassmorphism
Use translucent, blurred panels to preserve background context while keeping foreground content readable.
Open field note
Liquid Glass
An adaptive, floating control material preserves rich content beneath a distinct navigation layer.
Open field note
Material 3 Expressive
Color, shape, size and motion emphasize key actions within the Material design system.
Open field note
Minimalism
Reduce competing elements to focus attention while retaining essential information and controls.
Open field note
Neobrutalism
Bright blocks, thick outlines and hard shadows give selected content deliberate graphic emphasis.
Open field note
Neumorphism
Similar-tone surfaces and paired shadows suggest soft raised or pressed controls.
Open field note
Retro digital
Early-computer windows, pixel details and type evoke a deliberate digital nostalgia.
Open field note
Skeuomorphism
Familiar object and material cues explain digital content through a recognizable physical metaphor.
Open field note
Tactile collage
Layered paper, tape and fragments create an assembled, handmade visual character.
Open field noteTypography
Monospace
Equal character advances suit aligned text data; shape and fallback coverage remain separate concerns.
Open field note
Proportional
Varying character advances suit flowing text; letter spacing is a separate adjustment.
Open field note
Sans serif
Letterforms without serifs suit a plain visual voice; readability still depends on the chosen face and context.
Open field note
Script
Handwritten strokes suit short expressive lettering while ordinary text carries detailed instructions.
Open field note
Serif
Finishing strokes at letter terminals create a distinct text texture; choose by editorial tone and tested legibility.
Open field noteRevenue sources
Advertising
Advertisers fund access when audience attention has commercial value.
Open field note
Affiliate commissions
Earn a referral commission when an external purchase qualifies.
Open field note
Customer direct payment
Users fund access when its value supports payment.
Open field note
Sponsorship
Fund shared resources through support rather than access sales.
Open field note
Transaction fees
Take a share of completed marketplace transactions.
Open field noteBilling methods
One-time payment
Collect once when a bounded purchase can fund its promise.
Open field note
Prepaid credits
Collect before consumption and spend a bounded credit balance.
Open field note
Subscription
Charge over recurring periods for continuing value; define renewal, payment failure and access policies.
Open field note
Usage-based billing
Bill measured consumption when work varies by customer.
Open field noteSeller responsibility models
Pricing models
Base fee plus overage
Combine an included allowance with a charge for excess usage.
Open field note
Feature-tiered pricing
Price distinct capabilities when customers need different feature sets.
Open field note
Flat-rate pricing
Charge one package price when a predictable bundle matters most.
Open field note
Graduated pricing
Price each quantity band separately and add the subtotals.
Open field note
Per-seat pricing
Scale price with licensed people when access per person drives value.
Open field note
Volume pricing
Apply the reached quantity tier’s rate to every unit.
Open field note
