Re:How To Become a Successful Freelance Web Developer (and N...
by karolisd on Thursday December 27, 2012 @11:08PM
(#4976387)
That's what I've seen from my experience. But I might have a limited perspective. Could you provide some examples of interesting freelance projects for a single developer?
[ Parent
| on HN ]
Re:How To Become a Successful Freelance Web Developer (and N...
by rahoulb on Friday December 28, 2012 @05:06AM
(#4977172)
I have a long term client where initially I took over maintenance of a Rails-written brochure site as their existing freelancer was moving on. From there the relationship developed and I now have built a suite of inter-related apps (and manage their own private network) for them (on a retainer so I have guaranteed income). The work isn't cutting edge but its much more interesting than churning out sites according to someone else's design.
Re:How To Become a Successful Freelance Web Developer (and N...
by rahoulb on Wednesday January 02, 2013 @03:11PM
(#4998958)
To Jesse who emailed me; we had an outage with the EmberAds support system, so I lost your details - please mail me at ycombinator at madeofstone.net please.
Re:How To Become a Successful Freelance Web Developer (and N...
by Alan01252 on Friday December 28, 2012 @03:50AM
(#4977030)
This really comes down to confidence in your ability.
I wrote http://myanimcalcam.com by myself. This site is definitely more complex than a standard Wordpress install, but didn't require a team.
I also find adding features to existing sites a good source of "interesting" income. "I've got a website that does this but I need it to do this too" is a common problem I solve for my clients.
Also I'm not afraid of straying away from the "I built websites role" by producing in house systems for companies. A lot of these applications can be done by a single developer.
Re:How To Become a Successful Freelance Web Developer (and N...
by Hawkee on Friday December 28, 2012 @05:52AM
(#4977243)
I took over development of a fairly large Drupal site with Ubercart and multiple external API tie-ins. It took the original team nearly 2 years to develop it for a rather large client. Now I'm the only developer working on it making some interesting and sometimes complicated changes. I find this to be an ideal client.