On mySimon: Holiday Gifts For Him
BNET Business Network:
BNET
TechRepublic
ZDNet
TalkBack 1 of 10:
Next »
Just Ignorant or more MS-Sponsored Bull?
Articles like these always the ignorance line so closely that I cannot really tell if
they're genuine ignorance or influenced by parties with vested interest.
However, Robert De-Niro gave the best advice for some of these ZDNet guys in
the movie "Casino":

Listen, if you didn't know you're bein' scammed, you're too $*#%^ dumb to
keep this job. If you did know, you were in on it. Either way, you're out. Get out!
Go on.


So to answer these questions:
Is developing on an open source platform really different from developing on
a closed source platform?

Yes, actually. Developing open source usually means developing in a portable
manner so that the code may be used on many platforms - both open
and closed source. It also means properly adhering to many open
standards and actually following established software and operating system
design principles which proprietary ones usually neglect or implement poorly.
It usually also means liasing with an open source community who cannot
be "ordered" to do anything. Leadership, negotiation, and communication
skills are thoroughly tested on a regular basis by intelligent individuals, not
pointy-haired bosses. Finally, if you're writing open code you also have to
create high-quality, well commented, properly abstracted with lots of
forethought - there is no "close enough, nobody will know I took this shortcut"
option. Open-source communities are ruthlessly self-selective based on
merit. If you're a regular contributor or lead developer there's no way you got
there by cheating to obtain a diploma/certification or because your uncle is
president of this-that-or-the-other! Open Source developers are "the real deal"
proven through trial-by-fire and their work history (including conversations, not
just code) is publicly available for any employer to review.

Are the skills needed to develop for one any different from those needed to
develop for the other?

I think my response above covered this. Developers for proprietary platforms
have different skills including negotiatiation of office politics and meeting tight
deadlines. They also learn to compromise with non-technical agendas and
improvise their code for platforms which don't to provided specifications. With
closed source development there's even the option of learning to stuff
your resume and provide false references ;- )
Posted by: smartguy2@...   Posted on: 02/29/08 You are currently: a Guest | Members login | Terms of Use

Alert moderator to an offensive message

Subscribe to this discussion via Email or RSS

Just Ignorant or more MS-Sponsored Bull?  smartguy2@... | 02/29/08
Ignoramus...  qquidd@... | 02/29/08
Those skills can be learned  DanaBlankenhorn ZDNet Moderator | 02/29/08
Besides...  John L. Ries | 02/29/08
Yup, the "outta the door scenario"  fr0thy | 03/01/08
Dana, in a closed source proprietory scenario ...  fr0thy | 03/01/08
from all the responses you see  code_Warrior | 02/29/08
I dunno about that one  John L. Ries | 02/29/08
The evidence speaks for itself ...  fr0thy | 03/01/08
Had no idea...  John L. Ries | 02/29/08

What do you think?

SponsoredWhite Papers, Webcasts, and Downloads

SmartPlanet

Click Here