tag(s): #emacs #programming I am 100% convinced that choosing the simplest solution possible is always the better choice. My reasoning goes like this: if you approach a module/subsystem/function (the level of granularity doesn't matter, it applies at all levels) with the most boneheaded approach possible, your code/architecture/etc. will be stupid simple. This might have "obvious drawbacks", but it has the undeniable advantage of being the fastest way to get something up and running. It also has the best probability of being bug-free, since it should be a very straightforward implementation. Once you have something that runs, you can revisit your assumptions about these "obvious" problems. About half the times, the real problems will not be where you expected them, and you will be happy that you didn't jump to conclusions. Oh look at that, I didn't need to parallelize the math of BLEH, but to focus on reading the BLAH files in sequence, who knew...well, not you, until you tried. And…
No comments yet. Log in to reply on the Fediverse. Comments will appear here.