An Advice Column for Developers
By Ken North
Murphy's Law struck this month as server and network problems interrupted my progress in writing this column. If the problem had been in a production environment, there would be a hot-standby server that would take over and avoid interruptions in processing. However, the problem developed in an environment used only for developing and testing software. The test bed's backup server had older versions of some DBMSs and the newest server wasn't out of the carton.
In simple terms, I was dead in the water. Before completing the column, I'd need a working test bed with all of the right pieces. A series of corrective actions, such as removing and reinstalling software, didn't work. Eventually I replaced network cables and interface cards, formatted the system disk, and started installing software. My deadline was imminent and the process was consuming too much time, so I suspended that effort and started on a new column. As a result, this month I'm doing my Dr. Laura imitation with advice for those who are creating, or gearing up to create, Web applications.
Gearing Up: Start with Talent
These days the prevalent staffing model seems to be to hire for specialized skills and set up organizations in which people play narrow roles. The tendency is to pigeonhole workers, using employment ads that specify very precise qualifications. This narrow thinking produces some strange corporate behavior. I know of one instance in which a company sent rejection letters to people working with the current version of a DBMS, because the company wanted experience with a prior version.
