CodeGear: A Year After the Borland Spinout

 
 
By Darryl K. Taft  |  Posted 2008-01-09 Email Print this article Print
 
 
 
 
 
 
 

CodeGear's CEO talks to eWEEK about the company's first year as a separate entity from parent Borland Software. 

Jim Douglas, CEO of CodeGear, says the tool maker is picking up steam. According to Douglas, the company is poised to capitalize on opportunities in the open-source and Web development spaces. Borland Software spun off its core developer tools business into the separate entity known as CodeGear in November 2006. Douglas, who took over as CEO last April, spoke with eWEEK Senior Editor Darryl K. Taft about CodeGear's products, strategy and plans for the future.  

How is CodeGear doing one year after it became an independent business unit from Borland?

Life is good. CodeGear is profitable. We have more than 3.2 million users of our products in 29 countries, which puts us among the world's top tools providers-and the only one focused exclusively on tools. When CodeGear became a separate business entity from Borland, we had to spend a lot of time reassuring customers, partners and others that we were a viable, vibrant and profitable organization. Fortunately, the dust settled and the conversation moved from our business status back to what innovations we're bringing to market and have planned for the future. The good news is our development team was heads-down during this time frame, bringing innovative, new technologies to market. Over the past year we launched an amazing group of new products-JBuilder 2007 and JGear plug-ins based on Eclipse, Delphi for PHP and Delphi for Win32, C++Builder 2007, and a new Ruby on Rails product called 3rdRail. And we have some pretty exciting things in store for 2008.

 

Is CodeGear still looking to be sold or to separate from Borland?

Borland's strategic intent is still to divest of the development tools business. However, we have not put a timeline on pursuing and/or completing a transaction. Per our prior discussions, CodeGear has been set up as an autonomous operating organization. This structure has enabled us to exclusively focus on bringing value to developers and optimizing the operation for long-term success. The feedback from our customer base on our renewed focus has been overwhelmingly supportive and positive.

 

How do Borland and CodeGear approach the market differently and will anything change in that regard in 2008?

CodeGear is 100 percent focused on the developer tools market, providing individual productivity tools for a wide spectrum of developers and developer teams. Borland is 100 percent focused on [ALM] application lifecycle management, providing enterprise applications that make software delivery a more managed, efficient business process. Although we have many customers and prospects in common, we target different parts of customer organizations and thus have different go-to-market strategies. Operationally, CodeGear has a separate management team, R&D, [and] sales and marketing organization. You will see both CodeGear and Borland continue to independently fine-tune and optimize our operations. However, CodeGear will continue to operate as a fully autonomous business.

 

David Intersimone, your vice president of developer relations, recently suggested a new way of looking at the software development paradigm-capturing developer 'intent' via application factories. He called it 'application-driven development,' where the structure, evolution and logic behind developing an application is part of the application. And both those components and the application itself can be shared with other developers as reusable software assets. What's your view of this?

Application factories are going to be game-changing. Think back to the advent of the original IDEs (integrated development environments), which, by the way, we invented. They enabled a profound improvement in productivity. Some years later, IDEs were deemed commodities and productivity improvement was thought to have peaked. Along came component-based design and visualization.

Once again, a meaningful improvement in productivity was enabled by new innovations. The methodology behind application factories represents the next wave. A common theme you typically observe with innovations in design that lead to major productivity improvement, whether it be software, electrical or mechanical design, is a practical leap in abstraction. This approach will enable such a practical leap in design abstraction, enabling developers to think at the application level first. In addition, this approach will help address one of the biggest issues facing companies today: efficient knowledge transfer.

Companies struggle to harness intellectual capital due to changing project teams, organizational churn, turnover, and the necessity for distributed development. By capturing logic and intent in the application, companies will be able make significant improvements [to] how they leverage knowledge across their organizations. The result will be the creation of application factories, repositories of truly reusable software assets than can effectively be leveraged across an organization. You'll see us apply this concept of application factories in products we will be launching in 2008.



 
 
 
 
Darryl K. Taft covers the development tools and developer-related issues beat from his office in Baltimore. He has more than 10 years of experience in the business and is always looking for the next scoop. Taft is a member of the Association for Computing Machinery (ACM) and was named 'one of the most active middleware reporters in the world' by The Middleware Co. He also has his own card in the 'Who's Who in Enterprise Java' deck.
 
 
 
 
 
 
 

Submit a Comment

Loading Comments...
 
Manage your Newsletters: Login   Register My Newsletters























 
 
 
 
 
 
 
 
 
 
 
Rocket Fuel