mkiwala

5 ms·

1.
by mkiwala 4y ago
Funny how bottles don’t break as much when they’re worth money intact
2.
by mkiwala 7y ago
> “This replacement effort exponentially increased message storage capacity and operator response times for critical nuclear command and control message receipt and processing.” Glad to know operator response times have exponentially inc
3.
by mkiwala 8y ago
This is the second denied passport story I’ve seen recently. The first one was here: https://www.washingtonpost.com/amphtml/world/the_americas/us...
4.
by mkiwala 9y ago
> that rebasing as part of a workflow was part lack of discipline when creating commits Because we have rebase, there is not as much need for discipline when creating commits, because you can change change them later. > and part desir
5.
by mkiwala 9y ago
What you are describing is not what the author of the article is advocating, which is `git merge --squash`. What you've described -- committing often and later combining commits together into cohesive units that don't break tests
6.
by mkiwala 9y ago
I think my way of working is not too dissimilar from yours. I definitely use plenty of `rebase -i` in my workflow.
7.
by mkiwala 9y ago
I don't think I will ever understand people's fascination with squashing feature branches. Develop on a branch, yes; rebase the branch instead of merging in master, sure. But why delete the history by squashing, when a merge into
8.
by mkiwala 11y ago
Except for cryptocurrency.
9.
by mkiwala 11y ago
http://quorumlanguage.com/
10.
by mkiwala 11y ago
I'm using coeros to operate a deis cluster. We deploy to our own data center using openstack.
11.
by mkiwala 12y ago
Better yet, use `set editing-mode vi' in your .inputrc so that bash and other readline enabled utilities default to vi-style bindings.
12.
by mkiwala 13y ago
The sqlite3 .import command does not handle quoted csv values. "Doe, John", 1234 Pine St, Springfield That would be imported as 4 fields, not 3.