Why Use Email

Coding horror has a nice entry on why email is counter-productive. It takes a different view as to why this is so. Rather than assume that it is the need to respond to emails that is the counter-productive part, the entry states that it is the constant need to see if anything new has arrived. The chances of any important information arriving via email are quite slim. You might get one or to useful emails per day. So what is the contents of the other emails that arrive daily that you don't care about? Maybe smaller pieces of information that might be of some significance in the future, but not today. And being interrupted with these irrelevant pieces of information is what is counter-productive.

So how to deal with these irrelevant pieces of information? There are always social networks. Social networks are feature reach and are certainly more than common these days. But I find that even moving these smaller pieces of seemingly irrelevant data to social networks as the delivery medium does not solve the problem entirely. Sure, this would clean up your inbox and thus eliminate the need for you to constantly be checking it. But what about that nagging feeling that you are missing something on your social networks? They do suffer from the same productivity problems as email does. Something else that might be taken into account when considering social networks as a delivery medium for sending simple messages is the fact that they support many more features. These other bells and whistles can be even more distracting than email because email does one thing and one thing only.

Using a wiki for exchanging most types of information, both big and small pieces, often makes more sense. Larger, more static pieces of information can be created as wiki pages. Smaller pieces of information can be created as tickets in project management systems, most of which have wiki support. A threaded dialog can then be created on these tickets. The conversation is than public and persistent. It is also search ready. They key point here being that tickets and wiki pages for that matter, are not limited to a software development context. They are much more general purpose and do not require polling on the recipient's behalf.

Corporate Coding

In an interesting entry over at coding horror, we hear about the idea of "happy talk" and the general corporate stench that accompanies it. Happy talk is the type of corporate language employed that masks anything realistic that may actually going on. So why is this necessary? Obviously not everything that goes on at a company needs to be portrayed literally and it never is. The stakeholders need to be happy. Hence the term. If the company isn't placed in an overall "happy" light, all isn't well and people become upset. The news is, all is not well and never will be. Especially in software development, things just simply do not go as planned.

So what kind of effect does this "happy" corporate culture have on the software development effort of a given organization? Does the this bogus lingo spill over to the software development culture? Not always, at least not on the same scale. But sometimes it does.

So take some developer working in a large company for instance. This developer is in change of developing and maintaining some component in a complex system. Any developer is going to experience the stresses involved with deadlines. The stress arises because they need to make compromises that lead to not so high quality code, that is potentially buggy. But if he knows this component looks good on the outside and works "well enough", no harm done right? He'll just continue collaborating with the other developers as if all is well. This in itself would not be very damaging but what if scenarios like this are continually repeated?

It would be nice if all environments were like some smaller shops and developers could fearlessly admit to flawed code. The company in turn would in turn say to the concerned parties something close to what is actually happening. Doing otherwise sets the stage for upset customers down the road when things really go wrong.