redspark
Joined 14 years ago
Joined 14 years ago
You will end up throwing out much of the initial code, but use what you know in order to get in front of customers and collect feedback.
Your customers don't care what language/framework is being used, they only care that you are easing a pain point for them.
Vagrant/Puppet for local development
* this way every developer has an identical dev environment.
Git for code versioning - Github/Bitbucket for repo hosting
* each feature has a branch, then we use pull requests for review/merging into staging branch.
* when features are LGTM and tested, pull request to merge into production branch
Capistrano with multi-staging to deploy to staging and production servers
* every developer can deploy to staging
* only a few developers can deploy to production.
Why do so many operate under the assumption that remote workers are a handicap?
I have a separate dedicated office building, and don't work from my bedroom, living room, etc.
The driving force behind most of the new languages I have adopted; is a friend with experience who plants seeds, then can offer support and answer simple questions as I am learning. I have no friends that I know of who use Erlang.
Leaves you with mixed emotions.
We have extensive experience implementing and teaching lean principles. We primarily handle backend work, but have a designer and UX guy at our disposal. We love analytics and customer feedback.
Email: [email protected] skype: spinuplabs
Photos -> http://www.redbubble.com/people/sikhcaptain/works/10813204-c...