Commits

Kenneth Love committed d7b854a

blah

Comments (0)

Files changed (4)

-==================
-django-party-pack
-==================
+====================
+djangocon-2011-notes
+====================
 
-Combining the Django Tutorial with Sphinx Docs, Django-Coverage, Coverage.py, and some notes on good practices
+Notes from DjangoCon 2011 compiled by Kenneth Love.
+
+With an awesome kickstart from Daniel Greenfield's Django Party Pack.
 
 Installation and documentation is at http://readthedocs.org/docs/django-party-pack/en/latest/
 

confessions_of_joe_developer.txt

-Confessions of Joe Developer
-============================
-
-1. I'm stupid:
-    * Can't figure things out
-        * If I get stuck for more than 30 minutes:
-            * Find libraries that do it for me.
-            * Ask on Twitter for answers.
-            * SO is good, but watch out for trolls.
-            * IRC can be good, again, trolls.
-    * Can't remember things
-        * Documentation makes me look good.
-        * Docstrings are awesome.
-        * Learn you some REStructuredText
-        * Write down even the slide bullets.
-        * Sphinx makes me and my code look good.
-    * Ask the dumbest questions
-
-2. I'm lazy:
-    * Don't want to do anything twice
-        * If I write the same code twice, I stick it in a method.
-        * Then stick the function into a utils module.
-        * Then I put it up on Github so I don't lose it.
-    * Don't want to debug code that worked before
-        * Manually testing code by watching it run is hard...
-        * ... and boring ...
-        * ... and hence is error prone.
-        * Meaning you have to do more work.
-        * **Are you testing enough?**
-            * coverage.py is great
-            * django-coverage runs coverage.py for Django
-            * But you only want to test your own apps. Refer to code on Github for how.
-            * Look at how he does INSTALLED_APPS
-    * Don't want to upload ZIP files per documentation change
-
-3. Don't be smart and lazy
-
-4. Technical Debt
-    * Postponed activities:
-        * Documentation
-            * unshared knowledge
-        * Tests
-        * attending to TODO statements
-        * Code too confusing to be modified easily
-
-A positive trait good tech leads often look for is the ability to ask questions.
-
-http://bit.ly/audreyr-sphinx
-https://github.com/pydanny/django-party-pack/
-
-Q&A
-===
-
-1. Do you try to understand the 3rd party code or isolate it?
-    * Pip & Virtualenv to isolate it.

from_designer_to_djangoer.txt

-From Designer to Django'er in Six Weeks
-=======================================
-
-1. Start out on the right foot:
-    * If you can, spend 100% of your time on your project.
-    * Have a large savings account, low debt.
-    * Make sure you're having fun.
-    * Success can be just launching the app.
-    * Be focused and optimistic before you start.
-
-Cofounders are awesome, but no cofounder is better than the wrong cofounder.
-
-2. Launch as fast as possible:
-    * What can you take out?
-    * Launch tiny bits to keep motivated.
-    * Work on the hard stuff first.
-    * Spent as little time as possible on learning, as much on building.
-    * Launch with bad code (really, it's okay).
-
-3. Have a plan for monetization
-
-4. Don't be forever alone:
-    * Talk to friends.
-    * Don't be prideful; accept help.
-    * NDAs suck.
-    * Surround yourself with good people & resources.
-
-5: Take shortcuts:
-    * Django is plug & play
-    * South, django-registration, django-profiles, sorl-thumbnail, django-debug-toolbar, djangopackages
-    * dotCloud
-    * virtualenv, pip
-
-5.5 Design shortcuts:
-    * themeforest
-    * 99designs (quick logos only)
-    * "The Non-designer's Design Book"
-    * Create a coming-soon page.
-
-Q&A
-===
-
-1. Django/Python rough edges?
-    * Review logic first (when learning).
-    * Had lots of people to ask questions to. Removed most (all?) speed bumps.
-
-2. Why choose Django and stay with it?
-    * Chose Python, really, not just Django.
-    * Django provides for lazy developing :)
-
-3. How did you find customers?
-    * Cold emailing for the vendors.
-    * Blogs and promotion help a lot.
-
-4. How to rein in a designer that likes to design hard-to-build items?
-    * Make him build it!
-    * Pluggables never exactly match.
-
-5. How far did your roadmap go?
-    * Not far at all.
-
-

the_story_and_tech_of_read_the_docs.txt

-The Story and Tech of Read The Docs
-===================================
-
-