3 ms·
Nice article. There's one paragraph that exposes a certain bit of web dev mindset that rubs me the wrong way: "Updating things as you go also means that parts
by pavlov 10y ago
Nice article. There's one paragraph that exposes a certain bit of web dev mindset that rubs me the wrong way:
"Updating things as you go also means that parts of the application that get less love tend to be written with an older style [...] and using older technology (like indexOf rather than contains or a for loop rather than reduce)."
That's not "older technology"! You're talking about whether to use some helper methods on Array.prototype. Who cares? It's certainly not any kind of technology choice.
It's really no different from whether you prefer to put your opening curly brace on the same line as an if sentence or the next one. Sure, it's slightly annoying when someone does it differently, but you shouldn't spend any time bikeshedding your codebase over stuff like this.
- antjanus 10y agoYou're completely right! I meant to say that some parts of the application are written in an older style that we don't use anymore. For loops, indexOf, etc. are valid and there's nothing wrong with using them, we just use a more functional approach now and use some of the newer methods for doing the same thing.
- rajangdavis 10y agoI don't think this is necessarily a wrong thing; I feel like really ground breaking/challenging development forces you to understand what you are building the farther you go along. It's always ideal to have perfect code the first time it's written, my experience is that this is never going to happen unless you have perfected what you are building to the point that you have code generators/boiler plate code to cover most of what you are building. With that said, very interesting article. Thank you for sharing your experience, it is very eye opening for me.