sye19

Completely agree. I tried to learn HTML/CSS first, then Python, Ruby, then Rails. Needless to say, I didn't make any progress and was no closer to building out anything on my own.

It's an interesting balance between architecting an entire technology web app and understanding a programming language on a meta level. Most people learn from the ground up - i.e. syntax first, then simple commands..etc. No one starts by building the practical stuff and getting it to work before understanding the details.

I finally built an online food ordering site only after sitting down...and building an online food ordering site. I didn't try to learn Ruby, or Python, or Javascript. I just brute forced my way to getting a functional app. I googled a lot, trolled stackoverflow, debugged errors, nagged people for help, and ended up hacking together a Rails app.

Learning to build apps is different than learning to code. So why are we still learning it the same way?

- Susie

Founder at https://baserails.com

So I'm one of those "websites coming out of nowhere" that teaches people to code web projects in Rails (baserails.com). I chose to use a video screencast format because it's the easiest way for people to watch what you're physically doing on the computer screen and then follow along, something that's difficult to convey with just written text and images.

Are you looking for more in-depth content on syntax/framework/theory? Or just more curated written tutorials that's mobile friendly?

To the girls of Hacker News: I am a female founder who codes. Here's a blog post I wrote reflecting on PG's essay (guess I had too much to say for the comments section):

http://susieye.com/2014/01/20/to-the-girls-of-hackernews-i-a...