686 karma · joined September 25, 2011
I hope the audience is smart and intuitive enough to understand that if none of the co-founders is a coder, then obviously your first hire can't be a sys-admin. With that assumption, having a sysadmin early on will only improve the productivity of the development team as is the case at Crowdtilt.
I guess the better word than Sysadmin is DevOps. Because what the author did at Crowdtilt wasn't just deploying and maintaining servers, but actually impacting and streamlining the development process.
But my main point from the post is I want people to be OK and accepting of "failures". Because in reality, it isn't a failure. It is a lesson that you learned for your next attempt.
One day someone asked Thomas Edison “Aren’t you ashamed that you have failed 99 times?” Edison replied “I have not failed, rather I’ve learnt 99 ways in which an electric bulb would not lit up”
^^ This is what I mean by not fearing "failures"
Lockitron was a perfect example that used Selfstarter to fund their project and got a lot of attention from users without the help of any organization like Kickstarter.
Selfstarter is really cool for a one-off type of project such as Lockitron, but with the Crowdtilt API, you can also build a "kickstarter-as-a-service" type of product, which I would really love to see built one day.
(disclosure: I'm one of the Crowdtilt founders)
I should add that I did use a screen session to share vim though.
I think a big part of it is that once you dig into complexity points and time estimates and all that other stuff, people tend to be on the safe side and add a lot of buffer. But when the whole team is in the hacking mentality and just wants to get sh*t done, you don't need to have everything in sprints. You just need a highly motivated and a dedicated team.
It is so hard to know that @ means array and % means a hash (key/value pair) haha.
This is basically what Modern Perl and CPAN modules are all about. Checkout Perl Dancer as a web framework for example and you'll see simplicity.
Thanks for the feedback :).
I definitely recommend reading "Modern Perl". It is a game changer.