I watched an interesting YouTube recently: I get what he’s saying, and I totally disagree. Testing against “behaviors” while ignoring implementation details (classes and methods) is a great way to leave a significant fraction of your code uncovered. It also lets you get away with designing crap that’s good for the “behavioral test” but which […]
Author Archives: PDQ
Why I Advocate for SOLID, TDD, and 100% Code Coverage
I’m not telling you to use SOLID and TDD because I read some cool stuff on a blog somewhere. I’m telling you to use them because your code needs to have the following attributes: It must be easy to understand. It must be easy to maintain. It must not expose stakeholders (you, your employer, your […]
How To Tell Whether Your Web Framework Is Shit
Does it ship with unit tests? If it doesn’t, it’s shit. Before basing the future of your business (or even your hobby) on a Web framework, see if you can find the tests. If you can’t, either move on, or get ready to take on someone else’s terrible, smelly code. Whoever wrote it doesn’t care […]