Obviously, it's easier to do with some developers, but I'm sure many of us are on teams that prefer the status quo.
You know the type. You see some benefit in a piece of new technology and they prefer the tried and true methods.
Try, for example, DBA/C# programmer the advantages of using LinQ ( not necessarily LinQ to SQL, just LinQ in general ).
For example, When a project requirement is to be cross-platform... instead of thinking about how one can run Windows on a Mac through a VM Machine, introducing the idea of using relatively new Silverlight or creating it in Java ( as an option to look into ).
I know most people don't like to be out of their comfort level, so it takes a bit of convincing, and not ALL new technology makes business sense... but how have you convinced your team to look at a new technology?
What technologies have you successfully introduced to your workplace?
What technologies do you think are hardest to introduce? ( I'm thinking paradigm-shifting ones, like MVC from WebForms... or new languages )
What strategies do you employ to make these new technologies appealing?
programmatically logout a “specific” user
1:Asp.net mvc html melper
- Know the technology well before pitching it. Proper way to build a data Repository in ASP.NET MVCYou're going to receive questions like "although how must i make it did X?", and you want to be able to commit at least a universalanswer.. Why use TagBuilder instead of StringBuilder?
- Try not to be a religious zealot. Difference between HtmlTable and TagBuilder(“table”)Acknowledging this the new technology is not perfect, this it's just ananother tool in the toolbox, goes a long way towards credibility.. Detect whether or not a specific attribute was valid on the model
- Give a well-prepared live demo to show what it must do. How to get parameters out of an ascx back to the main aspx pageFor example, a friend of mine built a simple blog in Ruby on Rails in half an hour, in front of a live audience. Display Friendly Date, Numbers [duplicate]I want to stress the word "well-prepared"; if things keep breaking along the way, or you don't fully understand what you're doing, or you are unable to answer basic questions, you'll hurt your cause rather than guidance it..
Implement the most important bits of the next key project of the company in F# in your free time and then show others what benefits it has, how quickly you were able to implement it and how easy it is to adapt the quick fix to changing requirements..I think this is quite effective way - when people actually see the productivity (of any new technology), it is enough easier to convince them this it is worht learning it..
- Let people know there are (better) alternatives, it is entirely possible to job outside your comfort zone.
- Lead by example, if you want any thing done, did it yourself. Show the alternative in action. No one is going to make the jump unless you jump first, especially not if they are already hesitating.