n_t

This looks like much more involved and longer project. But still I'll get your book, looks very interesting :)

JVM might be much more involved project but here is a simple virtual machine - https://github.com/skx/simple.vm

It's great book. I liked it too.

Very nice! These days think of something and someone somewhere has not just thought about it already but also making money out of it :)

Great stuff! Thanks for it.

It certainly is a good course and I recommend it too. However, this is a full-fledged class requiring many weeks instead of few hours or days.

Good one!

It's difficult to give any advise without knowing more about your background. Finding job can be uphill task due to many things -

1. Age factor (above 40 might have some challenge finding new job)

2. One and only one skill in quiver and if that's antiquated, even more challenging to get job.

3. Resume doesn't match experience. E.g. in industry for 7 years and have nothing significant to put on resume. You wont get contacted at all, probably.

4. Interviewing for position/group/company which do not align with your skill sets or experience.

5. Lack of interviewing skill.

6. Lack of depth in domain of interview.

7. Some personality trait which is becoming hindrance.

I think all of above can be tackled in some way, one just needs to identify the problem. My advise for interviews in general is -

a. Pick one generic domain and try to learn a lot in that domain instead of glossing through tonnes of terms.

b. Pick one language and stick to it for practicing interviews, you can always learn new language on job once hired.

c. Pick companies to apply for carefully. See if their product or requisition matches with some of your skill set. If they invited you for interview, focus on those match and try to project them. Even if you dont do well on certain things, your grasp on some other area might sway the interview.

d. Be enthusiastic, even if you are tanking the interview. It's not end of road.

e. Treat each interview as preparation for next one, instead of do-or-die situation. Be mindful of your shortcomings and mistakes and then practice on correcting them before next interview.

f. Apply to companies where you know someone. See if they can help get some feedback for you.

As others said, interviews are not valid measure of skill. There is no way interviews can find if a person is in wrong business, so spend some time on job before coming to that conclusion.

* edited for formatting.

What a surprise to see my teacher's home page on HN. Also, totally no surprise that he gets limelight not for his CS stuff but bookbinding :D

how do you measure the soil moisture? I didnt see anything in supplies and both graphs didnt had anything.

As if they already don't have enough, feed more data in to Google.

Extending this post to ask, what are some of your favorite programming books and why? I still remember Peter Van Der Linden's expert C programming for it's humorous approach and Friedman & Matthias' The little schemer for it's gradual build up.