This article is now published on my website: Prefer Subshells for Context.
Michael F. Lamb datagrok
datagrok
/ gist:2199506
Last active
April 8, 2023 17:36
Virtualenv's `bin/activate` is Doing It Wrong
datagrok
/ git-branch-simplify.md
Last active
April 16, 2024 17:26
How to simplify the graph produced by git log --graph
I will maybe someday get around to dusting off my C and making these changes myself unless someone else does it first.
Imagine a long-running development branch periodically merges from master. The
git log --graph --all --topo-order is not as simple as it could be, as of git version 1.7.10.4.
It doesn't seem like a big deal in this example, but when you're trying to follow the history trails in ASCII and you've got several different branches displayed at once, it gets difficult quickly.
datagrok
/ git-serve.md
Last active
April 21, 2023 07:33
How to easily launch a temporary one-off git server from any local repository, to enable a peer-to-peer git workflow.
This article is now published on my website: A one-off git repo server.
datagrok
/ LICENSE.AGPL-3.0.md
Last active
December 30, 2015 23:49
Various GNU Licenses (GPLv3, AGPLv3, LGPLv3) converted to Markdown format.
Version 3, 19 November 2007
Copyright © 2007 Free Software Foundation, Inc. http://fsf.org/
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
The article previously hosted here is now published on my website: My ErgoDox Keyboard.
From a comment on StackOverflow:
Vendoring is the moving of all 3rd party items such as plugins, gems and even rails into the /vendor directory. This is one method for ensuring that all files are deployed to the production server the same as the dev environment.
The activity described above, on its own, is fine. It merely describes the deployment location for various resources in an application.
Python has a built-in variable __debug__ which is set to True when python is called without -O (optimize). The -O flag disables all assertion code.
This seems at first glance like a very easy and clean construct to rely on when coding in development versus production: in development, don't use -O, defensively litter your code with type- and sanity-checking asserts. Perform development-only debugging by testing __debug__ beforehand.
When in production, run all code is run with -O which disables asserts (speeding execution) and sets __debug__ to False.
datagrok
/ AGPL3-modifications.md
Last active
January 14, 2019 07:43
Some questions and answers about various Free Software licenses.
This article previously hosted here is now published on my website: AGPLv3 affects only derivatives?
datagrok
/ if_i_ran_the_company.md
Last active
January 14, 2019 07:36
If I ran a company, what would it look like?
The article previously hosted at this location is now published on my website: If I Ran The Company.
The scripts previously contained in this gist have moved to datagrok/modular-git-hooks/hooks.
OlderNewer