169 karma · joined November 30, 2010
Javascript Developer, UI/UX Designer. Interested in many many things.
Everything starts to revolve around your companies point of view instead of around what you think most people want. I think he makes a great point, and relates directly to this awesome talk by simon sineck http://bit.ly/eLt15m.
People develop personal relationships with a point of view, thus helping you develop a brand not just a product. And not only a brand but one that stands for something and has values.
I think this is the most important thing you should be thinking about when approaching product design, customer service and financial responsibility.
Although I'm not one hundred percent certain what you mean by financial responsibility. I'm assuming your referring to corporate social responsibility, I'm not so sure that this has much place in a startup.
I would love it you could expand on this.
I agree with main point that shipping is the most important thing you can do. And you should always ship what you have done. In the case for startups it can easily be referred to as shipping in stages. Not delaying shipping because your product isn't fully built, and then shipping the rest in small chunks over time. You shouldn't have a fear that causes you to wait until your product is complete and perfect to ship.
But just shipping isn't the correct solution either. It's a case of balance, you have to find the right one. There is no hard answer to what that is, it's down to you. But as the post says don't let that stop you from shipping anything at all.
I doubt that the intention of the post was to suggest you should just ship anything. But that is a prime example of sometimes taking the time to express yourself correctly. If the author didn't just click the ship button, and took a little bit of extra time he may have expressed that part the way he intended.
On a separate note, I agree with the comments about the per day pricing. It is a little confusing and I would rather just see a monthly subscription cost, with a few plan variants based on # of projects and users. Your making me think to hard about paying for something when I have to start calculating how much it will cost me. You should definitely consider simplifying it.
I disagree with the comments around pricing though. I think that estimated cost is well worth not having hassle, and when you consider it to the cost of say your mobile phone bill. Just ask which do you use the most, more importantly which one is making you the money in the first place.
If I'm honest I think the pricing is a on the low side, However I wouldn't limit the free plan to "open-source" projects either. Depending on how you are quantifying open source. If you require a public github repo then I would potentially suggest it's a bad thing. People need chance to use your IDE for a project to see if they are willing to pay. Allowing only say one or two projects makes more sense I think.
You can mail me at, me[at] ashmokhberi [dot] com
Thanks very much in advance.
Thanks for pointing it out. :)