Hi Deestann, good catch, I should have stressed that these are guidelines not rules, what I meant is if possible use positive logic, but it fits better the negative, use the negative one.
you are absolutely right with your observation, that variable name its just a bad example, I have just edited the post and I have changed its name to daysDateRange.
Hi swombat, thanks for your comment, I actually completely agree on what you say: "Over-engineered code is as much in need of a refactoring as under-engineered code" I should have also mention that on the original article. Good observation, thanks!!!!
Hi callmeed and any other eventual reader, please accept my apologies for my bad writing in English, I hope you will understand it's not my native language and that I do my best, anyway, going forward I will try to get my articles reviewed from some native speaker guy before publishing them. Thanks for your comment!!!
@Janzert - About the first image, sorry about that, I have just changed to a gif image, now it should be a few kb, thanks for that.
@jhancock - You are right to mention that there is no comment on how to measure any of the vertex, that´s the tricky part, I am going to evolve the idea in future posts and I hope I will be able to provide with some ideas, anyway I think the most important thing is to have in mind the pyramid when developing
@silentbicycle - Sorry if my post is short, I just wanted to share this idea and as I like the articles that are very lean I thought the best was to express it with as less words as possible.