"No code" is code you don't control. Simple abstractions are a superpower, but you need to able to peel them off when the situation requires it.
Two anti-patterns:
1. The blackbox. You've outsourced critical logic to a thing you can't open at all.
2. The cliff: you can open the box, but understanding what's inside requires a completely different set of mental models and skills. Like driving vs repairing a car.
1. The blackbox. You've outsourced critical logic to a thing you can't open at all.
2. The cliff: you can open the box, but understanding what's inside requires a completely different set of mental models and skills. Like driving vs repairing a car.
Requiring users to have low-level expertise is also an anti-pattern (insufficient abstraction).
The best model to follow is "progressive disclosure of complexity": a hierarchy of levels of abstraction where each level builds on top of the previous one in an incremental way.
The best model to follow is "progressive disclosure of complexity": a hierarchy of levels of abstraction where each level builds on top of the previous one in an incremental way.