July 7, 2006
My last post might have been a little to aggressive... but I have to say the reaction was fast and very positive. The information is now correct.
I might have overreacted, and maybe someone else has, too, but for sure this time the effect was immediate. The article has now been corrected, and goes into some details explaining the IDE-based compilation and the Code Insight advantages (with a nice comparative screen shot). The response from the author and the BDN team, was indeed much faster than I could expect. Kudos.
As for John Kaster invitation to get involved in helping BDN (as a writer and or reviewer), I'll certainly consider it. DevCo certainly needs helping hands more than critical voices!
posted by
marcocantu @ 11:52PM | 2 Comments
[0 Pending]
CF Disinformation Stopped, BDN Article Fixed (in Record Time)
DevCo( and previously Borland) DESPERATELY need
critical voices. Without them, they would have no
idea how badly they've screwed up and will continue
to wander down the wrong path.
Be critical of DevCo, LET them know when they screw
up, overcharge, destroy the help files. If they
don't hear about it, they will never ever fix it.
Borland refused to hear ANY discenting voice and the
hoards followed their lead. DevCo is much more
receptive at the moment, so for gods' sake, if you
care about the quality of Delphi, LET DEVCO HEAR YOUR
VOICE!!!
Then, if they listen, they will seek to improve their
standard by doing things like hiring people on for
documentation improvements.
They need the people to do the job right, they need
the critical voices to know what the right job is, so
stand up and be heard and counted.
And hey, if you have the skills to help and the
opportunity arises, and you can afford the risk, you
might just become a DevCo employee.
Comment by Xepol on July 8, 20:47
CF Disinformation Stopped, BDN Article Fixed (in Record Time)
Hi Marco,
When will we see your CF article you promised us a
few months ago?
Looking forward to it...
TDaniel
Comment by TDaniel on July 10, 13:29
There are currently 0 pending (unapproved) messages.