
Bug #1 in Ubuntu. This one may take a while to fix, but we’re working on it. (Thanks Matthieu)
Bug #2 must be the people. As Andrés Taylor reminds us, it’s always a people problem:
It basically means that technical problems are symptoms of people problems. And solving the techie problem is like taking pain killers for a brain tumor. Maybe it will give you a bit of relief in the short run, but you’re still far from well.
Backseat coders in particular. Coderific tells you how to spot them (as if you don’t already know), and how to deal with them.
What if we call them HR units? Abstracting doesn’t solve problems either, just moves them off to someone else. As Abhijit Nadgouda observes:
A lot of times, especially in discussions, it has been implicitly considered that abstraction reduces complexity. It does not! Complexity is like total amount of energy – constant. I do not remember where I had read this, but it conveys the message. Complexity cannot be reduced.
Because we’re helpless. Jacek Furmankiewicz evaluates the Survivors of the Java IDE Wars. The last page recommends which IDE to pick, depending on the type of project you’re working with. For example, if you’r developing for Swing, you’d want to use NetBeans. JSP/Struts, on the other hand …
Does anyone else have a problem with this helpless mentality, or is it just me?