Post

On design: Thinking of 'One obvious way' versus 'expressiveness' (e.g. Python versus Ruby), not as a dichotomy but as a continuum, have the expressiveness AND then allow layering on the 'obvious way' for <thing> ([mono]repo, package, file, block, ...). In other words when designing an interface, ...

... don't necessarily see a fork in the road, but instead potential for both, expressive with _rigid presets_. You can think of a linter for example as a preset for a language. Ideally/But preset construction/sharing/use cannot be an afterthought, must be first class, seamless, near trivial. #api

0 reposts0 likes

No replies yet.