Successfully is rather overstating it. The shipment of Soylent was delayed by over a year and went at a snail's pace. My shipment was delayed at a rate of roughly one month per month, with it eventually arriving something like six months after the first shipment had gone out, despite being one of the first backers. I can't think of a single metric on which I would call the Soylent shipping process "successful".
How We Spent $500 on Tech to Ship $2.6M of Soylent
21–30 of 78 posts
Re: How We Spent $500 on Tech to Ship $2.6M of Soylent
#22This is a really good example of why you need a 'hacker' in your startup, in the traditional 'one who is good at building ad hoc systems' sense. Having awesome technologists who can write brilliant, well-tested and robust code is certainly useful, but a lot of the time in the early stages of a company you just don't have time. You have a problem and it needs to be solved fast . Most things can be fixed later when the…
Re: How We Spent $500 on Tech to Ship $2.6M of Soylent
#23Don't eat soy.
Re: How We Spent $500 on Tech to Ship $2.6M of Soylent
#24"a $500 system that successfully managed the first four months of Soylent shipments." Successfully is rather overstating it. The shipment of Soylent was delayed by over a year and went at a snail's pace. My shipment was delayed at a rate of roughly one month per month, with it eventually arriving something like six months after the first shipment had gone out, despite being one of the first backers. I can't think of…
Re: How We Spent $500 on Tech to Ship $2.6M of Soylent
#25Re: How We Spent $500 on Tech to Ship $2.6M of Soylent
#26He can only say this because they are profitable. In reality I think they were lucky to have a product people wanted so badly. In the first 12-18 months, most of the complaints by actual Soylent customers about Soylent had nothing to do with the product itself, only the fulfillment.
Re: How We Spent $500 on Tech to Ship $2.6M of Soylent
#27Earlier quoted context omitted.
If you put the apostrophe in front of a number, and save it as csv, that works. But if you reopen that exact same file, Excel will still misinterpret the number. The issue here was that there's no way to let Excel know that this value in this CSV file is not a number. The only way around it that I know of is to stick with xlsx, which has its own pain points.
Would it still be an issue with TSV? That's my preferred flat file data format, find it less error prone compared with CSV.
Re: How We Spent $500 on Tech to Ship $2.6M of Soylent
#28Re: How We Spent $500 on Tech to Ship $2.6M of Soylent
#29Don't eat soy.
Why?
So right now many, myself included, advocate minimizing soy. You can't get away from it. Thanks to several US administrations soy is huge business. Just watch it. It might be that its good for you. Right now the soy debate is much like the egg debate of the 80s. I leave you with Lewis Black's commentary on food nutrition: https://www.youtube.com/watch?v=tXS5GBuk-GQ
1 - http://blog.zocdoc.com/does-soy-feminize-men-fact-vs-myth/ 2 - http://wwf.panda.org/what_we_do/footprint/agriculture/soy/im... 3 - http://en.wikipedia.org/wiki/Soybean#Nutrition
Re: How We Spent $500 on Tech to Ship $2.6M of Soylent
#30This is a really good example of why you need a 'hacker' in your startup, in the traditional 'one who is good at building ad hoc systems' sense. Having awesome technologists who can write brilliant, well-tested and robust code is certainly useful, but a lot of the time in the early stages of a company you just don't have time. You have a problem and it needs to be solved fast . Most things can be fixed later when the…