Slashdot Mirror
Finding Programmers to Build a Website?
jameseyjamesey asks: "I have a really good idea for an Ajax/Web2.0 website, but I have no idea how to code or put it together. I know what HTML, Java, PHP are but I have no idea clue how to code or program. Due to my demanding job, I also have no time to learn how to code. I have the layout, design, options, settings and method of making money all mapped out. Who can I talk to, and where can I go to work with someone to get my website developed and off the ground?"
The AC said:
1: phonebook
2: google
I would add:
3. http://scriptlance.com/
It depends what you want. Do you want to sit down with someone and talk over needs? Call some local ISPs and ask them for recommendations.
Do you want to find a big company on the internet to help you? Google has plenty. Hint: pick a few tasks you need to perform and search Google for how to do them. Contact the authors who give the best examples.
Are you willing to risk a little? ScriptLance has a large number of people who are qualified to do the work. You will have to wade through the sludge though.
If you are really brave, you could post your contact info here. There are certainly qualified web designers who post on slashdot. Heck, a year ago, I would have bid on this. Sounds fun.
Get an experienced developer with experience in software architecture and website development, then get several interns who are young, but promising. Give them a lot of exposure to every buzzword you can in this area so that they can get their resumes well underway. Most of them will consider it a bargain and it's a good way to train up a new generation of domestic coders.
As I go to DeVry (yeah, it's even crappier than most people imagine), I think I may be able to shed some light onto the whole "it would be free" thing. The thing about it is, the student's really don't have much of a say. DeVry technically owns the projects that students do for their Senior Projects. DeVry then works out a deal with the companies in turn saying that they get the work done for free in exchange for filling out a bunch of extra paperwork, and agreeing that there is no warranty, support, etc.
University ownership of projects aside- there is another reason talented college students may come cheap or sometimes free. Most "entry level" jobs now still want a couple of years experience, and it's really tough comming out of college with a degree and nothing else. I'm sure it's not an exclusive to DeVry- but there are a lot of people who graduate with high GPAs and very little skills in their fields. Because of this, a lot of talented students are willing to barter work for a good reference on their resume and perhaps some work of mouth advertising.
I do agree that for most projects you are extremely unlikely to find students who are fully qualified (I would agree that 50:1 odds are about right), however in my experience there are a lot more students with experience coding with LAMP/WIMP/etc than in other environments.
Famous Last Words: "hmm...wikipedia says it's edible"
1. A real engineer's time is worth 100/hr without headhunters.
2. Ask for rapid prototypes prior to any bids.
3. Ensure that the developers have extensive experience in the business or trade of the solution's realm.
4. Take care to never tie in to any proprietary technologies.
5. Choose the correct tools.
6. Make sure that the people developing the solution are focused on developing the product, not a framework for the product.
7. Know that with modern web development technologies, that product life cycles are completed monthly with milestones weekly.
8. Make sure that the development process is Quality based with regression tests and configuration management.
9. Be convinced that another team can easily manage whats developed at any time.
10. Ensure that requirements are documented to ensure whats to be delivered is well specified and keep engineering documentation light and only updated after major revs because it is constantly changing.
11. Ensure that the project lead is well versed in development AND networking.
12. Start the project by defining milestones and prototype the deliverables so you can easily track performance.
Theres much more to the SDLC depending on the requirements.
You always start with the Business Case. The Business Case states the objective of the project, the benefits of the project, and importantly how the money is going to work.
You need to map out the costs of the project. Consider the hosting costs, development costs, advertising costs, and your time!
You can even have a few different models - consider that the development might cost twice as much as you think!(IT projects always seem to cost twice as much as what was in the Business Case)
The Business Case also incorporates how you are going to make money. How long will it take to re-coup the project cost.
You also need to map out the delivery time for each portion of the project. Have at least monthly milestones (or weekly if you can)
Very very often your great idea doesn't look so hot once its all mapped out like this. At this point you make the decision to bank roll the idea or not. Let your wife look at it, and also maybe someone you admire for their business skills. They will give you feedback about your idea.
You idea doesn't have to make your rich - sometimes its just great to do something interesting!!
As for finding developers - again thats a question that I find very simple. All you have to do is hire one ! Good ones will charge at least $100/hour. It seems like a lot to you but when you are free lancing 1/2 your time is chewed up finding work. Most consulting firms charge 3 times what they pay to the worker. Thats just how the $ works out.
Go for someone local, interview a few people and find someone YOU can work with.
You have to be upfront about the contract. (Yes - you have to write a contract with this person). It can just be 1 A4 piece of paper with your company logo and details. YOU own the code! For $100/hour YOU own everything that they do - and they have to give you all source code. Give them 20% up front to get them started. On the first protype (at least most of the major functions should work) give them another 40%. The rest on delivery once you have checked everything works.
Once the site is up and running you are going to want to make changes. The best person to do this is coder you just hired. So keep a good relationship with this person. At this point you are probably going to hire them by the hour. Write down all the changes you want and get them to tell you how much each will cost. That way you can prioritise your upgrades. (This is called benefit analysis).
I can design websites (see my professional webpage), but I cannot understand this obsession with ajax... ajax here, ajax there...! I am fed up with Ajax and Javascript, and I believe they are bad for usability and compatibility. can you give me ONE good reason why one should use ajax instead of web standards and (if web interactivity is really needed) java?
Some of what you say is true, however...
'A 22 year out of college kid may know how to code some stuff, but they're VASTLY inadequate for medium to large sized projects.'
That's a gross generalization. There are kernel maintainers who are still in high school (last I heard, anyhow). I'm 22 and I've been using PHP to build CMS systems since I was 16, which is coincidentally when PHP 3 came out.
Young != inexperienced
Thanks.
Why the hell call it a CV? Have you no actual work experience? Or do you believe that academic terms carry more weight?
Slashdot - where whining about luck is the new way to make the world you want.
In European English, "CV" is the term used for both academic and "real-world" jobs. I've never heard the word "resume" from anyone from Britain or the continent. As I have spent most of my adult life in Europe, such are the speech habits I've picked up.