Superfud

9 ms·

1.
by Superfud 27d ago
"Oh no, I hit a timeout" -> "I've increased the timeout and added a retry" -> "Oh no."
2.
by Superfud 2mo ago
Batteries fortunately do not destroy the raw materials they are made from. So eventually we can stop mining new raw materials once we have built enough batteries. In addition, batteries for cars live a surprising long time - and can be used
3.
by Superfud 6mo ago
ddrescue can read from /dev/urandom and write to any device. This can come in handy when you have a device with bad blocks but still would like to "shred" all the still writable parts of.
4.
by Superfud 2y ago
A change ID is stable over time as you tweak the message of the change or the files edited by the change. Each of these changes become a new immutable git commit under the hood. The fact that change ID is stable is very convenient for human
5.
by Superfud 2y ago
Initial empty commit with just a message you can create with "git commit --allow-empty -m'Early commit message" Then when you have the changes lined up you --amend that same commit.
6.
by Superfud 2y ago
This is probably the very first thing you tried, but maybe don't cut the nail quite so short? Recommend upgrading to sharp and precise nail cutters as they make it easier to control exact nail length.
7.
by Superfud 2y ago
For PostgreSQL, the manual is extremely well written, and is warmly recommended reading. That should give you a robust foundation.
8.
by Superfud 4y ago
Hitting enter two times gets you out of code blocks. It's the only consistent method I have found.
9.
by Superfud 4y ago
Readwise allows you to “recover” your streak if you miss a day for whatever reason. I’m sure it is for the exact reason you cite here.
10.
by Superfud 15y ago
Sounds like a simple solution which gets the job done. Using whiskey_disk would reduce your typing by a bit (repeatability is nice for things done all the time), but if you don't have any post-commit tasks you have to run on each deploy, st
11.
by Superfud 15y ago
Good question! The main benefit is you deploy directly from your git-server to your production server, instead of uploading from your own computer. This means a lot faster deploys, especially when your deployments are large or your internet
12.
Deploy a private Github repository with whiskey_disk(object.io)
19 points by Superfud 15y ago|10 comments
13.
Modernize Your Git Workflow(object.io)
3 points by Superfud 15y ago|0 comments
14.
The sneakernet in git - trivial backup of personal repositories(object.io)
36 points by Superfud 16y ago|4 comments
15.
Identify what your Ruby process is doing(object.io)
1 points by Superfud 16y ago|0 comments
16.
Ack Effortlessly search your codebase(object.io)
2 points by Superfud 16y ago|0 comments
17.
Chop – efficiently dispense with the current git branch(object.io)
1 points by Superfud 16y ago|0 comments
18.
Quick data import and linking in Rails(object.io)
1 points by Superfud 16y ago|0 comments
19.
Easy local code-review with git(object.io)
2 points by Superfud 16y ago|0 comments
20.
Simple git workflow with hack and ship(object.io)
29 points by Superfud 16y ago|8 comments