karyon

9 ms·

61.
by karyon 10y ago
discussion is here: https://news.ycombinator.com/item?id=12011419
62.
by karyon 10y ago
these don't seem to be the correct slides.
63.
by karyon 10y ago
The question of where to draw the line does not come with more telemetry data collected by cars. If you would deploy lots of speed traps everywhere, you'd have a similar situation. Overtaking a slow-moving vehicle does probably not all
64.
by karyon 10y ago
could you expand on in how far this is a problem? i must say i'm glad there's finally no way of talking out of it, if the data says you did it wrong, then you most likely did it wrong and the cops should make you pay money or jail
65.
by karyon 11y ago
> If you look at a commit, there's no "anymore", no other timeframe rather that the commit's; it's either correct or incorrect on it's own. this is true but frankly nothing i ever cared about. I think of com
66.
by karyon 11y ago
> I often don't want to record my development history in the master branch because it's messy. Instead I squash my work into a single cohesive commit personally i rebase my commits into fewer ones so the result is a reasonable
67.
by karyon 11y ago
That notion is false, right, thus I'd rather think "this commit is not correct anymore". Regarding getting ideas how the code was developed, for the commit that is not correct anymore I have a commit message telling me why it
68.
by karyon 11y ago
once more, gitlab does it right and offers a "rebase" button on merge requests along with a "fast-forward merges only" option for repositories. See http://doc.gitlab.com/ee/workflow/rebase_befor
69.
by karyon 11y ago
> git bisect pointing to the merge commit as culprit is exactly what should happen in theory, maybe. in practice, this simply does not help if you are looking at massive merge commits. sometimes, the merge goes wrong even with no conflic
70.
by karyon 11y ago
You lose a whole lot of development history information. You have no chance of finding out why these five lines of code came to be when all your commits touch hundreds or thousands of lines. Maybe the intent of the code should've been
71.
by karyon 11y ago
On my two machines (with SSDs) I regularly find that copying lots of small files is severely slowed down by Windows Defender. It utilizes one core to the max and when disabling it, the copy operation gets a lot faster. I don't know abo