VirtualTam's bookmarks
39 bookmarks found
-
- https://www.debian.org/doc/manuals/maint-guide/build.en.html
- https://salsa.debian.org/nginx-team/nginx
- https://www.debian.org/doc/debian-policy/#document-ch-controlfields
- https://www.debian.org/doc/debian-policy/#document-ch-relationships
- https://unix.stackexchange.com/questions/333603/debian-control-file-provides-does-not-satisfy-dependency
- https://github.com/JayH5/nginx-modules
-
Administration
- https://docs.djangoproject.com/en/2.0/ref/contrib/admin/
- https://docs.djangoproject.com/en/2.0/ref/contrib/admin/admindocs/
Models and Querysets
- https://docs.djangoproject.com/en/2.0/topics/db/models/
- https://docs.djangoproject.com/en/2.0/ref/models/instances/
- https://docs.djangoproject.com/en/2.0/ref/models/fields/
- https://docs.djangoproject.com/en/2.0/topics/db/aggregation/
Static files
User management
- https://docs.djangoproject.com/en/2.0/topics/auth/default/
- https://docs.djangoproject.com/en/2.0/topics/auth/customizing/
- https://docs.djangoproject.com/en/2.0/ref/contrib/auth/
- https://docs.djangoproject.com/en/2.0/ref/settings/#login-redirect-url
URL dispatcher
-
Vim and Django
2018-02-10 - https://code.djangoproject.com/wiki/UsingVimWithDjango
- http://www.vim.org/scripts/script.php?script_id=1487
- https://github.com/jmcomets/vim-pony/
- https://github.com/vim-scripts/django.vim
- https://github.com/tweekmonster/django-plus.vim
- https://stackoverflow.com/questions/4027961/describe-your-customized-vim-editor-for-python-django-development
- https://www.reddit.com/r/vim/comments/2zkxip/some_good_vimrcs_blog_posts_about_using_vim_with/
-
I've inherited 200K lines of spaghetti code -- what now? - Software Engineering Stack Exchange
2017-10-16 - https://softwareengineering.stackexchange.com/questions/6395/how-do-you-dive-into-large-code-bases
- https://softwareengineering.stackexchange.com/questions/6268/when-is-a-big-rewrite-the-answer
- https://www.red-gate.com/blog/software-development/legacy-code
- https://craftedsw.blogspot.ro/2011/06/change-in-attitude-legacy-code.html
- https://www.joelonsoftware.com/2000/04/06/things-you-should-never-do-part-i/
- https://www.reddit.com/r/PHP/comments/7blo1b/refactoring_huge_ci_2_application/
- https://leanpub.com/mlaphp
- https://softwareengineering.stackexchange.com/questions/184227/migrating-legacy-procedural-code-to-mvc-without-rewriting/184241
- https://www.reddit.com/r/PHP/comments/ax88ot/i_am_taking_on_a_custom_crappy_php_application/
-
- https://github.com/qmk/qmk_firmware
- https://colemak.com/
- https://www.scorpia.co.uk/2016/03/17/using-usb-type-c-on-hobyist-projects/
- http://www.embedded.com/electronics-blogs/benson-s-blocks/4442214/USB-Type-C-in-a-Micro-B-world
- https://sgotti.me/post/atreus-keyboard-build-log/
- https://atreus.technomancy.us/
-
-
hgrc - Mercurial configuration
2016-01-14 -
D'Addario String Tension Pro
2015-08-31 Tension / gauge calculator to design custom string sets
Related threads:
- http://www.talkingbass.net/flappy-b-strings-tight-d-strings-and-the-switch-to-progressive-tension/
- http://www.mcdonaldstrings.com/stringxxiii.html (limited support for open/drop tunings, no 7+ string support, no bass support)
-
Creating a custom git flow visualization
2015-03-02 -
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:
-
Git - Tips and Tricks
2014-05-15 Bash completion & custom aliases
-
Bad Tourist Behavior - Business Insider
2014-04-09 UK - Don't invite someone to your home: "Unless you know them very very well."