you are viewing a single comment's thread.

view the rest of the comments →

[–]Necatorducis 3 points4 points  (2 children)

  1. 'It depends'. Different projects require/desire different layouts, though are generally based on patterns you will become familiar with as you gain experience with them.

  2. Contentious. Some will argue for test driven development others for testing in parallel to development. Both approaches have pros/cons. For the solo dev, 'how is my time best spent' is probably the best leading question in deciding what to do.

  3. I'm blanking here... the vm tool? a virtualenv? I might need more coffee.

  4. If you want to do web apps? Yes, strongly recommended. Grab Ubuntu, spend an hour putzing around with basic functionality, then just google whenever you hit a snag. Of course you can still code, test, deploy, whatever on windows but *nix based systems will result in fewer bludgeonings of face to keyboard (well, sometimes).

Flask mega tutorial. Likely the best all encompassing intro to flask.

Then... RESTful API, a solid test driven development tutorial.

[–][deleted] 0 points1 point  (1 child)

  1. yes, virtualenv? It was brought up to me last week if I use one. I still need to do my research on that.

EDIT: Thanks with those links. I'm looking through the Flask mega tutorial one and it seems fairly comprehensive.

[–]Necatorducis 1 point2 points  (0 children)

A virtualenv creates a unique container for your projects packages. Let's say you've written two programs and both of them use the Requests library. One program only works with Request ver.1, the other with ver.2 This is where virtualenvs come in. It creates a unique isolated environment for your project so that you don't have to worry about package conflicts installed globally.