Luhur S Nugroho

Windows Workflow Specialist
See also: Other Geeks@INDC

measuring your .net development skills

Jika kita lama ber .net ria, muncul pertanyaan baik dari diri kita sendiri maupun orang lain, sejauh mana skill kita pada bidang development software dengan .net? bagaimana kita mengukurnya? pasti akan banyak jawabannya!,jika jawaban orang non technical/awam pasti menjawab ukurannya dengan sertifikasi professional, jika orang sudah mempunyai sertifikasi di bidang .net akan dianggap menguasai .net, walaupun belum tentu terbukti apakah mampu membuat solusi software based .net yang benar. nah bagaimana dengan jawaban orang technical(kita sendiri yang berkecimpung di .net)? ataupun jawaban orang berpengalaman memanage project .net? tanggapannya saya tunggu...
Share this post: | | | |

Comments

luhur said:

Yang biasanya saya lakukan utk assess .NET skill level candidate employee adalah ...

1. Experience

It's simply the resume:
- What kind of .NET projects have someone DID,
- What WAS his role (Architect, Dev Lead, Dev)
- What WERE his contributions (built UI, Library, security, performance optimations, object model design, etc)
- How .NET WAS used (what .NET APIs were significant in that project, is it common APIs or are there 'advanced' APIs, what APIs he worked with).
Experience is the best judgement. But, someone can lie in his resume. Or the resume doesn't reflect those things. So... (see next).

2. Knowledge

Thru deep technical interview.
First, confirming what was written in the resume (see above). Or asking them the questions above.
Second, I will also ask tons of questions of:
- CLR (From simple things like: 'What's an AppDomain?', 'what's MSIL?', till advanced CLR internals).
- Most used APIs from .NET Library (anything in System.*)
- C# language (like: What's 'lock' means?, what's Generics, etc)
Semakin banyak dia bisa jawab pertanyaan berarti semakin tinggi levelnya. Artinya, dia benar2 "kenal" .NET.
- Upcoming .NET (next version of CLR, The Library, C#)
How far a candidate following the technology advancement.
It'a bit hard to lile here...

3. Skill

I used to give a programming task. The candidate to complete the task (yes, coding on the spot) and we will together walkthru each line of code. We will review the motivations why the code become like that, the object model, the algorithm, perf, security, etc.
You can lie... but code doesn't lie! :)
# April 13, 2006 10:46 PM