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
I imaging there are some of you out there like myself who are a step past freelancing and have a team to tackle entire projects or augmenting another team.Please lead with either SEEKING PROJECTS or SEEKING TEAM, your location and whether remote work is a possibility.
Photos -> http://www.redbubble.com/people/sikhcaptain/works/10813204-c...
You might think about narrowing your question down a bit.
We do some of that in a consultancy masterclass I am part of, but nothing that organized.
2. Get in touch with owners/managers in your chosen area.
3. Take them to lunch and discuss their business. Watch their face and when they show you a pain point, try to pinpoint the cause.
4. You should discover more than a few problems they would spend money to have solved if you talk to enough of them.
5. Follow up with an email thanking them for their time and mention again how you have been giving some thought to a particular pain point. Try to find an article, software package, etc that attempts to solve their pain point and send them the link.
6. Build a true MVP (should be embarrassing, yet offer value to them), and follow-up with an email. Tell them you have been thinking more about their problem and wrote up a quick dirty app that might help them. Offer to demo it for them. While demoing discuss how much their pain costs their business.
7. Iterate based on their collective feedback.
8. Based on the discussion about pain costs, come up with a value-based price for your solution.
9. Refine your MVP, follow-up with another demo. Sell them a subscription to your solution. It may still be rough, but you should be able to demonstrate value and savings compared to their pain costs. CLOSE THE DEAL.
10. Follow-up
11. Iterate
12. Follow-up
13. Iterate
14. Follow-up
15. Iterate
16...Rinse... Repeat.
There are problems all around us that need solved. Most people only want to solve the sexy problems, but find a niche that you know well and start doing interviews with people in the field. Talk to enough of them and you should discover a problem they will pay you to solve.
Tell us what it is and we can give you better information.
Any good developer should recognize that encoding. :-)
Just curious why we are still serving them as xml and not json??? Then they would basically become a REST interface, right?
If not what features is flippa or others missing.
On patent transfer, I am not familiar with that, but I would assume that process is much more complicated than transferring ownership of a site and domain name.