Researching topic of working efficiently with your mail I came across two more articles definitely forth attention:

• Inbox Master: Get all your inboxes to zero, and have fewer inboxes
• Email Zen: Clear Out Your Inbox

I’m now trying to come up with schema that will work best for me as my e-mail processing workflow quite often differs from traditional read-do-reply/delete cycle.

With growing number of staff in my department I found my self being interrupted more often than I would like to efficiently do what I have to. As e-mail is the main source of information that requires attention for time enough to completely get you away from what you were currently doing I decided to deal with that first. The first thing (probably, not the most obvious one) I did I visited ToDoOrElse blog by Bob Walsh. I came to know about this blog through his another blog and book ClearBlogging. I found his recommendations for bloggers very valuable so it was natural to assay his ideas on Getting Things Done. And I was rewarded for that by link to “Clearing Your Inbox with Minimal Pain” at Web Worker Daily. Going to try this approach in practice.

New York Post reiterated a year-old rumors that Microsoft wants to acquire Yahoo!. In the light of the “Microsoft is dead” essay by Paul Graham. In the web space Microsoft to my mind was always challenger trying to overtake leadership of innovations by others. It will be interesting to see how this story will end.

By the way, Russian translation of Paul Graham’s essay is available here.

If you are seeking for improvement of your modeling practices in software development check out P-Modeling Framework by INTSPEI. I participated in several experiments that lead to creation of the framework. Personally I’m looking forward to see first case studies of application of the framework in “real life”.

If you happen to not know who is Jim McCarthy watch all the video episodes of his “23.5 Rules of Thumb” presentation and read his article “21 Rules of Thumb for Shipping Great Software on Time” based on earlier version of the presentation. Jim left Microsoft to continue his research in the field of team dynamics. The result of this research is The Core: set of commitments and protocols to enhance productivity of teams.

If you think downloading The Core PDF is a waste of time and traffic – just read the thoughts of a bootcamper. Or watch an episode of Jim’s presentation right now.

If you are reading Joel’s blog you probably have read his post about New elevator technology. While this is an interesting idea from pure technology viewpoint, another idea came to my mind…

I believe that USA (together with Singapore, Hong Kong) is the place where such technology was likely to emerge more than in any other country. And almost certainly (alas) such technology could not be invented in Ukraine. Why? Because there is no demand such kind of elevators usage optimization, simply there is no places in Ukraine where it can be applied. Even if a man has a bright ideas he has to be in the right place at the right time for his ideas to blossom. Unfortunately, the factor of place still can limit the greatness of accomplishments one can do.

Mankind has to go a long road as yet to overcome limits imposed by all sorts of divide on the achievements of human race. I hope that in future we will more often learn about technology breakthroughs made in places we now know as “developing countries”.

Well, I did not completely wasted last month blogging-wise. I was looking for hosted blogging solution to move to from dasBlog. It is not that dasBlog is bad, but it turned out that supporting dasBlog (well, my instance of it) consumes more time than I originally expected. I decided that I’d better spend time writing new post rather than tweaking blog engine.

At first I decided to use TypePad. During test drive for the first month everything was going more or less well. The only issue I encountered was somewhat limited capabilities to customize design of the blog with the Plus subscription level. The real problem emerged when they could not charge subscription fee from my credit card. Although their staff was responsive and did their best to resolve the problem we did not find acceptable way of making the payment. So I ended up looking for another alternative.

After comparing all the options I decided to go with Blogger blog hosted on external server.

My new blog is now accessible at blog.dmalenko.org. For some time my both old and new blogs will be running in parallel. As for feeds: those of you who get my feed via FeedBurner do not have to worry about anything, those who are not – please, subscribe to this feed.

It's been a while since I blogged last time. It was busy and interesting time for me. So, I guess, will have something to blog about.

I've come across a good example of Color Modelling and DNC use by Stephen Palmer: Modelling in Colour: Using the DNC. Recommended.

I guess, it's not news that you should prepare for the interview. For interviewer it is about learning candidate's resume and thinking out questions that the candidate is supposed to answer or discuss. Depending on the candidate's level my questions of course will be different, but in general I would divide them into following 3 categories:

1. Academic. These questions are concerned with more of a theoretical knowledge of the candidate and usually assume more or less exact answers. Something like "What is garbage collector? How does it work in .NET?" Also I try to put such questions in a way that will allow me to ask follow-up questions and elaborate the topic. E.g. if candidate says that there is generational garbage collector used in .NET, I would go ahead and ask what other types of GCs the candidate know and how they compare to generational GC. (Unfortunately, not so many candidates can take up a talk in this direction) If candidates know nothing about generational GC they usually compare .NET GC to Java by saying that .NET GC is "much better". Asking for more details is logical next step :)
2. Experience. Here I usually start with "What is your greatest professional achievement you are really proud of?" Then questions go to most remarkable notices from the resume.
3. Discussion. Questions or rather topics that allow more or less informal discussion. Often I just ask questions that I'm just curious about which are relevant to candidates experience or interests. Something like "How long does it take boost libraries to compile?" and so on about "usability" of boost. For me this section of interview is not about knowledge, but about opinion. I kind of assess candidate's general ability to think and present his thoughts.

Actually, if I see that that candidate feels comfortable on the interview I may use fourth category: provocative questions. Questions or assertions that go against common way of doing things or accepted knowledge with weak or irrational reasoning behind. I just need to say it confidently and ask the candidate for opinion. Well, sometimes I play so good that after all I have to say that it was just a joke and in reality it is somewhat different then I was saying.

Also the interview I try to create an atmosphere that helps to make it easier for the candidate to show his best. And I ask tricky questions only if I see that candidate can handle them. Interview is not about showing the candidate how miserable his knowledge or experience is, but about making him show everything he knows and can do.