Recap..

Well, it's been an eventful last couple of months, to say the least.  I've not commented here on recent events for several reasons.  First of all, I've been on vacation for the last week with the family (Disneyland and Disney's California Adventure).  Secondly, I wanted to see what the tone and reactions were to some of the latest news from Borland.  So far, I'm pleased with how the customers have been reacting.  So let's recap the latest news along with my various opinions...

Tod Nielsen - New Borland CEO.  So far so good.  He's a former MS exec and has walked in the shoes of many of us in the tools and database business.  Frankly, I feel his pedigree is the best since Phillipe Kahn.  That isn't a knock to any former CEOs (at least not all of them ;-), but merely an observation.  His tag line, “Go big, or go home.“

Borland Developer Conference - Smaller venue.  More focused on developers.  Good content.  Different “feel.”  Better in some ways, and not so much in others.  I really enjoyed participating in the opening keynote and doing the “What's new in Delphi“ talk.

Borland Developer Studio 2006 - Released to manufacturing.  It was nearly a month and a half later than the original schedule due to needing more time to hit our quality criterion.  Upper management, pushed hard for the orginal release date (as they should) but know that a quality focus would pay off in the long run.  Big, big change from previous releases.  Is it perfect in every way?  Probably not quite, but it really needed to be out there so we can better know where to focus our efforts for updates. 

C++Builder 2006 - The descision to release C++Builder as a preview and update that personality later was unprecidented.  The team was stoked by this descision.  By all rights, the C++Builder personality will get a significant number of much needed fixes before the update is released (which is real soon now).

Danny Thorpe - Sticky subject, for sure.  First of all, yes, Danny has left Borland and is now working for Google.  His reasons for leaving are personal, so I'll simply quote his comments made in the borland.public.delphi.non-technical newsgroup:

Members of the Delphi Community,
 
As you've no doubt read in other threads in this newsgroup, I have left
Borland to seek new opportunities at Google.

This was not a sudden action.  I have tried my best to ensure a smooth
transition for the Delphi team, starting with transition plan
discussions with Borland management more than nine months ago.

Delphi is built by a team, not by any individual. Far greater talent
than mine has come and gone from the team, and Delphi presses on.  More
importantly, far greater talent remains in the team, some of it as yet
untapped.

As you may know, my philosphy is that teams should be built to
anticipate, tolerate, and support the comings and goings of individuals
on the team. Everyone will eventually leave the team - either by
choice, or by pine box. To ignore this is childish.

I have full confidence in the Delphi team to continue to deliver the
right stuff to keep Delphi current, innovative, and competitive for
years to come. Though there have been some difficult spots between
myself and Borland corporate management, the internal changes in
attitude and messaging in recent months from Borland corporate toward
Delphi have turned my faith in Borland supporting Delphi back toward
the positive.   I'm sure that will only get better as Todd Neilsen
steps in as the new CEO.

I'm also pleased that in some small measure my departure is creating
opportunities for advancement within the Delphi team, and that Borland
management (Boz and Steve Todd) was very supportive of "redrawing the
map" under the guidance of Allen, Michael, Eli, and myself. Several
individuals on the team have been promoted in title and/or in pay as a
result of this change. Many of those have not seen promotion or pay
raises for as long as 5 years. Borland has also committed to opening up
several new positions in the Delphi group in Scotts Valley, which may
be filled with entry or mid level engineering talent. This alone is a
significant reversal of the "No new hires in Scotts Valley" edict
earlier this year by then-CEO Dale Fuller.

I was not snatched away from Borland, and I am not leaving Borland for
lack of money.  I sought out Google, and I'll be making at Google
exactly what I made at Borland, which is nicely comfortable but not
excessive.  There were other suitors (including the obvious one) but,
quite frankly, Google outmaneuvered them.

Could Borland have bought me back?  No, because I didn't leave for
money.  Why, then?  Opportunity.  I'm going to Google to pursue ideas
and opportunities that are simply beyond Borland.  I love Delphi, I
know it inside out, but there's a lot more in me than just Delphi.
 
After 15 exciting years doing a wide variety of things at Borland, it's
time for me to do something /completely/ different.

This is not goodbye.  This is just changing channels.

-Danny Thorpe
Engineer, Google.

Let me comment by first saying that Danny's departure will certainly inccur some pain, however we've always survived the departure of other high-level team members.  What this does is open up the team to allow some of the existing talent to advance and get the opportunity to put their unique mark on the product.  It also opens up an avenue to bring in some new budding talent.  As a matter of fact, we've just hired a new, young, hot-shot engineer in an entry-level position who was with us as an intern for a year or so.  (the scary thing is that this guy was still in middle-school when Delphi was released!)  Notice I said, “team.”  That is a key point.  Delphi was, and always will be, a team effort.  Danny himself states, “Delphi was built with a team.”

On a personal note, Danny's mark will always be on the Delphi product, as will be Chuck Jazdzewski's and Anders Hejlsberg's.  I can honestly say that Delphi wouldn't be what it is today without the vision and guidance of those individuals.  I also count them all as very key to my own personal success for it is was with thier mentoring and guidance that I've been able to take over the reigns for Delphi.

So Delphi is moving forward on into the next release, codenamed Highlander.  We're still on the same roadmap.  The only things that may change is the timing.  Internally, we're investigating various agile development methodologies in order to enhance our current processes.  What is interesting about this is that it is being endorsed and supported by the exec management team.