
…”. You write your code naturally, then you measure it. If there are performance problems, fix them. We don’t need to prove an inline arrow function is fast, somebody else needs to prove it’s slow. Otherwise it’s a premature optimization.
A critical mistake I made was designing “on-the-fly”, aka making things up as I went. Not only did this slow down development, but it caused me to change the design multiple times throughout. This in turn altered backend requirements, so as you can imagine this is just plain awful ☺. I think it’s good to prototype so you can get a feel of what things could be, but once you start ex…