VirtualTam's bookmarks

  1. Beware! Very cool book dealing with Lisp programming, with plenty of examples

  2. Python's built-in unittest module is quite cool, but a bit limited and way too verbose (read: it's quite not easy to incite developers to write unit tests)

    I'm currently looking for more dev-friendly solutions, the key points being:

    • writing test code should be easy and straight-forward -keep the focus on "what to test" instead of "how to transcribe a process to a test"
    • parallelization! -we, spoiled developers, should make good use of our way-too-many-cores build machines...
    • complete feature set!
      • we don't want to just run tests...
      • coverage reports (find dead/weak/untested code sections)
      • output formatting (JUnit-XML seems to be quite a common format out there)

    There seem to be 3 solutions in Python:

    • stock unittest + project-dependent customizations / test helpers
    • nosetests
    • py.test

    And 2 ways of gettings things done:

    • keeping things stock: no external dependency, project-specific implementation...
    • using a test framework: one more module in your (test) virtualenv, more concise tests, more features (// run, code coverage, etc.)

    Some links:

  3. Given your unittests are in the tests directory:

     1# run a specific test module
     2python -m unittest tests.<module>
     3 
     4# run a specific test suite
     5python -m unittest tests.<module>.<class>
     6 
     7# run a specific test
     8python -m unittest tests.<module>.<class>.<test>
     9 
    10# run tests matching a given pattern
    11python -m unittest discover -s tests -p <pattern>
    
  4. Very cool & detailed tutorial on how to setup Emacs for Python editing, completion & execution.

    https://github.com/jhamrick/emacs

  5. This little gem made my day ;-)

  6. Git is coming to AUR (or, AUR is coming to Git?)

  7. "Every piece of knowledge must have a single, unambiguous, authoritative representation within a system."

    The opposite is WET:

    We
    Edit
    Terribly, Tumultuously, Tempestuously, Tenaciously, Too much, Timidly, Tortuously, Terrifiedly... 
    

    > I think WET also stands for "We Enjoy Typing" // DuncanBayne

  8. code @ https://github.com/scanlime/arduino-lelo-remote

    via OWNI, News, Augmented : Hacke ton vagin - Revue du web