Standard Architecture Patterns must be used by Agents

As an app architect, we depend on standardized coding patterns. They shorten debugging times and encourage proper testing.

All db functionality should be routed through a storageFactory. Mobile-first, offline? No problem. Cache it, route it, sync it. Multi-Tennant SaaS? No problem. Route it!

All error functionality should be routed through an errorFactory. Trap it, log it, route it!

All apps must be HIPAA compliant. This suggests securityFactory. Split it, De-identify it, route it!

All apps with purchase capabilities require purchaseFactory.

These are tried & tested patterns. The Agents must code according to them! Try/Catches scattered throughout the app? BUZZZZ. Sorry. Can’t test that. BOOOO. Users seeing technical error messages? BUZZZZZ. Sorry. We just lost another User. They moved on to a more friendly app. Users seeing other User info? Here come the attorneys and insurance representatives.

Yes, the Agents are very good.

They can be better.

Start with some standardized coding practices and Factories.