In the 1980s, a decade in which it was impossible to tell the actors from the politicians, it was fitting that the Macintosh gave anyone with a little cash the ability to produce absolutely gorgeous documents with absolutely no content.
Now rapid software-development tools bring the same potential to developers. If you are quite reasonably looking to such tools to reduce your software backlogs, be careful: It’s as easy to abuse them as it is to use them well.
We’ve seen such abuses up close, and they’re scary. Here are a few of the symptoms. If you spot them in your developers, take action quickly.
All interface, no content. You may have seen this one before. The tool lends itself to creating graphical interfaces, so that’s what the developer does first. The interface looks great, but none of the underlying code is present.