[briancary]

Kudos for starting the path to self discovery, aka programming. However, it is tough to go from zero coding experience to being able to pick projects that are fulfilling and worth the money earned.

I would study the following day and night for 60 days straight if I were you:

- HTML (so you can come up with and create designs - even if very basic) - PHP (it is widely available, has a large market, you can prototype other people's ideas easily with it, gives you a decent base to go to other languages with) - CSS (so your designs are at least more efficient by separating presentation from content) - JavaScript (read: jQuery)

Spend a solid two weeks of doing html/css/js, then add PHP into the mix. Add in MySQL after another couple of weeks and then iterate on the whole system for another month. That will give you the confidence to seek out the work that will be worth your time (after 2-3 months of really hard work).

Another point: Knowing how to program is a different job than getting side work/contracts and dealing with customers. Find someone to partner with you if you can - maybe give then 25% or 33% if they are dedicated to helping you manage customer relationships. Dealing with customers takes a lot of time away from actually programming and leads to burning out sooner if you are doing it all.

Lastly, network as much as you can. If you do so effectively, you will meet some people who want to hire you for your skills later down the line (from a few months to 6 months or more away) so its best to get them in the pipeline early and follow up every once in a while.

[pavel_lishin]

I haven't worked with many other languages, but in my experience, most PHP projects are a tangled mess that are hard enough to figure out when you're an expert, much less a novice. I would recommend a language with a better user-base, and one less susceptible to newbies building big projects. I'd wager that given any 100 PHP projects vs any 100 Rails projects, the rails projects would be easier to read and understand.

[eavc]

Does that mean you'd recommend Rails for me based on my criteria?

[Groxx]

I would actually recommend against Rails, unless you have a fair amount of programming experience already. I really like it, and Ruby is a wonderful language, but it's extraordinarily complex. It'll get you from zero to something very very quickly, but the "magic" behind the scenes will inevitably bite you, and the solutions can be difficult to grasp. It's also a very quickly changing framework, so you will have to watch out if you change versions, even fairly minor ones.

If you take your time with it, it can work, and there are a fair number of very good guides for it. But be willing to take the time you need to really understand what's going on.

[pavel_lishin]

I don't have enough experience with Rails, tbh - this is less of a recommendation and more of a warning that you may grow to despite PHP, programming, and life itself if you inherit a bad set of projects.

[eavc]

Thanks for the good response. I'm somewhat surprised that your answer seems to amount to, "All of it."

Would you say there's a way to avoid having customers altogether while only doing part-time work? I'd like to have something closer to an employer.