khetarpal

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!

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

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.

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?

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!

I'm thinking about a way to call bullshit on such job descriptions. Not sure money is the answer though. What about interesting jobs / startups that can't pay that much?

It would be nice to get a crowd sourced mechanism that involves employees / ex-employees / vendors who could provide a well rounded view on what is the job really like, and not just some marketing spiel from hiring manager

If engineers suck at finding the right job, and companies can't find the right people, then this problem is screaming for better solutions. The challenge here I see is that every employer is looking for 'rockstars', even if the actual job responsibilities may not require one.

So, if I'm a 'rockstar', its a big hurdle to separate the reality from the marketing pitch of the magic job. What can be used as a signal for filtering good quality jobs from the less desired ones? It's surely not money, because plenty of big companies will pay you ample to make good power points.

I think a startup that can figure out the right mix of signals to indicate the job quality, which may be a combination of challenging problems, team, work-environment will really hit it big.

The power of habit by Charles Duhigg.

Whether its getting up early in the morning, going to the gym, learning new skills - it all comes down how good a person is in forming new habits and sticking to them.

This book helps get into the mechanics of how habits are formed, and the elements that will help make them stick. The best part is that the book is loaded with specific case studies for both personal use as well as case studies relevant for product-based organization.

I loved it! Not that I'm going to the gym any more regularly though :)

I like the way you put it - "Put simply, go to where your potential users are".

I would add - Think about not just users, but power users! At-least in the begining you are not looking for a regular joe, but somebody who would benefit the most by your product, and be the cheerleader moving forward.

Nice and clean! Keep it up guys!

As an engineering manager - I'm all for pursuit of knowledge and excellence. I could care less whether a person has a degree as long as he has the subject matter expertise. Multiple well respected engineers in my group don't have a degree.

I think its really a personal choice. You can get a degree and not have to keep justifying your choice, and how good you are even without it. Or, you can be a strong man and choose to ignore the mainstream perception. Either ways, the knowledge and subject matter-expertise is non-negotiable to succeed.

Well written, and totally agreed that a degree stamp / piece of paper is not an indicator of the knowledge or passion of the individual.

However, I do know that lack of degree is always weighing heavily on the individual who doesn't have it. This further leads to compensatory behaviour

My 2 cents - I think an individual is better off taking small steps towards getting a degree than justifying it for the rest of their life.

Top notch guy, but unless you know him or have any political weight, he's not going to take the case.

Hi Daniel,

My uncle is an ex MLA (member of legislative assembly) and is lawyer by background. He may be able to help. I have spoken to my dad about this, and he will connect you.

Please call him @ [redacted].

Best of Luck!

Sumit

- Be prepared to sell, sell, and sell - But first, you need to be sold yourself. So start answering questions in a structured way. Dave Mcclure gives a nice framework here: http://www.slideshare.net/dmc500hats/ - Even though the slides are for a VC, that's a good framework no matter who you are pitching. - Once you are convinced, start looking at building a well balanced team. - Your team / co-founder(s) will be the most critical piece. Don't compromise on the quality of people you build around yourself.

Good Luck!