VirtualTam's bookmarks

  1. Build Go projects on-the-fly inside throwable containers

    1. Understand user needs
    2. Do ongoing user research
    3. Have a multidisciplinary team
    4. Use agile methods
    5. Iterate and improve frequently
    6. Evaluate tools and systems
    7. Understand security and privacy issues
    8. Make all new source code open
    9. Use open standards and common platforms
    10. Test the end-to-end service
    11. Make a plan for being offline
    12. Make sure users succeed first time
    13. Make the user experience consistent with GOV.UK
    14. Encourage everyone to use the digital service
    15. Collect performance data
    16. Identify performance indicators
    17. Report performance data on the Performance Platform
    18. Test with the minister
  2. (1) If it should exist, it doesn't. (2) If it does exist, it's out of date. (3) Only documentation for useless programs transcends the first two laws.

  3. Implementation for OOP generic objects, starting with 3.5 : )

    See https://docs.python.org/3.5/library/typing.html

  4. Context: replace spaces by dashes in a script-generated HTML file's links

    1awk -F\' 'm = /a href/ { gsub(/ /,'-',$2); print$1'\''$2'\''$3} !m {print $0}'
    
  5. Pro: no need to setup a DNS server to test virtualhosts Con: keep in mind that all "fake" hosts will point to 127.0.0.1!

    1. Use /etc/hosts to declare test hosts / domains / subdomains
    #<ip-address>	<hostname.domain.org>	<hostname>
    127.0.0.1	localhost.localdomain	localhost
    127.0.0.1	host.localdomain	host
    127.0.0.1	sub.host.localdomain	sub.host
    ::1		localhost.localdomain	localhost
    
    1. Allow per-user virtualhost definition in either (depending on your distro)
    • /etc/httpd/conf/httpd.conf
    • /etc/apache2/apache2.conf

    Include /home/albert/.httpd/*.conf

    1. Profit! Create virtualhosts with local hostnames :)
  6. 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:

  7. 2014-11-30

    A follow-up to Mark Pilgrim's http://www.diveintopython.net/

  8. Stalactites, stalagmites, icicles and more cave stuff!