Rob Janssen (RobIII)

Naming in OOP

To be honest it's not Computer Science specific issue, but common problem for whole science. History of science is composed of discoveries and evolution of definitions. Every math theorem is based on some definitions - I would call it “theorem dictionary”.

TDD myths: the problems

Code coverage seems to be a bad indicator for the quality of the tests. Take the following code as an example: Baby steps in TDD could lead you to this implementation. It has 100% code coverage and all tests are green. But the implementation isn’t finished at all.

Hacking the tag in 100 characters

Brian’s Stupid Feed Tricks

At NewsGator and Sepia Labs I worked with Brian Reischl, one of the server-side guys. Among other things, he worked on NewsGator’s RSS content service, which reads n million feeds once an hour. (I don’t know if I can say what n is. It surprised me when I heard it.

Chapter 16. Making It Real: Connections, Transactions, Performance, and More

There's no question that when you introduce layers into your application, performance will be impacted. Using ADO.

The Open-Closed Principle, in review

I've been to a few talks on SOLID before. Most of the principles seem pretty reasonable to me – but I've never "got" the open-closed principle (OCP from here on).

Five "laws" of programming paradigms

Now that we are close to releasing Mozart 2 (a complete redesign of the Mozart system), I have been thinking about how best to summarize the lessons we learned about programming paradigms in CTM. Here are five "laws" that summarize these lessons:

The fallacy of “the right tool”

Let me start this blog post with a disclaimer: I’m really convinced of the value of multilingual programming and also think that applying the “right tool for the job” is a good thing. But there is a fallacy around this concept in programming that i want to point out here.

Full Throttle with Brad Wilson: TDD

In this video Brad Wilson (co-creator of XUnit test suite) is put to the test: Build a Shopping Cart for Tekpub. And do it LIVE using TDD. And Brad did just that - very well.

Thread Abort and Critical Regions (in .Net)

I don’t need to see the source code of an API to code against. In fact, I actively discourage against depending (even psychologically) on the inner details of an implementation. The contract should be sufficient.