Who decides what technology to use at your work place
-
I asked a similar question a while ago :) Anyway, in my case the correct answer would be: "history". The technology was picked when the development started, in 1997. Sure, we use new API calls and have switched to Unicode-only builds, but questions such as "WPF vs. Silverlight" make absolutelly no sense in this environment.
modified on Wednesday, May 27, 2009 5:09 PM
-
I have the fortune to test, evaluate and then pick the right technology for the right job for my product. But it may not be the case for many. (Obviously, I am talking about new projects here). So who dictates what technology need to be used for your products (technology I mean more in line with frameworks rather than generic areas like web/desktop): 1. Someone who have little or no programming experience. 2. Someone who has programming experience but no longer writes code. 3. Someone who writes code actively. 4. The programming team as a whole. 5. A rigorous method that involves test/prototype of different technologies. 6. No idea who does? or don't care. Of course "or" the above options with: 1. The person who picks the technology is supposed to be actively involved with the project.
1. My Boss, the general manager. When I first started one of my jobs was to start planning a website for the company. So he runs off to a meeting for a week and comes back to announce that he's hired someone to build the initial website for us. In PHP, on a Linux server. Two subjects I know nothing about and have no interest in learning. When we needed a new server, I recommended (against my better judgement) Win2003 Small Business Server as the best value for our buck. He hired an outside computer guy who recommended the same thing, and had him install it. But he instructed the guy not to install SQL Server, Exchange Server, IIS, or Sharepoint Server. Now he wonders why he can't share his Outlook calendar. Duh... When I installed a SCADA system to monitor and control our substations he directed me not to connect it to our internal network, so that it will be secure. Now he can't understand why he has to walk into the center office and look at the tiny laptop display (which is the only supervisory node we have) to see what's going on in our system. I tried to explain that our SonicWall routers (excellent products, by the way, though hard to configure and expensive) would do a fine job of keeping bad guys out, but he wasn't hearing any of that stuff. He reads magazines and knows all about this... :sigh:
"A Journey of a Thousand Rest Stops Begins with a Single Movement"
-
I have the fortune to test, evaluate and then pick the right technology for the right job for my product. But it may not be the case for many. (Obviously, I am talking about new projects here). So who dictates what technology need to be used for your products (technology I mean more in line with frameworks rather than generic areas like web/desktop): 1. Someone who have little or no programming experience. 2. Someone who has programming experience but no longer writes code. 3. Someone who writes code actively. 4. The programming team as a whole. 5. A rigorous method that involves test/prototype of different technologies. 6. No idea who does? or don't care. Of course "or" the above options with: 1. The person who picks the technology is supposed to be actively involved with the project.
I decide it here along with my team manager. He is highly technical and still actively writes code every day, even after his 10+ years in the industry. I guess I'm lucky that way. :)
It is a crappy thing, but it's life -^ Carlo Pallini
-
I have the fortune to test, evaluate and then pick the right technology for the right job for my product. But it may not be the case for many. (Obviously, I am talking about new projects here). So who dictates what technology need to be used for your products (technology I mean more in line with frameworks rather than generic areas like web/desktop): 1. Someone who have little or no programming experience. 2. Someone who has programming experience but no longer writes code. 3. Someone who writes code actively. 4. The programming team as a whole. 5. A rigorous method that involves test/prototype of different technologies. 6. No idea who does? or don't care. Of course "or" the above options with: 1. The person who picks the technology is supposed to be actively involved with the project.
For my projects, I decide; for other IT projects, I influence. ;)
-
For my projects, I decide; for other IT projects, I influence. ;)
Generally I do - but the director pushes me towards software sometimes (a good thing).
-
I have the fortune to test, evaluate and then pick the right technology for the right job for my product. But it may not be the case for many. (Obviously, I am talking about new projects here). So who dictates what technology need to be used for your products (technology I mean more in line with frameworks rather than generic areas like web/desktop): 1. Someone who have little or no programming experience. 2. Someone who has programming experience but no longer writes code. 3. Someone who writes code actively. 4. The programming team as a whole. 5. A rigorous method that involves test/prototype of different technologies. 6. No idea who does? or don't care. Of course "or" the above options with: 1. The person who picks the technology is supposed to be actively involved with the project.
I'm a small fry who caters for the requirements of large companies, what they use I use as it's just simply the path of least resistance. Their IT decisions are based on what the Microsoft salespeople tell the people in charge. Could be worse.
-
I have the fortune to test, evaluate and then pick the right technology for the right job for my product. But it may not be the case for many. (Obviously, I am talking about new projects here). So who dictates what technology need to be used for your products (technology I mean more in line with frameworks rather than generic areas like web/desktop): 1. Someone who have little or no programming experience. 2. Someone who has programming experience but no longer writes code. 3. Someone who writes code actively. 4. The programming team as a whole. 5. A rigorous method that involves test/prototype of different technologies. 6. No idea who does? or don't care. Of course "or" the above options with: 1. The person who picks the technology is supposed to be actively involved with the project.
Client's sometimes ask for an opinion, but more often than not it's history that dictates the outcome. At home, ostensibly it's me, but the comptroller of discretionary spending usually exercises her veto.
Multi famam, conscientiam pauci verentur.(Pliny)
-
I have the fortune to test, evaluate and then pick the right technology for the right job for my product. But it may not be the case for many. (Obviously, I am talking about new projects here). So who dictates what technology need to be used for your products (technology I mean more in line with frameworks rather than generic areas like web/desktop): 1. Someone who have little or no programming experience. 2. Someone who has programming experience but no longer writes code. 3. Someone who writes code actively. 4. The programming team as a whole. 5. A rigorous method that involves test/prototype of different technologies. 6. No idea who does? or don't care. Of course "or" the above options with: 1. The person who picks the technology is supposed to be actively involved with the project.
The salesman who convinces the boss his stuff is best...or the salesman with the biggest "incentives" for buying.
Joe V My Blog on Testing Me, Myself, and I SGP Robotics team and FIRST Robotics
-
I have the fortune to test, evaluate and then pick the right technology for the right job for my product. But it may not be the case for many. (Obviously, I am talking about new projects here). So who dictates what technology need to be used for your products (technology I mean more in line with frameworks rather than generic areas like web/desktop): 1. Someone who have little or no programming experience. 2. Someone who has programming experience but no longer writes code. 3. Someone who writes code actively. 4. The programming team as a whole. 5. A rigorous method that involves test/prototype of different technologies. 6. No idea who does? or don't care. Of course "or" the above options with: 1. The person who picks the technology is supposed to be actively involved with the project.
First: The client Second: 4. Third: If the team doesn't agree with 4. then, goto 5. Also, if the client doesn't care or the decision is about a technical detail the client doesen't care, go to "Second". Fábio