|
Fire them all and start interviews on Monday?
|
|
|
|
|
I have a team of 5 - and I can hardly afford to restart the entire division and submit them to the Onboarding rigmarole!
Kind Regards,
- Will
william@enziq.com
www.enziq.com
|
|
|
|
|
It's about the only way you can be sure to get a team of five fully up to speed with a "new technology" in two weeks. It's way too late to organise a course; there are books and tutorials called "learn MVC in 15 days" (generally with numerous exclamation marks in the title) but my experience with such books in other fields are that you can get the basics, but nowhere near enough to be fully competent. Heck, at the end of one you don't generally even have a clue what you don't know - which is worse than not knowing what you should know (if you see what I mean).
Good luck - but I think it is an unrealistic aim, and you are going to get burnt badly on this one!
|
|
|
|
|
Go Agile, it will help solve any problem you may have, lack of time, insufficient funding, or support from The Client (Please dont forget to "Stand up" in the meetings)
dev
|
|
|
|
|
Boy, have you drunk the Kool-Aid™.
Software Zen: delete this;
|
|
|
|
|
It's Carlsberg this weekend
dev
|
|
|
|
|
|
|
Good luck! Pluralsight[^] could get a start on the learning curve.
There are tutorials on asp.net[^].
Wow tough task.
Hope You get up to speed.
David
|
|
|
|
|
Thanks I'll try - 10 days of free training seems good, will try to get some funding for the full package.
Also as someone suggested Agile sounds good, will attempt to convince my team about that too.
Kind Regards,
- Will
william@enziq.com
www.enziq.com
|
|
|
|
|
William Emmanual wrote: Also as someone suggested Agile sounds good
I could be wrong, but I think he was joking.
Again good luck.
David
|
|
|
|
|
William Emmanual wrote: Also as someone suggested Agile
Since you are new here, that was a joke.
Many people here often joke about stuff without using joke icon / smiley, it's their lame effort to attempt a dry british humor, which confuses rest of the 'normal' people. 
|
|
|
|
|
William Emmanual wrote: I have been asked to upgrade my entire team to "MVC ready" in 15 days!
Go back to the person who made this request and explain why that is not realistic.
Veni, vidi, abiit domum
|
|
|
|
|
Actually, I would go back to the requestor and challenge their assumption. Why 15? Why not 16 or 30 or 1?
Once it's been established that 15 is a completely arbitrary, totally pulled-out-of-someone's-ass number, then start talking about what's realistic.
I don't think OP said in what environment he's currently working. If it's something like Java, then maybe it's not too bad; you know OO concepts, are used to working with an IDE. Moving from Eclipse or whatever to VS won't be totally foreign.
Of course, moving the existing software itself is a big job.
However, if OP is doing something like COBOL or C, then it's a much, much, larger challenge. You have to start with a lower-level, learning the OO concepts and such.
|
|
|
|
|
Ok I'll start MVC means "Move Very Cautiously" that's all I got.
|
|
|
|
|
I don't think this is achievable unless they had had strong training before !
|
|
|
|
|
Do a quick meeting with your team, see if everyone is willing to learn the new concept. Once everyone agrees, I am sure your team could learn the concept of MVC in few days, and after that they should work on a very small project using MVC (it is very important, not just jump in after only reading and watching stuff, you need to try it out).
And after 15 Days, check where everyone stands and then, you all can just jump in with the new Project that your Client/Boss wants with extra days of buffer in the timeline. It is lot of work, but it's possible.
And if you think that after 15 days of trying, the whole thing is not working, just say 'no' with facts and reasons. People respect when you say 'no' with proper justification.
IMHO: for learning, read a book. It's OK if you don't read the whole book and only first few chapters. But before you start watching videos, you should read a book. You should learn the basic concepts thoroughly and only a book can teach you in a detail.
Good luck. 
|
|
|
|
|
good advice, thx for posting
|
|
|
|
|
Rutvik Dave wrote: for learning, read a book. It's OK if you don't read the whole book and only first few chapters. But before you start watching videos, you should read a book. You should learn the basic concepts thoroughly and only a book can teach you in a detail.
I find the combination of reading and watching to be better than either alone. I somehow seem to pick up different things from videos than I do from reading (and vice-versa).
Kevin
|
|
|
|
|
I agree, I also combine book, video, online articles, even Q/A on the topic that I want to learn.
Videos are like attending a classroom in the school, but to get a complete picture you still need a text-book.
|
|
|
|
|
Thanks a bunch, have been putting my peeps through the rigor. Reading online as and when we encounter problems. Asp.net makes it as difficult as possible to learn simple things, but yea we have been getting along.
Learning all the way...
|
|
|
|
|
You could give each team member an area to specialise in once they've covered a certain amount of basics. Then have them give a presentation each - on learning resources as well as how-to's...
|
|
|
|
|
Rutvik Dave wrote:
And if you think that after 15 days of trying, the whole thing is not working, just say 'no' with facts and reasons. People respect when you say 'no' with proper justification.
In my opinion the best way to go is to warn your boss that it is not possible, explaining the reasons, the possible outcomes and some alternative solutions.
Good bosses know that after getting a 'no' for an answer, comes a "so what do we do?" question.
|
|
|
|
|
You are right, but I always want to try first before saying 'no'. That way I will have strong reasons on why I failed. He has 15 days, why not give it a try.
|
|
|
|
|
I jumped in my first MVC 4 project without any special preparations.
My colleague was already a bit familiar with the framework and he started to work on the project alone, but due to circumstances he couldn't make the deadline so I was called in to help out where I could and finish. He explained the basics and I also found some tutorials online.
Both of us made some mistakes, most common mistake was not following naming conventions (which is btw really important if you want to take full advantage of the framework).
At the end it turned out okay. It wasn't a frustrating first experience and it didn't take long before it felt right. Also, to jump in an application that was already partly finished helped a lot because you have some examples from which you can build on.
.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
