4 Matching Annotations
- Nov 2020
I'm still calling this v1.00 as this is what will be included in the first print run.
There seems to be an artificial pressure and a false assumption that the version that gets printed and included in the box be the "magic number" 1.00.
But I think there is absolutely nothing bad or to be ashamed of to have the version number printed in the rule book be 1.47 or even 2.0. (Or, of course, you could just not print it at all.) It's just being transparent/honest about how many versions/revisions you've made. ￼
- magic values
- too much importance placed on something
- too much ceremony/bureaucracy
- focused too much on the wrong thing
- artificial pressure
- false assumptions
- Oct 2020
Since re-rendering in Svelte happens at a more granular level than the component, there is no artificial pressure to create smaller components than would be naturally desirable
- Sep 2020
Since re-rendering in Svelte happens at a more granular level than the component, there is no artificial pressure to create smaller components than would be naturally desirable, and in fact (because one-component-per-file) there is pressure in the opposite direction. As such, large components are not uncommon.