6 Matching Annotations
- Oct 2020
-
www.basefactor.com www.basefactor.com
-
If you want to implement a form with a superb User Experience, you have to take care of many variables:
Tags
- easy to get wrong
- too hard/difficult/much work to expect end-developers to write from scratch (need library to do it for them)
- difficult/hard problem
- user experience
- can't keep entire system in your mind at once (software development) (scope too large)
- form design
- a lot of things to consider
Annotators
URL
-
-
-
One of the primary tasks of engineers is to minimize complexity. JSX changes such a fundamental part (syntax and semantics of the language) that the complexity bubbles up to everything it touches. Pretty much every pipeline tool I've had to work with has become far more complex than necessary because of JSX. It affects AST parsers, it affects linters, it affects code coverage, it affects build systems. That tons and tons of additional code that I now need to wade through and mentally parse and ignore whenever I need to debug or want to contribute to a library that adds JSX support.
Tags
- engineering (general)
- complexity
- unintended consequence
- high-cost changes
- avoid complexity
- fundamental
- syntax
- for-reaching consequences
- primary task/job/responsibility
- mental bandwidth
- implementation complexity
- mentally filter/ignore
- can't keep entire system in your mind at once (software development) (scope too large)
- infectious problem
- semantics (of programming language)
- engineers
- the cost of changing something
- too complicated
Annotators
URL
-
- Sep 2020
-
refactoring.guru refactoring.guru
-
Eliminating needless classes frees up operating memory on the computer—and bandwidth in your head.
-
-
svelte.dev svelte.dev
-
Your styles are scoped to the component. No more leakage, no more unpredictable cascade.
-
It's fashionable to dislike CSS. There are lots of reasons why that's the case, but it boils down to this: CSS is unpredictable. If you've never had the experience of tweaking a style rule and accidentally breaking some layout that you thought was completely unrelated — usually when you're trying to ship — then you're either new at this or you're a much better programmer than the rest of us.
-
It gets worse when you're working on a team. No-one dares touch styles authored by someone else, because it's often unclear what they're doing, what markup they apply to, and what disasters will unfold if you remove them. The consequence of all this is the append-only stylesheet. There's no way of knowing which code can safely be removed, so it's common to undo some existing style with another, more specific style — even on relatively small projects.
-