jekyll on S3 is a pretty killer combo for a cheap blog that scales infinitely and automatically. You'll probably like it, especially since you're a ruby guy.
Yes, it was the hardest/easiest thing to learn I've ever experienced. Sometimes I was jumping out of my chair and then other times throwing things against the wall.
Plenty of times I wanted to just give up.. during those points; I'd step back and go take a break, go for a walk, do something.. other than think.
Programming is hard because it's full-time blitz mode thinking. I felt the front part of my brain (is that where all the programming juice is held?) hurt often in the beginning.
Do you have an actual product you want to work on?
> Do you have an actual product you want to work on?
Having a real product to build, even if its just to help yourself and not the world is key. It gets you out of the tutorials (which you need to do) and into finding out the main problems you have to solve to get something live.
And once you've got something live, you've built your mental framework that you can "hang" everything else you learn on.
Couldn't agree more. The urge and desire to start learning was constantly squashed by the daunting task at hand. Once my ideas began to coalesce into something coherent, the passion and interest superseded the difficulty or fear I'd never "get it".
You're 100% right about having something specific to work on. Going through tutorials doen't commit you to anything, and hence never compels you to keep going when things get tough.
The place where I stopped with Michael Hartl's tutorial was on the authentication chapter. I found that whole salt thing completely confusing. Later, I heard about Devise (and others), I thought—Ok, so I'll never actually need to know how to do this—but that's not true. Right on the Github page it says that Devise is complicated and not for beginners. In fact, I'm pretty sure it links back to Michael Hartl's article as an 'easy' way to implement authentication!
That's when I packed it in right there!
Thanks for the advice and for taking the time to write this stuff down. Your freelance site looks amazing for 12 weeks work. Great stuff.
I'd like to add to this simply because I had a very similar experience but with PHP.
There were definitely times when I was extremely frustrated and wanted to give up. There were a couple times when I had 5+ hour sessions and got nowhere, then I'd come back the next day to realize it was a stupid mistake.
One thing I can't stress enough (and James has been saying it too), if you don't have a final site, product, or app in mind you're probably going to get bored and walk away for good. I tried to learn C++ a while back and gave up because I didn't have anything in mind and the boring repetitive exercises lead to nothing in the end.
"then I'd come back the next day to realize it was a stupid" I couldn't agree with that more!! Come back and you find out all you had to do was restart the 'Rails Server' or simply mis-spelled something.
Thank you! Without getting too much into technics in the beginning, and getting the person to get something up to feel accomplished, gain confidence.
I think that's what gets most people. That initial learning curve takes a lot reassurance that they can do it; but if they hit a wall and it takes more than 7-8 hours to get around it, a lot just quit all together.
By far, the most thorough and best written resource I used was the Rails Tutorial from Michael Hartl.
During the initial learning phase I wasn't as enthralled because who cares what $this->someFunction($variable) means? I'd say I put in around an hour per day for the first month and then once I got the hang of it, probably 2-4 hours per day after that. I made sure to take off programming at least one day per week so I wouldn't get burned out considering I was working full time too.
So, I'd estimate around 150-160 hours. I should've kept track. I plan on learning ruby later on this year and I'll be sure to keep a record of that.
James, this is in response to what you said to my last comment. The reply button wasn't showing.
Anyway, that 150-160 hours was to the point where I was comfortable enough to sit down and code away. I'm still working on the system and I'm still learning a lot. I'd also like to become a lot better with css/jquery. I know the basics and not much more. A guy on my team is a front end whiz so I don't have to worry about cramming that into my head right now.
great question. I was a web designer working with only html/css. I had no clue what an MVC was before I got told the best route is to learn Rails by Josh.
I'll definitely be making a blog post about the learning Rails aspect as it was requested alot today. If you want, I'd suggest to subscribe that way it'll email you when that post is created.
The ability to tell the person who posted the project that their project will be a piece of crap if they try to get something done for that much and why.
Also, those spray and pray 'generic' bids that many companies on Elance and oDesk can't get away with that. So they actually have to display some sort brain power and ability to the project poster.
The ability for the project poster not be embarded by 40-50 bids all at the same time and not having a clue about their work ethic/communication/etc. and going purely off of reviews and botched portfolios.
