I can live with that. I usually stop and abstract when I find myself repeating something the 2nd time because I don't want it to spiral out of control. I've been criticized in code reviews for abstracting too much into methods, some of them only having one or two lines. I abstract things early which may be repeated... that arguably can be another form of YAGNI lol.
But I do like the "do one thing and do it well" philosophy. 3 times is reasonable.
I will not abstract prematurelyI will not abstract prematurelyI will not abstract <when><who> will not abstract <when><who> will <shouldAbstract ? '' : 'not'> abstract <when>oh no
01:26 AM - 09 Aug 2019
Guilty. But lots of abstractions means faster running unit tests, right?
Not sure if you're sarcastic here, but if you're not our units under test originate in very different testing philosophies.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.