104 karma · joined February 22, 2007
Here's the money quote:
"The best advice I can offer: stop taking advice from articles like this!"
http://prework.flatironschool.com/web-development/
It's ruby specific, but what you learn in terms of html, css, and git can be ported if you decide to use a different backend language later down the road.
Then just start building things - that when you'll start to really learn.
As far as languages to learn, I think Go, Python, and JavaScript should lead the pack.
Do this after working through Learn Ruby the Hard Way.
Mr. Neighborly's Humble Little Ruby Book is also a great intro to the language - http://humblelittlerubybook.com/book/html/index.html
First and foremost, you are the best resource for learning Ruby. Lean by doing.
1) Work through http://ruby.learncodethehardway.org/book/ then work through it again.
2) Then pick up David A. Black's The Well Grounded Rubyist. Read it to fill in the blanks, then read it again to pick up the tidbits you missed the first go around.
3) Find other people. Look for guidance. Look for a mentor. Look for a users group (ruby brigade) in your area where you can find others to ask questions and advice on the topics that stump you the most.
Don't treat this opportunity as in interview. Be genuinely interested in his life, his story, and his company. If you show interest, he'll open up. Ask the questions you have based on the current context of the conversation. Everyone has a story to tell, all you have to do is be inquisitive.
You may just end up with a friend and mentor.
http://www.amazon.com/The-4-Hour-Workweek-Anywhere-Expanded/...
Check out Net10. You can get an unlimited plan for $50 for a smartphone, 750 minutes for $25/mo. and 200 minutes for $15/mo. The 200 minute plan has carry over minutes. Your net total would be $105, and ~$115 by the time you include sales tax. Granted, you still have to buy the phones.
You could also look at Walmart's family plan. http://www.walmart.com/cp/Family-Mobile/1076544 That would get you down to $150 for the whole family and it's powered by T-Mobile.
FYI, I'm not offering this simply as a suggestion. I did this back in 2009. I was looking to move away from Sprint (poor coverage where I moved to) to a regional carrier. They wanted $60 per live for activation. I was told they'd only charge for one but I ended up still getting billed for all three. They wouldn't honor the discount the sales person offered me saying the offer wasn't approved by a manager.
Fed up with the state of wireless companies at the time, I originally moved to Tracfone and later to Net10 when Net10 came out with monthly plans (both owned by the same company). Only this past August did I finally upgrade to Android. While my phone is no frills (800 MHz processor and 3.2 pixel camera), it keeps my calendar and contacts in sync, which makes life easier.
When we learn, we learn by applying new material to what we already know. Hence foundations and context. When you read, especially something like a book on programming, you're not going to absorb it all. Also, programming books shouldn't be treated as one and done reading. Each time you read, I guarantee something will pop out based on previously acquired knowledge.
The art of building web applications today, in itself, is much more complex than it was 10 years ago - mostly due to the every growing selection of tools that make it easier for experienced developers to build web applications. This in turn can make web development seem daunting.
Personally, when I started learning Rails, I had a foundation of working with rudimentary frameworks in other languages. When I discovered Rails, it did quiet a bit of what those other frameworks accomplished and then some. Then it took it further and pushed the envelope (i.e. REST support for urls and routing, more recently including CoffeeScript and the Asset Pipeline).
While there's a ton of learning resources out there for learning Rails, it can be really hard to put them together and figure out what in what order you need to learn new concepts.
That being said, I think The Flatiron School did an excellent job getting together a list of learning resources: http://prework.flatironschool.com/ - Just a heads up that it recommends CodeSchool and Tree house which are subscription services. If you're serious about learning, I'd consider the subscription cost to be a small investment.
The one resource that Flatiron Prework didn't mention is the Rails Tuturial: http://ruby.railstutorial.org/ruby-on-rails-tutorial-book
If you really want to dive into ruby, I'd recommend The Well Ground Rubyist by David Black.
My favorites from this site are as follows: http://eloquentjavascript.net/contents.html http://bonsaiden.github.com/JavaScript-Garden/ http://www.addyosmani.com/resources/essentialjsdesignpattern... http://jstherightway.com/
Mozilla has excellent JavaScript material: https://developer.mozilla.org/en-US/docs/JavaScript/Guide https://developer.mozilla.org/en-US/docs/JavaScript/Referenc...
As far as print goes, you'll want these books in your reading list:
JavaScript: The Good Parts by Douglas Crockford Secrets of the JavaScript Ninga by John Resig
Never stop meeting people. Always be learning. If you read Hart's book and it doesn't stick. Do it again. Once you're done with it a 2nd time, then go over to CodeSchool.com and work through Rails for Zombies 2 ($20/mo.).
Good Luck!
That being said, I dropped out after three years. I'm not saying you should do the same, but at the time my heart was just not in it.
Nothing says you have to major in Computer Science. Some of the best developers I've worked with majored in something else: English, History, Accounting, Psychology, Music, etc. They were great because they were passionate, eager to learn, and put what they had learned into practice. Granted, these developers were building web applications, which typically are written in highly abstracted languages. Depending on what type of development you want to do, a Computer Science degree may not be necessary. Besides, no matter what type of development you choose, you'll be learning for the rest of your life.
My suggestion is for you to talk to you CS advisors and also talk to advisors for other majors you might be interested in and then make a decision.
Think about cars for a minute. Don't they all look and function the same? Where's the steering wheel? Where's the radio? Where's the motor? Gas pedal? Brake pedal? Seat adjusters? Cup holders? A/C and heat controls? Doors?
Most cars are pretty much the same. The differentiation is in the paint colors offered, the design of the body, wheels, and rims. The visual aspects, per se.
You see, the same thing could be said for start up sites. Everything is where you expect it to be. What's different are the logos and color schemes used.
I use Jira with the Greenhopper plugin, but that's probably heavy for what you're looking for. There's a ton that goes on behind the scenes with it and you can spend countless hours tinkering with it. The key selling point is that you can create custom workflows for specific client and project needs.
If you want something light, take a look at SmartQ (http://www.getsmartq.com/) or Trello (https://trello.com/).
That being said, I'll address what it's like after marriage.
If you're like me, you probably view hacking as a form of 1) entertainment and 2) continuous self education.
Make sure his/her needs are being met. Eat dinner together, every night. Set aside (at least) one evening for him/her each week. Do something fun as least one weekend a month.
Don't sacrifice his/her time for hacking. Do look at setting aside other activities that aren't really important if hacking is more important to you (i.e. golf, playing video games, watching tv, Skyrim, Minecraft, etc.).
Keep communication open. Let him/her know what you're working on as well as why it's important. Use him/her as a sounding board for your ideas. It keeps him/her involved and informed. Also, focus on point #2 above.
More than likely, he/she will have times that he/she likes to read, watch tv, or go out with friends. You'll find that those times are also valuable for hacking. When you do hack, try to be in the same room and sitting on the couch next to him/her, rather than being down the hall, away at a coffee shop or somewhere else.
To recap: 1) make sure his/her needs are being met, 2) don't be selfish with your hacking time, 3) always keep communication open, 4) be visible.
Good luck!