VirtualTam's bookmarks

  1. TL;DR

    • March 12, 2015 - New project creation disabled.
    • August 24, 2015 - The site goes read-only.
    • January 25, 2016 - The project hosting service is closed.
  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. Uses a project or repository's history to plot user contributions, displaying an elegant, colored graph of the file arborescence.

    After running it on quite different projects...

    • Python/Bash CI/Jenkins scripts
    • Qt apps: GoldenDict, Psi+
    • PHP website: Shaarli

    ...watching some vids on teh intartubez:

    It allows to arbitrary spot some interesting implementation aspects (sorted by descending impact):

    • language-dependent trees (oh hai Java packages ^^)
    • framework-dependent trees
    • project-management method (none, Agile, TDD)

    Having a graphical tool also quickly shows:

    • the overall structure of the project (a bit cooler than a simple $ tree, way quicker than loading the project on an IDE)
    • the repartition of files (by extensions)
    • who are the most active contributors
    • what are the most modified files over time
    • who does what: additions, deletions, refactoring

    Some more CI-related matters:

    • are there any tests?
    • what is the source code / test code ratio? (we could expect a project/lib with N modules to have at least N test modules)
    • who initiates / implements / optimizes test code?
  4.  1# setup a transifex virtualenv
     2virtualenv2 VENV; source VENV/bin/activate; pip install transifex-client
     3
     4# global config: ~/.transifexrc
     5# this step can be omitted, as 'tx init' will create the file if it doesn't exist
     6[https://www.transifex.com]
     7username = User
     8token =
     9password = un54f3_p4ssw0rd!
    10hostname = https://www.transifex.com
    11
    12# setup example project
    13mkdir example; cd example
    14tx init
    15tx set --auto-remote https://www.transifex.com/projects/p/my-project/
    16
    17# get the files
    18tx pull -l pt_BR
    19
    20# edit things
    21poedit / linguist-qt4
    22
    23# push to transifex
    24tx push -t
    
  5. A personal project where I aimed to illustrate words found in foreign languages that cannot be Anglicised word for word.

  6. Project Euler 2014-03-27

    Solve challenging math/computer problems!