Reminds me of this: Make the climb like the child did - without the rope.

https://www.youtube.com/watch?v=KXxw-zXRqOs

The rope makes you weak!

The same movie also lets the protagonist heal from a incapacitating spinal injury in a dusty pit -

So I'm not sure if this is a pro- or anti-rope statement :)

I would recommend picking a project that you can do only in Assembly. For me, this was creating a special waveform on a microchip controller. I had to create a custom 800kHz signal using a 16MHz clock, so there was no way other than to respect each and every clock cycle, and make the most of it.

The key is to choose a project that you are excited about. If you pick another blah assembly tutorial, without the excitement of a project pushing you, your enthusiasm will evaporate sooner or later.

Here you go:

http://openclassroom.stanford.edu/MainFolder/CoursePage.php?...

Yes

Why did you answer both "Yes" and "No" to your own question?

I think it's a failed attempt to set up a poll by the OP.

No

Maybe, I'll take it on some day

With the high frequency of "Looking For Co-Founder" posts, I was hoping that there would be plenty of success stories around! Please chime in, if you met a key team member (not necessarily a co-founder) or if you know some body who did!

I'm just using a spreadsheet via Google Docs. On one tab, I have broad areas that I want to learn. After that I break that down into weekly milestones based on the book / learning material. This includes projects or specific assignments I'm supposed to accomplish. Once I have the roadmap created, I then follow the pomodoro technique. The pomodoro technique is quite handy to monitor my productivity on a regular basis.

Hi Khetarpai, Thank you, that is the closest that we could get to managing learning tasks I think.

Thanks Svetha for your input and encouragement! My dilemma is to build it on iOS or Android? But eitherways - I've gotta start. For me next step is to finalize the wireframes and approach the golf courses!

Thanks - very thoughtful response! I have been burnt before, so validation is definitely #1 priority for me. I'm still in the wire-framing phase, because I at-least want to take these screenshots with me when I talk to the golf courses.

But my problem is that of segmentation - I don't have the bandwidth to support both iOS and Android at the same time, which cuts off a big chunk of audience.

Since the core of the app is networking - supporting the major platforms is quite important. But hey it is what it is. I've gotta start from somewhere!

What do you mean when you say you don't have the bandwidth to support both iOS and Android?

If you're targeting businessmen, I think cross-platform is pretty important. Most executives are likely using Blackberry and Android. iOS is still trailing in the business sector last I checked.

If you use a cross-platform SDK you can cover your bases and not have to worry about it. Something like Phonegap or Corona could dramatically increase your likelihood of adoption.

I agree with you. By band-width I meant the time and resource I have to devote to this idea. I have a full time job, and in evenings, I have been taking programming classes. So, I didn't think I could support cross platform from the get-go.

Your responses and suggestions are right on the money. What's your background and interest areas?