51–60 of 83 posts
Congrats on the launch. I think I speak for everyone on HN when I say, you're going about this the right way: learn enough to build applications for yourself, whether or not you're going to be a code committer over the long term. Can I give you some quick advice? Don't take this the wrong way: Rails makes it easy to learn enough to be dangerous in 12 weeks. Some quick hits on obvious things you should look over in yo…
Please, designers, stop doing this (and stop doing menu bars with the same behavior). There's not much on your site that is important enough that I need it to follow me everywhere.
Did you go about this project doing TDD/BDD?
Earlier quoted context omitted.
You mentioned Heroku in your post. Why did you decide not to host there?
Good question. The wordpress blog (webstartup.me) is on a cheap server. Freelancify is hosted on Heroku.
The other thing I want to add is how much 'else' I learned while running through Michael Hartl's tutorial. Despite many years making websites, I really had no clue about basic http methods — get, put, post, etc — and in fact, I didn't even realize what they were. The other huge, huge thing for me was finally figuring out what REST is all about. Basically, the web runs on those few basic http methods, and using the RE…
Earlier quoted context omitted.
Do you think it's a left brain, right brain sort of thing? I mean what controls someone's ability to draw better than others? I've noticed usually the better someone can draw on paper, their web design reflects the same.
I think it has a lot more to do with memorization of all the little quirks on what works on what browser and what doesn't. With languages like C#/Ruby/PHP/JavaScript, I find that I can soak up that knowledge better than HTML/CSS, because I find it consistent and organized (...not too sure about PHP's quirky API naming conventions). For CSS, it just seems like there is a myriad of tricks you gain through out the years…
Congrats on the launch. I think I speak for everyone on HN when I say, you're going about this the right way: learn enough to build applications for yourself, whether or not you're going to be a code committer over the long term. Can I give you some quick advice? Don't take this the wrong way: Rails makes it easy to learn enough to be dangerous in 12 weeks. Some quick hits on obvious things you should look over in yo…
Any advice for getting started for someone without a Mac? I remember once trying to learn and immediately stalling out during setup (lame, I know). I have WinXP & Ubuntu, and would like to take a stab at this again no matter how stupid I feel about not even being to able to install the damn stuff to start with.
Use Mac Leopard, and don't switch from 32 bit to 64 bit - you're gonna get a massive headache getting all those gems you need to install. Also if you're considering doing anything to do with image processing, consider NOT using Mac. Installing stuff like PIL and ImageMagick can be hell
Any advice for getting started for someone without a Mac? I remember once trying to learn and immediately stalling out during setup (lame, I know). I have WinXP & Ubuntu, and would like to take a stab at this again no matter how stupid I feel about not even being to able to install the damn stuff to start with.
I don't want to sound blunt, but I found the installation process of ruby/python/git on windows to be more painful than necessary. (Last time I tried) It might make sense to try it on Ubuntu as it should be very similar to a mac environment. Good Luck!
Ruby is a bit more understandable, if you don't get DevKit (or if DevKit can't compile something) working with gems can be frustrating. And setting up Git on Windows with an SSH key has been awful in the past.
RailsInstaller takes a lot of the pain out of setup, though.