fp-design

Designing software architecture using functional programming principles involves modeling domains with ADTs, structuring effect and purity boundaries, and designing concurrency to surface type invariants before implementation. It produces design docs or critiques without writing code, explicitly naming tradeoffs.

Critiquing a proposed design for illegal states and missing exhaustiveness requires reviewing type and state-machine invariants from a functional-programming perspective. It identifies misplaced effects, weak error handling, and FP over-reach or under-reach, outputting both elegant and pragmatic recommendations.

Yes, functional programming design patterns apply across different languages by reviewing type and state-machine invariants universally. The approach provides dual-output guidance: an elegant FP design direction plus a pragmatic recommendation specifically tailored to match your language and team context.

Modeling domain data with algebraic data types (ADTs) involves structuring your data modeling strategy during brainstorming mode to explore functional approaches. This process evaluates effect boundaries and composition strategies to ensure type safety and eliminate illegal states before committing.

You should avoid a strict functional programming approach when the tradeoffs outweigh team context or language constraints. The critique explicitly contrasts an elegant FP option with a pragmatic recommendation, identifying FP over-reach where strict purity creates unnecessary friction in your environment.

No, fp-design does not write implementation code for functional programming architectures. It focuses strictly on design decisions by producing design docs or critiques that analyze effect boundaries, ADT modeling, and concurrency tradeoffs without generating the actual source code.