Before I get too far ahead of myself, I think it would be helpful to establish my goals for this experience. I read a great post by Michael Hyatt today called 5 Reasons Why You Should Commit Your Goals to Writing. While the article doesn’t pertain to programming in particular, the main points can be applied to what I’m doing here. In particular, points 2. “Because it will motivate you to take action” and 3. “Because it will provide a filter for other opportunities.” These two points are what I foresee being my biggest obstacles, so if there’s anything I can do to reduce the chances of failure, I’m going to jump on them.
So all that being said, here are the goals I want to have accomplished in 3 months time:
- Complete Michael Hartl’s Ruby on Rails Tutorial
- Using the new knowledge I’ve obtained, build a minimum viable product of 1 of my application ideas
- Launch the MVP to determine if there’s a demand for the product
My goals aren’t crazy extensive at this point, but that’s okay I think—I think I’m taking a step in the right direction now, at least, by just focusing on ONE thing rather than the million others floating around my head.
I’ll revisit these goals again in 90 days.
Just finished working through Chapter 1 of the Rails Tutorial. So far, so good!
We’ve now gone through installation, setting up the development environment, version control, and deployment. There’s a lot to take in, but it hasn’t been overwhelming… so that’s nice.
My thoughts so far:
- Holy commands, Batman! This is my first time using the terminal, so, obviously, it’s a lot all at once. Not too worried though—I’m sure with repetition I won’t have too much trouble.
- Michael’s writing style is really easy to follow—makes flipping back and forth to the terminal super easy.
- Version control seems pretty cool. I haven’t been able to totally wrap my head around it yet, but I can grasp why it will be important later.
- Heroku is RAD. It’s so easy to set up and deploy a new application—and I love that it looks sexy as well. Coming from a designer’s standpoint, this get’s me real jazzed. Also, the names it generates when you create a new app are hilarious and amazing (hence the title of this post.)
Some other thoughts:
- Worked in Starbucks tonight for the first time ever… the WiFi is kinda slow, but I felt really productive and focused—this could get expensive.
- I’m a big fan of listening to music while I work (usually without vocals.) It really helps me get in the zone. The Last of Us for the PS3 has one of the best soundtracks in any game ever, IMO… perfect for getting shit done, whether that’s sniping clickers or committing branches.
Just 2 short days ago, I decided that I was going to learn to code after getting yet another idea for some awesome web app that I would never build. It finally made me realize that before I can unleash that new fancy app, I need to learn to code. No more procrastinating.
Excitedly, I dove into Google, to try to figure out what I was going to attempt to teach myself. With the gentle guidance of the internet, I discovered that Ruby (on Rails) was what all the cool kids were using—and if it’s good enough for Twitter, it’s good enough for me.
Okay, so I have my language… now where do I begin learning it?
Some more Googling brought me to Michael Hartl’s Ruby on Rails Tutorial. Reviews all seemed really positive, and the ebook is free. Sounds good to me!
With a combination of help from the RoR tutorial and installrails.com, I got RVN, Git, Ruby and Rails installed on my system, and successfully generated a new Rails application. Luckily, the notoriously complicated installation process didn’t cause me any grief this time… although, inevitably, it will every time from now on…
I’m now up to chapter 1.3 in the RoR tutorial, so tonight I plan on going through the primer on Git. I’m excited to dive in to finally see what all the hype surrounding it is all about.
I’ve been meaning to do this for a long time, but for some reason I’ve had a hell of a time getting myself to actually do it. Don’t ask me why.
So what is this, you ask? This is my journey into the slightly-terrifying world of web development. In my case, it’s mostly slightly-terrifying because for the longest time I’ve been struggling where I’m sure countless others have struggled as well…
“WHERE DO I START?!”
The answer had only vaguely started forming in the last couple of days, and today it finally just clicked. To what should be no one’s surprise, the answer is blatantly obvious. Countless Google searches and blogs have already been slapping the answer in my face for months…
“JUST EFFING START!”
I have all these fancy app ideas, business ideas, the “next-big-thing” ideas (make sure to note the quotes around that), but so far all that’s come of them are scribbles in my notebook. Then they’re set aside while I await the mythical developer-knight-in-shining-armour to ride in and sweep me off my feet to ride into the sunset.
Well, you know what? It’s not going to happen, Kev-o. Time to take control of your own destiny. Seize the day, or something.