Rehash of a Reiteration of a Revamp of a…

It is infinitely easier to remake something than to make something. Retrofit, recreate, reuse, recycle, whatever you term it, when a concrete formula is already established and all that remains is to improve a few aspects, that’s when you’ve got a simple project, so simple that it almost seems foolish to not undertake it.

For reference, see: Pokémon games, the smartphone market, C/GPU releases, and “Hello World!”

I find myself falling into that trope a lot. There’s always something to lose myself in, some gain to squeeze out.

I’ve been learning Svelte. “Hmm, perhaps I should remake Melrady in Svelte! Wouldn’t that be fun?” I’ve nearly finished Guide to Scientific Computing in C++, I should take the improved systems from my web sorting algorithm visualizer and use them to rewrite my Python sorting algorithm visualizer (lol) with C++ “For the efficiency gains, of course! Think of the speed!” Mental folly.

Art, applications, music albums, movies, and so much more (usually) benefit from a revamp, and that’s great. Redo everything, down to the bleeding edge! Squeeze that nanosecond of extra performance out, it always adds up, yah?! Maybe, if the time invested implementing such improvements isn’t better used elsewhere.

It’s nice to redo something if you find glaring issues with it, because if you see problems, your users probably do too. But that concept must be held in moderation: You can do/make one thing really well, but growth is necessary too. Bonus point if you can grow the scope of one project you’ve already done really well, add new features, et cetera, et cetera!

All the fun of optimization, with the added quest of innovation.