Jeanne Boyarsky wrote:Vasmi,
A few pieces of advice:
1) Get to know the team members. What are their skills? What do they like to do? What problems are they struggling with.
2) Carve up the work into smaller pieces. You should be involved in the design. And how to carve up the tasks into manageable pieces. This also lets you know early when something "doesn't work" so you can help/intervene earlier.
3) If you have time, see if you can pair program with each of them. Even if it is just an hour or two a week each, you can help grow their skills.
4) Don't assign yourself any coding tasks. You'll be plenty involved pairing, mentoring, etc.
And yes, Selenium is a great tool.
K. Tsang wrote:Further to what Jeanne said
1) When you do assign tasks to your team, such tasks should be the use-cases or functions for the site, not different phase of SDLC like testing. That way the person can develop it, test it, refine it... He owns that function. Yet you as the leader is responsible if anything goes awry.
2) Prepare to work on documentation (tech spec, design spec, etc)
3) Ask the team what tools they have used. Research on such tools then decide if they can be used in your project. Relearning/using something that is familiar in the past tends to be quicker than learning something brand new.
vamsi naki wrote:2) For making up the design ,is there any good article to read.I can google it but i have to do lot of work alone as of now,and any pointers will help to reduce the time .
vamsi naki wrote:3)It sounds like a very good idea,i am also thinking of giving them small tasks every week ,like first encrypting and decrypting a password saving it to Database,then telling that Hashing with Salt is better ,guide them through the process ,so that they will develop their skills.Tell them about SQL injection attacks.Is that fine?
vamsi naki wrote:4)As far as coding is concerned till now i did all the majority of coding but from off shore,so i dont know their skills we didnt have an introduction yet until i meet them in person,but is it ok to ask them to code dirctly,i want to train them with the basics ,give them assignments to complete .A sample project to finish then only ask them to code .
vamsi naki wrote:I need some suggestions on training the freshers,i am thinking of training them in Java ,then train them in Blue J,and ask them to build a sample application in Blue J so OOPS concept is understood fully.
Jeanne Boyarsky wrote:
I'm not clear on where you and they are. If you can't pair in person, can you pair remotely? Being in charge of a bunch of new programmers you can't communicate with synchronously isn't likely to end well.
Jeanne Boyarsky wrote:
Wait. They don't know Java yet? I thought they were inexperienced and not lacking in basic knowledge. Freshers usually wen to university and come in knowing some programming language. If they don't even know Java, you need to talk to your boss. Expecting you to teach them and get a project done is a lot to ask!
Paul Clapham wrote:Here's another issue which I don't know if you meant to ask about: For quite a while your team will not be producing anything useful for the company you work for. So you're going to have to work with your bosses to make sure they understand that and are OK with it. It may be that they thought that they could hire a group of beginners and expect them to be productive immediately, and if so then you need to help them to understand why that isn't the case.
You showed up just in time for the waffles! And this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton