Application Developer: Anti-patterns
Reference: This page is a source-based technical synthesis of the LaTeX chapter cited below. For exact syntax, availability or ABI signatures, verify the versioned source, manifest and executable tests.
Scope and source boundary
Common developer anti-patterns include encoding domain authority in views, bypassing model validation and treating implementation types as semantic contracts.
The developer guide describes a progression from business concepts to declarations, validation, activated runtime models and published capabilities. Declarative modeling, native operationalization and generated bindings are complementary implementation paths. The smallest path that preserves the intended domain meaning should be preferred.
Engineering rules
- Start with vocabulary, identity and business scenarios.
- Validate the conceptual model before adding implementation adapters.
- Choose declarative, scripted or compiled execution by measured need.
- Publish and test the resulting contract before extending to more complexity.
Chapter outline (original LaTeX headings)
- The Central Decision Chain
- Choose the Construction Path Before the Artifacts
- Decision Table
- Quick Questions Before Creating Anything
- Common Beginner Decisions
- Concept or Field?
LaTeX provenance
Primary chapter: Declarative Conceptual Programming with the logiCells Platform/developer-guide/chapters/design-decision-guide.tex.