VirtualTam's bookmarks
474 bookmarks found
-
A successful Git branching model
2015-03-02 -
Review of PHP Static Analysis Tools
2015-02-22 -
- https://en.wikipedia.org/wiki/SHA-1
- http://stackoverflow.com/questions/1867191/probability-of-sha1-collisions
- http://en.wikipedia.org/wiki/Birthday_problem
Some thoughts we had while toying with Gerrit, which artificially tracks different commits to group them as "patch sets", by using a Change-Id SHA-1 in the commit message:
-
gitbrute: bruteforce a Git commit SHA-1
2015-02-14 Applied example: https://github.com/bradfitz/deadbeef
-
Practical Common Lisp
2015-02-13 Beware! Very cool book dealing with Lisp programming, with plenty of examples
-
Become a Programmer, Motherfucker
2015-02-13 Programming... Do you speak it?
-
Python unit testing frameworks: Nose, Pytest
2015-02-13 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:
-
Python: run specific unit tests
2015-02-13 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>
-
Flow: a static Javascript typechecker
2015-02-11 -
-
Emacs as a Python IDE
2015-02-07 Very cool & detailed tutorial on how to setup Emacs for Python editing, completion & execution.
-
PHP Sadness
2015-01-16 -
Is Your Son a Computer Hacker?
2015-01-08 This little gem made my day ;-)
-
[aur-dev] AUR 4.0.0 pre-alpha
2015-01-06 Git is coming to AUR (or, AUR is coming to Git?)
-
Cobertura - Jenkins Plugin
2015-01-04 DIsplay code coverage stats
-
DRY Principle: Don't Repeat Yourself
2014-12-17 "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
-
How to solve Git issues...
from https://presentate.com/bobthecow/talks/changing-history
-
code @ https://github.com/scanlime/arduino-lelo-remote
via OWNI, News, Augmented : Hacke ton vagin - Revue du web