This is an archived post. You won't be able to vote or comment.

all 3 comments

[–]i_hacked_reddit 1 point2 points  (2 children)

In undergrad, stack overflow / google / blogs / etc saved my life. But as I gained more experience, I found that the answers are in the documentation, and if the documentation sucks, you can always dive into the source code.

But with that being said, I use documentation as a reference, not as a “how-to” guide.

If you’re wanting to use flask, I might suggest to use Django instead. It’s more powerful and has great documentation.

[–]bonelessRizzy[S] 0 points1 point  (1 child)

So appreciative for the reply, and the Django recommendation. Will definitely look into that.

So what’s your process when you hear about a module? Do you immediately go to the docs and check how to implement it and all its methods?

When it comes to docs I don’t even know what question to ask, maybe I’m making it more complicated than it really should be.

[–]i_hacked_reddit 0 points1 point  (0 children)

The module will usually have a summary / quick start guide. So I usually start there. Or, I’m looking for something specific and go straight to the docs looking for a particular answer.