A bit sarcastic, but makes its point efficiently. It's important to realize that more code to maintain is definitely not what we need.
Calls a bit too much everything mocks while the term test double would have done the job. Still it stresses fairly well the importance of being as close to reality as possible and the tradeoffs we have to make.
Where does this style of tests shine? A few elements to consider.
Nice little article about Conway's Law. Shows nicely all the ramifications it has.
It's definitely tempting me to switch my blog comments to the fediverse as well.
Black has been getting too much of a bad reputation in the last few years. This article makes a good job arguing for a more balanced view.
It'll be interesting to see where this complaint goes.
Very nice article. We must not loose from sight that actual learning requires some sort of effort. Even better when it's coupled to using your hands (definitely why I still take notes written by hands for some things).
I'm not necessarily convinced this is as much a silver bullet as it is presented here. Still there are benefits to such a structured approach for reviews in community projects.
I mostly agree with this. I'd just complete it a bit: it's probably a good idea to have at least one language where you went really deep in (emphasis on at least). A kind of strategy to aim at "T shaped skills" (or better "paint drip shaped skills").
In praise of property based testing. This definitely completes well the tests you write by hand.
This is a welcome consequence of the CJUE ruling. Be warned, think twice before reaching for Google Analytics.
Remote work is clearly the best way for smaller companies to compete to attract talent. This greatly increases the size of the pool of potential hires.
Interesting optimization on this somewhat common data structure.
This often overlooked indeed... and to make it worse it can be hard to optimize.
Interesting proof of concept. I wonder how far this will go. There is definitely a need in any case.
Excellent piece from an excellent artist. I really thought this through and I think he's going in the right direction.
This would be an interesting extension to the Java Stream API. Maybe one day it'll make its way to the standard...
This is a neat example of what programming languages could check at compile time. This clearly brings way more safety when you get such contract validation at build time.
I always felt uneasy around this "law" as well. It's a good deconstruction of it and proposes proper alternatives. It's all about dependencies really.