|XP is just a number|
No. I simply try to develop coding habits that make the inherently unpredictable nature of the future less error-prone and less fraught.
Translation: You expend extra energy now, to potentially save energy in the future. That is guessing!
And if you guess wrong; you didn't just waste that extra energy; you potentially cost more energy undoing the product of that extra energy in order to accommodate the real future requirement.
No matter how you dress that equation in "experience", there is no way to make doing something now that you didn't need to do; in order to potentially save some immeasurable amount of effort that you might need to expend in the future; balance. Never has, and never will.
I'm sure you're right. But you seem to be berating me for something I neither suggested nor advocate.
Certainly not "berating". A frank exchange of views for the purpose of perhaps modifying our positions. (NB: Our own, not each others.)
I assume it is of some interest to you, as you are still taking part.
I was merely saying that I believe that code maintainability is generally more important than code performance. Which is why I still prefer the regex-based solution, even through it's three orders of magnitude slower.
This makes no sense to me.
It implies (not states) that you would condemn (strong word for effect) the users of the application to waiting 4 1/2 weeks instead of 1 hour; 15 weeks instead of 1 day; for the sake that this piece of code might need to be modified at some unspecified time in the future.
As a purely academic nicety, stating that you favour maintenance over performance is always a vote winner; but in the real world, code that does what it needs to do in a timely fashion is of far more importance than whether it was written in a declarative or functional style; or even if it might require the programmer to expend some effort to (re-)understand it in 6 months or 2 years from now.
Indeed, most users would say: "That's his damn job"!
Beyond old-farts like me playing 1stP shooters; I've never heard a user say he wishes his application ran more slowly.
It is the height of something for programmers to favour (potentially) saving a little of their time (for which they are well paid), in a future that may never arrive, over the time of the users who are generally paying (directly or otherwise) for the privilege of using the application.
With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.