I liked the article. I think another point to bring up is that if you're interviewing a developer / technical co-founder and you yourself are not coming from that background, it might be a a good idea (at least from my own personal experience) to have a friend who's technical who's opinion you trust with you during some of those meetings to give you an objective and external view on things. I think there's a chance that might help you make a better, or at least a slightly more informed decision. Just my two cents..
When reading about the lean start-up movement (of which I'm a fan) a question that comes into my mind is - can LSM techniques be applied to more traditional technology areas such as storage, networking or even stuff like medical equipment? I'm sure they can be, and would love to hear from folks here, what they've seen in that area or how they think those can be applied there.
This looks super interesting. I personally like the way JS is maturing into the back-end, with stuff like this and node picking up steam. What I liked about this site, even while I'm installing it to play with it, is that they seem to have put in a lot of effort on it to make it intuitive + clear , even at such an early stage (just to be clear - this is the first time I've seen it). I'm taking this for a test drive to play around with it, and hopefully if it works well find some place down the line where I can put it to use.
Hi! congrats on your new site. I think it's a lovely effort, and very worthwhile. One piece of input, at least from my end, is to provide your users not only with the answers, but also with some elaborations on things they should / shouldn't do when writing code. This will be of course more evident when they tackle problems when they have to work with string or collections and things like that. Instilling some good principles, even just slightly, at the very beginning is something which will dividends for people learning to program just a bit down the road. Just my two cents, and once again - great job and best of luck!
Even regardless of the outcome of each program, just the fact that we're starting to have this discussion in the open is a big step forward, in my mind at least. I do understand that by discussing some of these plans we are in essence hampering their effectiveness, but my feeling is that in the grand scale of things it's a price that I think I'm willing to pay. Just my feelings.
I love the part at the end, where the writer talks about how such an important part of finishing something, is just making the conscious decision of finishing it and moving on. It's for small tasks as well as larger projects. Not getting caught up in that last 5% is definitely something we want to be able to do and something to aspire to.
I think the rising interest of people to learn how to code is a trend that can't (and probably shouldn't be) stopped. The post uses an analogy of everyone wanting to be chef. My sense is that it's more like everybody wants to learn how to cook something. There is a big difference in the kind of qualifications and experience you need to be a chef in restaurant or a developer working on a secure banking platform, than cooking a meal at home or someone building a small social app our of interest. Those we'd better not get mixed up :) I do hope that from a technology / security standpoint we'll see some innovations that would at least help inexperienced developers produce more secure code, by possibly hiding some of the complexity from them. Tall task - I know. But as I said, at the end of the day you do want your critical 24x7 apps to be written by pros. Just my two cents.