It is very weird to randomly click on some post on HN and get this. If you're me. http://begriffs.com/posts/2015-04-20-going-write-only.html
git-annex is featured on the 10 Years of Git timeline https://www.atlassian.com/git/articles/10-years-of-git/
next 7drl design
Much as I came up with the whole design document for Scroll late one night, I've just written down a pretty complete design for "GIt the Explorer".
In which you play Git, a level 1 Explorer of a git repository. Any git repository.
Your goal: To travel back in time to the Big Commit that started it all.
[snip 79 lines]
(Does this mean the game could not only play its own repositoriy, but even play its own save games as levels in itself? :)
Other than a rather tricky level layout, this seems simpler and easier than Scroll, so doable in a week. It still seems insane to do 7drl again next year, but one of these 7drl's ...
Have not been reading a lot of fiction the past year or two, but I certainly am this week. Read just 8 novels in Jan-Mar, but already 5 in April, and 2 in the past 2 days.
0x27 in programmer years means
... I can mostly sort of understand this: https://www.youtube.com/watch?v=_KioQRICpmo
... And hey, I remember that guy, we had lunch in Canberra once and the whole table of LCA attendees happened to know Haskell.
... And, it seems, I wake up at 6 am to watch lectures like this now?
Pleased that I helped the curl developers fix its behavior when downloading a 0-byte url. Before now, it "successfully" didn't create a file at all in this situation. https://github.com/bagder/curl/issues/183
They went from "It certainly works like this on purpose, it is not a mistake" to "I have merged the fix for this issue". All it took in this case was gently pointing out a better approach than the one they'd gotten stuck on.
Good bug reporting is such an art. Mine aren't always so good, or successful. Sometimes just funny is the way to go https://github.com/yamadapc/haskell-ascii-progress/issues/13
Stephen Michael Kellat shared this.“Connaisseur” is the actual word, thought I think most of the English-speaking world will settle for “connoisseur”, in what I think is a fork from old French, before it settled on the current form.
Otherwise, I completely agree with this issue. I want to see a full progress bar!
X11R5 likes this.
mkdir private; enable-encryption private
"Encryption in ext4 is a per-directory-tree affair." http://lwn.net/SubscriberLink/639427/309eb368f189617c/ OH YEAH
(Although exposure of number of encrypted files and sizes may limit use cases a tad.)
I hope this slays encfs; tired of getting bug reports related to its implementation warts.
Very hard to think an encryption scheme that shares so much metadata is worth using. :-/
If the directory contents were entirely hidden I'd say great. But leaking file sizes and permissions and more? That is not a good setup for much.
If all you want is to encrypt one file, OK. But the directory-level benefits are hard to support. Too much metadata undercuts everything.
Kete Foy likes this.
https://news.ycombinator.com/item?id=9343021 well that's interestingi couldn't help but think of git-annex as well. i do like how they have a very targeted feature set, it's an easy world they live in where no one will think "cool, the dropbox killer!" :) but it would have been nice to see them reach out before launching the product...
Lars Wirzenius likes this.
Why I should probably not be let near a bug tracker. https://github.com/yamadapc/haskell-ascii-progress/issues
from the features to turn off dept.
til: git expands wildcards. Because one expansion of wildcards, by the shell, is not enough?
Wish I could understand why, when someone is reporting a really strange problem, I can get 100% puzzled by it and stuck. But then, if I manage to reproduce the same problem, I can always quickly figure out the root cause and fix it.
It's often a night and day difference, I can go round and round with a user for hours trying to understand what they did, but once I reproduce the problem, I can have it fixed in minutes.
It's something to do with bandwidth, and limited information, and communication difficulties, and confirmation bias, and.. I don't know what all.
Being able to diagnose and fix reproducible problems is a good skill. Being able to coax reproducible test cases out of users is a good skill. But I feel there's something here I could be better at.
(Users could also be a lot better at reporting bugs and reliably communicating of course..)
Olivier Berger likes this.Show all 6 replies
Sometimes I barely go around the debugging loop at all, once I have the problem reproduced. I find myself immediately forming a hypothesis, and testing it, and I was right on my first try, and now I understand the problem.
Maybe part of it is that, if I've managed to reproduce the problem, I've collapsed the solution space significantly, just by observing it in a controlled, known situation.
It might have something also to do with perception as well. Words on a screen are words on a screen, but if I had to interact with the system to get the error message to come up, I might perceive it differently than if the error message was shown to me by someone else.it's all about reproducability. "it's broken", "it doesn't work" emails are so infuriating for that reason: "i'd love to help you, but i just *can't*!" it's not as if we're going to go around the ship pulling random ropes and punching holes through the hull to fix bugs by brute force...
i mean that can be part of a test suite, but that's a different thing.
also: TDD. i wish i discovered unit tests when i started programming (well, to be fair, they barely existed at all). i feel that a lot of the bugs i find are just some stupid mistakes i made that could have been caught with proper tests. it also helps clever devs (who, yes, even then, can't always file proper bug reports) help you reproduce issues properly.
but yeah, sitting next to the person is awesome. the folks at Freeswitch often just call people on the phone or invite them in a phone conference as compromise. :)+1 for TDD reducing the frequency and scope of these kinds of things for me, at least with the non-functional languages I've worked with (as @joeyh has heard me opine previously). Maybe the thing worth getting better at is asking folks who can't report a bug very precisely to make an appointment to show you. You'd have to go into town, and they'd have to prepare to reproduce the bug.
Just to be clear, this is MRIs for fun and research, not for medical reasons.