Christian Rackerseder | Blog
-
Passive event listeners are a promise to the browser
Passive event listeners let browsers scroll without waiting for JavaScript. The benefit comes from understanding what the listener gives up.
-
Feature flags separate deployment from release
Use feature flags to deploy incrementally, test with internal users and release gradually while keeping a way to disable new behavior.
-
Named arguments in JavaScript
Use object parameters to make function calls easier to read, distinguish values of the same type and expose boolean flags that deserve a better design.
-
A generated API client is not a trust boundary
Generated TypeScript types describe API responses. Runtime validation checks the data before the application uses it.
-
Responsive vs. adaptive web design
How fluid layouts differ from predefined layout sizes, why both can use breakpoints and what that means for implementation and testing.
-
Classes are the wrong default in JavaScript
Prefer pure functions for rules and closures for construction. Classes should solve a concrete problem, not become the default shape of application code.
- Prefer explicit returns in TypeScript
- Ship Node.js applications as a single executable
- Start with semantic HTML
- Make resource lifetime explicit with using
- Comments are not a substitute for design
- Runtime validation is a boundary concern
- Not every test double is a mock
- Fire and forget still needs an owner
- Translations belong to the user interface
- Don't log at the leaf. Log at the root
- Boring code is a feature
- Time is an external dependency
- Bugs are not backlog items
- Clean Architecture protects the happy zone