I tried to post a comment on Nick’s blog, but for some reason I never got the email for verification of my address so I thought I would respond here.
I find it very interesting that a former EMBT employee still with close ties, would write such a post. I understand how he drew some of his conclusions, but I think he is mistaken and I hope EMBT does not share the same views. Understanding the marketplace is very different from software development.
First of all, code quality is more about developer skill, and the processes employed during development and QA. The earlier defects are found the cheaper and easier it is to fix them. The number and age of unresolved bug reports does not speak well to EMBT’s (and their predecessors) concern for code quality. However, the primary driver, as with all things produced by a company, are the decisions made by management. While no code is perfect, if you accept that it is not possible to produce bug free software then you have lost the incentive to try.
Having “volunteers” go through QC reports says that a company isn’t even willing to pay their staff to properly evaluate bug reports. Having a broken voting system and web QC, as well as an antiquated Windows client that not being maintained speaks volumes about what is important to a company. Admittedly, the bug tracking systems have finally changed. It doesn’t seem to have affected the number of fixes for long outstanding issues though. As people we spend our time on what we believe is most important. Same thing for companies.
Allowing half baked (incomplete) or non-working visible things like the panel at the bottom of the object inspector that Marco wrote an add in to remove, Error Insight, and the Refactorings remain in the product for years without fixing them is not only stupid IMHO, but a software development nightmare. Web companies are making money on minimalist applications that satisfies a small need, but does it extremely well. EMBT seems to prefer the old school thinking of a humongous application that does everything under the sun, but does some things very poorly, and taints everything else with the same code smell. They don’t even seem to be willing to consider using the plug in system to provide ‘a la carte’ choices to their customers, or drop existing functionality that is not required to limit their technical debt going forward. What other company has someone external to the company provide bug fixes for their IDE that apparently never get incorporated into the product because Andreas is still churning out IDEFix pack!
Only in an emerging marketplace can you continue to sell flawed products that look good on the surface, but don’t work as well as they should, to be used daily for someone to make their living. Development markets are not emerging ones, nor are they without stiff competition.
Developers are smart people. EMBT is fooling no one with their choices when it comes to resource allocation. Hire cheaper developers around the world to cut costs, focus on emerging markets where quick profits can be made, and increase the cost of the tools by coupling the mobile pack with the core dev tools and charging for each, effectively double dipping, while raising the cost of the product across the board and providing diminishing product quality. Typical of a company acquired to provide profits to it’s purchaser, and not for any ideological reason.
The definition of insanity is doing the same thing over and over expecting a different outcome. Developers will only continue to buy EMBT licenses or subscriptions as long as they have to in order to support their products, or where their is some advantage (none come to mind right now) because they aren’t insane. EMBT on the other hand cannot continue indefinitely down this path, unless they want to drive away their user base, or intend on getting as much cash from their users until the bottom falls out, and they close the doors.
Delphi is no longer a bleeding edge tool, even in the mobile space. It has more competition than ever, and a major challenge with Microsoft/Xamarin/.NET Native and Apple competing in the market place. One of the reasons for it’s current success is the older user base supporting existing applications built when Delphi was bleeding edge, or trying to use their skills in the mobile space. That ride won’t last forever.
Perhaps I have digressed a little, but my point is that EMBT has shown it’s colours. They don’t care about code quality or their actions would speak more to it. Instead they want to add just one more feature into the box. Perhaps a subscription model would help a little, but it won’t result in more bugs fixes. We have been voting with our wallets for some time now, in QC, and on the forums and they are still not getting the message! As a customer I would have to be insane not to recognize their pattern, and refuse to pay for bug fixes (it’s a great money making machine if you can convince users to do so), and choose another toolset from a company that does care. If they did we would have seen bug bounties a long time ago…
At work we’re developing C# .NET replacements for our Delphi apps as we speak! Good luck to EMBT. XE4 with the infamous ‘Out of Memory issues’ will be the last release we buy…