From: albartell
This topic is interesting because it really demands another knowledge set
in today's software developer - the ability to understand long-term
effects of adopting new software on different platforms and in different
languages.
I hope you're not implying that this is a NEW knowledge set, Aaron. We've
been doing this sort of thing for thirty years now. Originally it was with
dedicated microprocessor-based devices (things like Xerox printers or
standalone communications boxes), and then in the early 80s it was with PCs.
It's not easy; it requires relying on other people and admitting that your
particular expertise isn't the best one for every problem, so in today's
rather territorial world of programming, it doesn't go over very well. But
if you have a true team of programmers working together, you can handle
program distribution just as well as any other part of the puzzle.
What really doesn't work in this environment is the "Code Cowboy" mentality.
Digital Divas tend to screw up multi-platform architectures because they
fight everything they don't know, often because they want to be known as the
experts in everything. These same people can't explain to others why they
do things because often they themselves don't really know, it's just "the
way they do things." And you should bow to their superior knowledge.
The only way a multi-platform architecture works is when you have really
bright people assigned to different areas and one strong-willed SOB of a
manager whose job is to understand enough of all the technologies to make
the hard calls and have everyone hate him.
Maybe that's why I was so good at it <grin>.
Joe
midrange.com
