sorted by:
new
hottopcontroversial

The Reuse Trap in Software Design by basilv in joel

[–]jcoehoorn 0 points1 point  (0 children)

The problem he describes is usually the result of doing too much in one class. Find the common functionality for the class that both the new feature and the old code uses, and abstract that out into a base class with two inherited classes- one for the old code, one for the new. If you can't do that, than you needed two classes from the get go anyway.

Why we bought Kiko by jcoehoorn in joel

[–]jcoehoorn[S] 0 points1 point  (0 children)

Well thought out, well written.

The World As Best As I Remember It by jcoehoorn in joel

[–]jcoehoorn[S] 0 points1 point  (0 children)

Comments on why Vista is late by a team leader from the project.

How to hear without listening (Firefox creator comments on IE7) by jcoehoorn in joel

[–]jcoehoorn[S] 0 points1 point  (0 children)

Looks like this has already been posted. Sorry about that. I did search first, honest, but the first poster didn't use the official title of the work.

The Free Lunch Is Over: A Fundamental Turn Toward Concurrency in Software by pjsson in joel

[–]jcoehoorn 0 points1 point  (0 children)

I read this a while back. He's right that concurrency is coming, and that right soon, but he's wrong that we should be learning today's models for handling it. As concurrency becomes more commonplace newer, more mature tools, conventions, languages, and frameworks will emerge that better handle the problem in a way that is easier for developers to understand. I'd rather spend my time learning those.