This is smart advice, but by listing specifics I think a larger point is glazed over. For a business founder, struggling and hacking your way through a seemingly intractable technical issue is the critical formative experience. It's not about the tools - they're necessary to have the experience, but not sufficient. To me, it's about the intellectual approach of hacking. Marketing/product and technical development are both part-science and part-art, but technical development trains you to break down large problems into discretely approachable steps, while still keeping a wide view of the problem incase you find an improved fundamental approach.<p>Once a business founder has hacked his way from an idea to a polished version of <i>something</i>, he can be much better at his job.
<i>If you work in a small team, especially a startup, knowing what’s going on and how your product works is valuable also to a non-technical business co-founder</i><p>Couldn't agree more! (especially for product people)<p>Can you give more specific details about how it helps you/the team? (no sarcasm here, I'm genuinely interested to understand this form the marketers' perspective)
Just one thing that obviously jumped out, the link to the MVC explanation is not great.<p><a href="http://www.codinghorror.com/blog/2008/05/understanding-model-view-controller.html" rel="nofollow">http://www.codinghorror.com/blog/2008/05/understanding-model...</a><p>This dude says MVC == HTML, CSS, 'the browser', respectively. Not sure many would agree with that assessment. If anything those three could, I suppose, be viewed as a separation of concerns, calling it MVC however, just seems muddy.<p>For example the way I see the pattern in terms of web apps (and MVC is not a domain specific pattern in any respect either):<p>- <i>model</i> should be largely in code and data and contain the business logic, not HTML.<p>- <i>view</i> is a mixture of HTML/CSS<p>- <i>control</i> is a mixture of the browser engine's logic and client side javascript.<p>Also Github and .NET don't seem to fit well together based on the types of communities. ;) That's not to say they can't in the future, just speaking historically.
I don't see why you need to learn vim. Just open your files with your preferred editor from the command line, as in Michael Hartl's Ruby on Rails tutorial. It's a google away to set up 'subl' to open a file in sublime text 2, for example.<p>I think the larger idea of knowing the surrounding tools and resources is crucial and can be glossed over (for example, not once has a professor at my university mentioned StackOverflow). Great idea making this post mikk0j.
Am I the only one annoyed by tutorials in video form? I can't hear myself think, I can't set myself the pace, you can convey up only so many informations with sound and image... I like real <i>lectures</i> in video, but it's not a really good format for quick tutorials.
As a techie, what I would love is "A Technical Guy's Guide to Marketing/Sales" that basically talks about the various concept and jargon a techie should know to run a business.