This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
November 13, 2008 11:52pm
Subscribe [5]#1 / Nov 13, 2008 11:52pm
#2 / Nov 14, 2008 12:09am
Oh boy, here we go again. I can see where this thread is headed.
Mike McDerment makes some good points. I can see the logic behind keep things being closed doors. But I also think there is a healthy middle ground in all of this. A way to keep curiosity alive and satiated at the same time.
#3 / Nov 14, 2008 1:33am
I think this applies… But ONLY to software. The eternal term ‘vaporware’ is a large part of it. Not only that, most software authors don’t really design a true roadmap. Not to say they’re shooting from the hip, but it’s a much more flexible line of process than say a brick and mortar development. Software timelines seem to be more fluid, and that hurts a solid road map. The other option is to lock yourself in and in the best interest of following that map you aren’t able to include new items as they hit the market. New features, technologies, etc. Unless you want to stay a year behind the technology, like most large coporations do on say, computer hardware and infrastructure, you aren’t able to maintain a firm line. Again, it’s too fluid. There are too many ‘new’ things coming out too fast and to curb your staff and yourself you aren’t able to entertain new ideas or approaches.
I also think the ‘keep your competition guessing’ statement is a cop-out.