4 ms·

I think the argument was poorly worded, but I agree with his point, which is that his business is stickers, not software. Hence, his advice is invalid when appl

I think the argument was poorly worded, but I agree with his point, which is that his business is stickers, not software. Hence, his advice is invalid when applied to a software business. If you run a physical business, the only thing you need a programmer for is probably a website and an online ordering system. In that case, the founder doesn't need to learn programming, as that's not his business. But when you're a saas startup or something, software is your business, and a non-technical founder should at least try to understand some of it. Not necessarily enough to contribute to product development, but enough to... edit basic html? Start/restart the server? Quickly debug and figure out a small technical problem when demoing the product to potential customers in case the programmer isn't available?

run4yourlives 15y ago
I'd argue that software is never your business. People use your software to do something. Understanding that usage is your business. Perhaps it's semantics, but I think it bears repeating.
- wnight 15y ago
  That might work for cookie-cutter, by-the-book managers later but it won't work for a founder, or anyone developing anything new. I've hired construction crews before knowing about the area, and again after working in it myself. It's a night and day difference. And not because they specifically lied or even stretched the truth but because they didn't tell me what I really needed to know to make good decisions. If all you want is "a blog" then you may be happy with what you get without more thought but if you want anything more complex than that you're going to need to understand significantly more about what you really want and how the constraints are going to impact it.