Team $$$ Efficiency Through Modularity

Any veteran developer knows that integration and maintenence is where all the time and money goes, writing a simple module can be a few days work once the requirements, interfaces, and dependencies are set in stone. Modularity (OSGi) promises to eliminate much of that cost, by never fully integrating a module into the rest of the code base. Every module stands on it's own, lives in it's own classpath, and develops in it's own tested, versioned process. Read more »

When I'm doing my job, I'm getting things done.

When OSGi (or modularity in general) is doing it's job, it is preventing things from getting done. That's the job of OSGi, to prevent things from working except within very narrow contractual relationships.

Which is why OSGi deserves a slow and painful death. OK OK OK, that's only the way I feel when I get in these week long moods that stem from my inability to get all the metadata right, and I can't get my "modules" to run perfectly. Read more »

Dangerous Fred

Every big team has seen one or two of these guys. Dangerous Fred. Brilliant and stupid at the same time, breaks the wrong rules and still gets pretty amazing stuff done. But you don't want him touching your code.

How many meetings do I have to go to, to keep Fred off my project?

I think I've been Fred in decades past, at least once or twice. Sure have written a couple things I'm not so proud of, on the way to becoming a slightly better programmer. Read more »