integraleq

Sorry that I did not mention that part: This was actually for a job interview. So, it had to be completed in a short amount of time.

Man, that game is so much fun!! It gets really hectic at points! What are the guys the spit junk at you called? Are they like bosses?

You are correct about the representation, but I went for the most low-scale approach since the search space is so small. The next version will learn how to build its own rules, but that is for another day. Thanks for all of your help though. I really appreciate it.

You are correct. So I suppose I should alter my previous post by saying that it is a good way to go iff you are also willing to be diligent in your updates to keep the documentation as current as possible.

Ok!!! Round 2! Any challengers?

Thanks a ton! I will tighten it up! Hopefully, you will pull the next release and try to beat it again. I do hope it was not a complete pushover.....

I personally look for a neat collection of tasks that I would be performing as well as a required skill set that I actually have. I used to really want to do telecommuting, but have since backed out of that desire since it tends to give your fellow employees license to frown at your ability to not have to be in the office. I also like posts that are not a generic list of incomprehensible gibberish. I will say that it seems even the most bland-sounding of companies have 11/12 these days on joelonsoftware. What's that all about? Has every company become "that company"? I joke of course. All tangents aside, these are the kinds of things I look for.

That is not a bug. It is there because these locations are just not initialized. How did you manage to beat the cpu? Can you remember the last state of the game board which led to your victory? Thanks.

Check this link out: It might help you.

http://www.amazon.com/Cracking-Coding-Interview-Fourth-Progr...

That is a real dilemma. If you feel more connected here, then it makes more sense to stay here. Of course, I understand that this might mean that you would have to work for an employer for 7-9 years, but I think that this will give you time to be financially stable and also to start working on some startup stuff in your non-working hours. This is hard to do, but with discipline it can be done. Going broke would make me not even consider the second choice, since that leaves you in a vulnerable state mentally and financially, which is no better than simply staying in the US and working for some company. One of the good things about having a stable job is that you can bootstrap the initial stages of your own company. I know I cannot completely answer your question, so please just take this as a bit of advice from a potential friend.

You should always be honest. If you are worried about them thinking that the startup will interfere with your work at the company, just be consistent in doing what you say you will do and do not do startup stuff when you should be working. Between that and full disclosure, you should be just fine.

Which part did you find buggy? I would like to tighten it up. Thanks!

I would still say that it is better to expect failure. That way, when you succeed it is more of an 'oh, ok.' moment than something that causes you to think too highly of yourself. Once I personally learned to get over the fact that I am smart, because, so is everyone else in my field that is worth their salt, that made it much easier to walk forward and not get turned back by rejections or failure.

I would agree with you, but I think there is something to be said for the kind of mental dexterity it takes to do higher-level thinking while having a detailed view of what you are trying to accomplish. I would not want to give up all lower level cognition though. To each his own I guess.

I would also agree with that sentiment. What you do on a consistent basis more than likely becomes "short-circuited" into your mental perception of the world that you navigate from day to day. Much like not using a programming language that you knew well for six months can, I believe, cause some kind of "mental atrophy" in that particular skill set.

this is an excellent post and quite relevant. i have found this kind of epiphany as well while writing a python based framework at my company. i would extend the README driven approach to even suggest a developer blog driven design methodology, since it allows for a more dynamic way to clarify points and also add diary entries for 'thinking aloud' while you are building complicated libraries.

Interesting! I am in Springfield,MO. I am not looking for a job, but how can I keep up with what your startup is doing? Could you send me info on what your company is about? Thanks!