A whole host of agile technologies have become mainstream over the past few years. These include refactoring, unit test, test driven development, and even Scrum. However pair programming is stuck in the mud.
One problem is that pair programming is expensive. On the surface, it takes twice as much to do pair programming. It is also not liked much by developers. It might be one of the agile methods that never pan out.
However it is the end results that matter. You want to know immediately when the build breaks. That might mean you have unit tests that automatically get applied. Or a build job checks for errors and emails the right people. We don't have that at our work. We used to. But the build scripts got rewritten, and are not as good any more.
Netstat - I have been researching info on a utility called netstat. There is surprisingly not much said about it, other than the multiple options that it support. N...