Domain/Software 2009.04.09 21:53
[[ blog 이사 과정에서 정확한 posting날짜가 분실됨. 년도와 분기 정도는 맞지 않을까? ]]
Let's consider two different level - Coder, Programmer.
Coder is engineer who can modify and implement not-big-size source code under the given SW architecture, requirement and environment.
Programmer is engineer who can define requirements, design SW architecture, analysis and fix system-wide-issues.
At first, we decide which level of SW engineer should be recruited.
To recruit Coder, following questions may be enough.
- Questions about language syntax and it's application.
- Simple problem-solving-ability (ex. simple optimization and so on.)
- Coding test. (ex. implement linked list, Queue or Stack etc)
But, to recruit Programmer, you may need additional questions to know about his/her programming policy and values.
- What's your opinion about 'modularity'?
- What is 'software layer' and what it should be?
- Please tell me about 'information hiding'
But, someone may give well-known answer that may come from books. So, detail and concrete question should be follows.
For example, followings can be asked after question "What's your opinion about 'modularity'"
- Then, What should good modular architecture be?
- Show example of good modular architecture.
- What kind of design can be used to connect between modules.
- What is good interface design to support modularity?
- Please design linked list with C language focusing on modularity.
... I am not sure that this kind of evaluation can be possible in practical. But...
|[GNU] Issues of cross-compiling in GNU build system. (0)||2011.04.21|
|[Tips] Cyclic Queue (0)||2010.10.18|
|[SW] Questions to evaluate SW Engineer (0)||2009.04.09|
|[Prog] Using so-called 'context' data structure. (0)||2008.01.10|
|[Prog] Take care of errata when using float/double at all times! (0)||2007.01.26|
|[Spec] DWARF2 (0)||2006.08.30|