Unfortunately many companies let themselves be led into a complex mess by so-called "rockstar" developers who usually are just people who have mastered a partic

Unfortunately many companies let themselves be led into a complex mess by so-called "rockstar" developers who usually are just people who have mastered a particular language and its libraries, and perhaps one common framework in that language. This allows them to churn out masses of poorly written code and bamboozle management into thinking that they are 10X productive. They are like the sales guy who makes some big sales, collects his commission checks, and then leaves the company before everyone finds out that the product was not suitable for that customer, and the contracts are cancelled. Then, working for another company, he does the same thing again. Some companies now withold part of their commission payments for a period of time to be sure that the product was sold correctly, that it gets delivered to the customer properly, and that the customer begins using it and gaining some value from the product. However, in software, we let rockstars create a big mess, and then over the next few years we spend many man-years of effort into maintaining that software, fixing bugs, attempting to shoehorn new features into a system that is rigid, inflexible and even fragile. This is what rockstars bring us, momentary euphoria until the concert is over and we are stuck in a traffic jam trying to get home. This is not scalable and not sustainable. If you see a job ad that asks for rockstars, run away. Their management are fools and they are busing building a complex mess that will destroy their business.