4 ms·
I've done this eight years ago, delivered a prototype in Ruby on Rails with MongoDB for two educators from the mid-west. Six timezones between us and though I k
by TomK32 8y ago
I've done this eight years ago, delivered a prototype in Ruby on Rails with MongoDB for two educators from the mid-west. Six timezones between us and though I kept developing for them, most of the time as the sole developer, I never met them in real life. Expect the company to run out of money every now and then, be prepared and you'll be just fine. That's startup-life :)
Would I do this again? YES. I enjoyed having the freedom to make technical decisions from the database to the amount of tests I wrote (the app still has some 80% of its code covered, the rest is just the admin area I never cared writing tests for). We also got the product out early to customers. Make sure the decisions and implementations you do are there for the next five years. Don't attempt something stupidly new but stick to solid tech with a good ecosystem that you can rely on without having to keep track of it all the time.
Mind you, I mentally wrote off the little equity I had (the hourly rate was great) since it just didn't grow exponentially, I rather see the company around another eight years without me.
What I'd do differently is to set myself a target, say three years. If by then the company didn't grow as we wanted it, I'd go and try with another startup.