Menu
.NET 3.5, .NET 4.0, WPF, Silverlight, ASP.NET MVC - there's really a lot of new Microsoft technology released / on the horizon to try out these days. (The examples I gave is all Microsoft technology but this can apply to any language or platform). I am curious how this is handled in the company you work for. A few examples:
These are just examples to make my question clearer. To summarize, I'd like to know what this process looks likes, who is responsible, who makes the decisions. Does your company jump on the bandwagon, or is it reluctant to try new technologies? And are you comfortable with this situation?
At the company I work for, we still use .NET 2.0 (although we are now slowly switching to .NET 3.5), haven't seriously looked into ASP.NET MVC, haven't tried out WPF at all, etcetera. And, some find it pretty hard to convince people to do. Is it fair to expect otherwise?
543
Definition 1. A technological innovation is a new or improved product or process whose technological characteristics are significantly different from before.
Technology helps increase the efficiency of systems, products and services. It helps track and streamline processes, maintain data flow and manage contacts and employee records. In fact, this increased efficiency in operation helps reduce costs as well as enable the business to grow rapidly.
Technological innovation creates opportunities for entrepreneurs to found new organizations and establish competitive positions as incumbents' sources of advantage decay. Technological innovation also creates uncertainty and risk for incumbents because its outcomes can be only imperfectly anticipated.
Innovation is vital to your company's success in today's highly competitive business environment, especially as customers become more demanding and savvy. Entrepreneurs need an edge to survive and stand out. Innovation can provide that edge—boosting your productivity, growth and profitability.
At my company, we have an architecture group that determines which technologies are used. People are welcome to read up on alternative technologies and make suggestions, but at the end of the day, it's the architecture group that makes the decisions.
While this may seem restrictive, it does ensure that all of the development groups are using the same or similar technologies, and moving from one group to the next is fairly easy. As well, by having one group do all the research, you ensure that you don't waste time by having multiple groups duplicate the research effort.
114
Since I work in such a small company and am I typically either the only developer, or the lead developer in a very small group, I can usually convince my boss to use whatever I think would be the best for a given project/situation.
37
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
