I found myself in an interesting coaching spot - I am going to teach Alt.NET to a programming infant. I’m going to create the first Alt.NET baby.
Real life sometime brings you to strange situations. I lead a development team which is building a web application and we recruited a new member a couple of weeks ago. I’ll refer to him as “the baby”, since he never wrote a single line of code.
Why is he on board, you ask? Well, he’s a fresh computer science student and knows his way around the presentation side of websites (good knowledge of HTML, CSS, Javascript and good ol’ web black magic) so this seemed like a good trade-off for both sides - the baby will join the team and help us out with his mighty presentation powers and in exchange will be part of a real project for the first time and will get on-job-training.
This is an interesting spot. Computer science has brought his knowledge to a certain level so far (basic C) and I need to catch him up with:
- Object Oriented Programming,
- What design is,
- Separation of Concerns,
- Liskov Substitution Principal,
- The .NET Framework (3.5),
- A whole bunch of BCL,
- C#,
- Relational databases & SQL,
- Active record & SubSonic,
- MVC,
- Dependency Injection & Inversion of Control,
- Test Driven Development & MbUnit,
- Mocking with Rhino Mocks,
- Design patterns,
- Scrum,
- Continuous integration,
- Source Control Management with Subversion,
- Tools.
Oh, and this needs to be done as we go on with the project.
Can you think of anything I forgot to mention?
Does the order make sense or would you suggest a different one?
Eeek.
