3 ms·
This is a complex and nuanced topic. I agree strongly with designing your code so it's easily changeable into whatever new features are needed. This is much ea
by BurningFrog 7y ago
This is a complex and nuanced topic.
I agree strongly with designing your code so it's easily changeable into whatever new features are needed. This is much easier said than done, and I don't know if anyone has written well about the tricks of that trade.
But anyway, if you have that kind of code, swapping out whatever you need to make line numbers happen is no more work later than sooner.
Code bases with features implemented that are never used, but you still have to keep working through all changes, because someone imagines it will be a real requirement someday, are what my nightmares are made of.
- jstimpfle 7y agoIt's all about the interfaces. More performant solutions require (in general) more complex interfaces. If your application has grown as long as it could with the simple implementation, and now it is all too slow, chances are there's a lot of code depending on the interface. If your interface (and the implementation) is too simplistic, then all of that code will need rearchitecting, too.