chrishill89

6 ms·

1.
by chrishill89 4d ago
I learned about proofreaders marks when my master’s advisor would print out my draft and mark it up with a pen.
2.
by chrishill89 3mo ago
> After reading about the default mode network here a few times recently, I think missing out on all that critical "daydreaming" time is a bigger problem. Part of the reason why I listen to music and scroll my phone is to get s
3.
by chrishill89 3mo ago
I write mostly for myself. That's a trite I guess observation considering that I happen to write a lot of private notes. But I think writing for broadcasting is overrated. Journaling or diarying is writing for myself, and often in a fo
4.
by chrishill89 3mo ago
If works/doesn't are semantic checkpoints, then I use that every day for myself with Git notes.
5.
by chrishill89 3mo ago
Many years ago I helped a friend with some draft that had to do with him finishing his doctorate. It ended up being maybe 50-60 between three of us and as fine grained as possible. That agents need something "beyond git" is lost o
6.
by chrishill89 3mo ago
Absolutely. You didn't have to make an account to remind me, at least. His relationship with Epstein was shameful and there is no excuse for it.
7.
by chrishill89 3mo ago
IMO that is only a problem for those who demand that the issue key needs to go first in the subject (which again IMO is bad for readability). I don't see why you can't just stick it somewhere after all the conventional commits jun
8.
by chrishill89 3mo ago
Want machine-readable? Use the footers/trailers. I can not say anything nice about conventional commits. The format takes up space in the most-read part of the message. The categories or types have little information. They can be repla
9.
by chrishill89 4mo ago
Does that show Jensen in a better light?
10.
by chrishill89 4mo ago
It took me many years to even think of problems that I wanted to solve. Or were missing. But eventually it happened. And it seems that the more time passes the more that list of ideas just expands since no one can follow up on all of those
11.
by chrishill89 4mo ago
Setting up a Mac user account. What accessibility settings do you need? - [four options/catgories] - Remind me Later (or something) And I guess the Later option is technically accurate.
12.
by chrishill89 4mo ago
I wrote an essay and sent it to Chomsky once. He wrote back that he probably won't have time to read it. Some years ago I realized that I can just start sending emails to an OSS mailing list. Without introduction just starting to post
13.
by chrishill89 4mo ago
I really like the Oracle tutorial on Java asserts. https://docs.oracle.com/javase/8/docs/technotes/guides/langu... And I'm pretty happy with its design considering its age. Notably this is not
14.
by chrishill89 4mo ago
Pretty recent Git versions have git-last-modified(1) which can list all files along with the last modified commit.
15.
Tell HN: Happy May Day
13 points by chrishill89 5mo ago|5 comments
16.
by chrishill89 5mo ago
> Maybe the worst part about this is that it can entirely come from a patch being exported by git and then imported straight back in to git. No one wants to apply diffs in commit messages. But some people use this technique via email:
17.
by chrishill89 5mo ago
git-am(1) (apply patches) delimits the commit message from the patch/diff by looking for (1) a line `---` or (2) a line that starts with `diff -` or (3) a line that starts with `Index:SP` (SP is space). Only the first rule is necessary
18.
by chrishill89 5mo ago
> It's very widely remarked that the Git CLI is pretty miserable, and as soon as a better (so I hear) alternative comes along they suddenly realise and start improving it... This happens all the time in software. This command is imp
19.
by chrishill89 5mo ago
Yeah it’s a direct inspiration.
20.
by chrishill89 5mo ago
I don’t know what the semantics of invoking Git means? These two commands operate on the same level of abstraction. And they should be equally powerful, which means that whichever you choose to learn will be able to serve all of your restor
21.
by chrishill89 5mo ago
Neither of these two commands are any more really-operates than the other.
22.
by chrishill89 5mo ago
The git-restore(1) implementation looks like about 35 lines of code. Then add a little more complexity for some apparent common functions that needed to be factored out. For a dedicated "restore" it's worth it to me... (who w
23.
by chrishill89 5mo ago
Didn't Go propose opt-out telemetry but then the community said no? Compilers and whatnot seem to suffer from the same problem that programs like git(1) does. Once you've put it out there in the world you have no idea if someone w
24.
by chrishill89 5mo ago
Git relatively recently got an `--i-still-use-this` option for two deprecated commands that you have to run if you want to use them. The error you get tells you about it and that you should "please email us here" if you really am
25.
by chrishill89 5mo ago
Let's say that this is obsolete for professional programming. Can't us hobbyists be left alone to our hobby by the LLM demoralization patrol?
26.
by chrishill89 5mo ago
> incorporated in Git.[1] Dangling footnote. I decided against adding one and forgot to remove it.
27.
by chrishill89 5mo ago
Not all software is developed by one software organization. Programs to manage “stacks of patches” go back decades. That might be hundreds that have accumulated over years which are all rebased on the upstream repository. The upstream repos
28.
by chrishill89 5mo ago
Sometimes I have several pull requests to review and none of them have any meaningful overlap (e.g. they touch code in different places, no apparent risk of overlap). So I've started making integration branches to test all of them in o
29.
by chrishill89 11mo ago
> Do I want every PR to be a long ugly list of trivial half-done commits with messages like “fix typo” or “partial checkpoint of encabulator functionality”? No. Does everything need to be hammered down into a single wad? Also no. There i
30.
by chrishill89 11mo ago
> Might as well squash as nobody wants to deal with untested in-between crap. I would rather deal with nice and tidy but untested commits rather than a very well-tested but too monolithic squash. If you test the eventual merge then you

More ›