Luhur S Nugroho - All Comments

re: Training .Net (custom curriculum)

Aditya Purwa Wbawa — Thu, 22 Mar 2007 02:10:56 GMT

bedalah antara materi yg dikasih trainer dan yg dikasih developer ... :D ... pasti lebih real-word experience yg developer kasih ... jadi terasa lebih bermakna buat developer kayak kita gini.

re: speaking about unit testing

erudeye — Wed, 28 Feb 2007 03:40:07 GMT

I think this is usefull from architectural design, but i want to know from managerial aspect...

OK, this is impotent ups important, but it's need double resource. To build the software and unit testing it self.

Maybe it could be more completed if added by feasibility study, how big the software is so it has to use unit testing? What minimal requirement of the software to have the maximum result with unit testing?

just my imagination...

re: Biztalk Server 2006 Developer Edition

luhur — Wed, 24 May 2006 19:52:00 GMT

ikutan ready to launch vs 2005,sql sever 2005, dan biztalk 2006...kok gak ketemu ya kita ?

re: measuring your .net development skills

luhur — Thu, 13 Apr 2006 15:46:00 GMT

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! :)

re: How much important using tests dicipline

luhur — Wed, 29 Mar 2006 15:52:00 GMT

jangan terlalu sering melakukan unit testing hur...bisa-bisa molor developmentnya, mendingan tetap berpatokan pada design.

re: How much important using tests dicipline

luhur — Thu, 23 Mar 2006 18:55:00 GMT

performance, skalabilitas dan fleksibilitas is by design, not by luck...;). Software bukan magic.
Dalam project management harus cukup memberikan waktu untuk menghasilkan design yang bagus.
Design yang udah dihasilkan sebelum masuk ke development pun sudah harus melalui serangkaian pengujian (peer testing, peer discussion, etc)

Kalau dalam testing kemudian menemukan cacat design (mostly happened when design time is limited or..u know it..;)), for the sake of the engineering itself harus dilakukan perbaikan. Perbaikan yang akan dilakukan pun harus melalui serangkaian proof of concept sebelum dilakukan yang intinya minimalisir contact surface (abstraction penting disini).

Kalau memang ternyata contact surface-nya luas (really2 poor design)...., coba temukan pola yg dipakai di design itu...kemudian buat tool yang mengautomate perubahan dari design lama ke baru.

Last but not least kalo poor design ini terjadi lebih dari sekali coba berikan training ke designer-nya. Kalau batas toleransi sudah terlewati harus di ingat bahwa setiap orang punya bakat yang berbeda..., probably designer-nya kurang berbakat di software engineering.