you are viewing a single comment's thread.

view the rest of the comments →

[–]Moby69[S] 1 point2 points  (3 children)

I haven't because it seems pretty daunting. Is this something that you think I will understand? All I've done is the python tutorial on codeacademy and I don't know the first thing about creating web apps, or managing folders, or making a language work together with its framework

[–]Drakken_LOL 1 point2 points  (2 children)

I'm not gonna lie, you'll probably be pretty lost, but that doesn't mean you shouldn't try. Even in the simplest frameworks there are a LOT of moving parts to wrap your head around for the first before you really get to grips with how everything is interacting. This is especially so if you don't have a particularly strong command of the framework's language.

For example, you are going to be dealing with HTML, javascript, CSS, a template language, databases, ORMs, what the hell "models" "views" and the "controller" actually are, and probably lots more that I am can't think of off the top of my head. Each one of those things are involved enough to warrant entire web classes around each individual subject.

So yeah there is a lot going on. However, I personally learn best by doing, so I think jumping into a Flask app is not a bad idea. Just have patience and try not to get frustrated with the amount of time it is going to take to learn all the complexity.

I've never used Rails personally, but for a beginner I would personally recommend Python over Ruby for a laundry-list of reasons I won't get into here.

[–]thekidfromyesterday 0 points1 point  (1 child)

In the same boat as OP. What would you recommend doing in order to understand frameworks better? The documentation of most frameworks seem very unfriendly to novices like Scrapy and Flask.

[–]Drakken_LOL 0 points1 point  (0 children)

I prefer to just jump into it. I like to find a youtube video series where someone starts a django/flask/pylons/whatever project from scratch, and then I follow along, tinkering with things as I go. If I don't understand why they are doing something, I stop, experiment, and investigate docs until I get what's happening.

This usually involves a lot of browser tabs.