VirtualTam's bookmarks

  1. Literate DevOps 2016-03-29

    """ Instead of opening up a terminal to my virtual machine, I pop into Emacs and load this sprint’s /note file/1, create a new header, and enter the shell and ruby commands in this text file.

    What good is this? Unlike a traditional terminal, this allows me to log, document and execute each command.

    As an old bear with very little brains, my prose can explain the background and purpose of each command. Clicking the hyperlink refreshes my memory of previous discoveries. A keychord executes the code block… """

  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. Change install dir:

    • get the EarSketch installer,
    • launch it, install Reaper and EarSketch to the default location => C:\Program Files{EarSketch, REAPER (x64)},
    • install the other softs (Python 2.7 and its extensions, Kommodo) where they belong,
    • move the REAPER (x64) folder to a new location,
    • edit the registry value [HKEY\LOCAL MACHINE\SOFTWARE\REAPER] to reflect this new location,
    • edit the Actions menu file to reflect the new Plugins folder locations [%appdata%\REAPER\reaper-kb.ini],
    • (restart Reaper),
    • clean the cache.