3 ms·
There's nothing like realizing, that feature you polished like a jewel? When implementing it, you brought all the patterns and best practices to bear that you c
by marktangotango 10y ago
There's nothing like realizing, that feature you polished like a jewel? When implementing it, you brought all the patterns and best practices to bear that you could. You archtitected the shit out of that thing! Yeah, no one uses that! That really puts things into perspective.
- Klathmon 10y agoMy favorite story about that is I created a really nice series of components in React. Fully functional, stateless, really nice clean testable code. A user gets it, it's "too fast", the designer wants to put an animation in there to slow it down and help give some context. Of course the animation means that once you "clear" the dialog it flashes to blank before "animating away" (because it's a beautiful stateless functional component!). So now the code is this hideous hacky bloated ugly solution, but it works...
- Rumudiez 10y agoThe view is inherently stateful. Ignoring that because the JS doesn't have to be will always get you trouble. Adding transitions, however fast they may animate, will be killer.
- Klathmon 10y agoI'm not shy of using internal state, but if I can get away with functional components, I will simply because of their simplicity and how easily they can be tested. But it was just more of a story about how sometimes ugly hacky code is better. Because at the end of the day, you are writing this for the user, not for yourself.
- shshhdhs 10y agoAnd to realize that feature was never invoked because you forgot to catch an exception a few lines before it.. Yeah.