Rather than bullet points per se, I find it natural to think hierarchically. Bullet outlines are one way of writing this hierarchy out. I think this is OK for a comment.
For a top-level post though, it feels unfinished. It’s fine to start with an outline, but note that markdown headers also have hierarchical layers just like bullets, with paragraphs below that. Prefer the headers for posts and reserve bullets for very short “leaf nodes” below the level of paragraphs, and only when they add clarity.
If you find you like to think in outlines, I recommend trying FreeMind, which lets you uproot and graft entire subtrees with much less effort than typing bullets. Once you have your thoughts outlined, you can export to normal bullet points.
I like the idea of using a “high level” section of a post, but it’s hard to do any better than writing a bunch of summaries. It’s just confusing to me about that.
There’s a lot to explain here, but I hope that some of this can be discussed together. For example, I didn’t like the term “high level” when I tried to argue with the post on how I understand the “high level” concept. I think “high level” really is a stronger phrase than “high-level”—it’s easier to describe if you can define the higher-level concepts more clearly. Now, for my purposes, “high level” is just the term “high-level” I meant to communicate.
And now, I’ve tried to make the concept “high-level” refer to things in the high-level concept—you need to know that “high-level” means something to you, and “low-level” is what you mean. So that you can understand it better if you can define a term as a synonym for “high level”.
(I’m starting to think I’m going to call it “yitalistic level”. But then why do I call it the “high level”? And I find that definition hard to do.
Rather than bullet points per se, I find it natural to think hierarchically. Bullet outlines are one way of writing this hierarchy out. I think this is OK for a comment.
For a top-level post though, it feels unfinished. It’s fine to start with an outline, but note that markdown headers also have hierarchical layers just like bullets, with paragraphs below that. Prefer the headers for posts and reserve bullets for very short “leaf nodes” below the level of paragraphs, and only when they add clarity.
If you find you like to think in outlines, I recommend trying FreeMind, which lets you uproot and graft entire subtrees with much less effort than typing bullets. Once you have your thoughts outlined, you can export to normal bullet points.
I like the idea of using a “high level” section of a post, but it’s hard to do any better than writing a bunch of summaries. It’s just confusing to me about that.
There’s a lot to explain here, but I hope that some of this can be discussed together. For example, I didn’t like the term “high level” when I tried to argue with the post on how I understand the “high level” concept. I think “high level” really is a stronger phrase than “high-level”—it’s easier to describe if you can define the higher-level concepts more clearly. Now, for my purposes, “high level” is just the term “high-level” I meant to communicate.
And now, I’ve tried to make the concept “high-level” refer to things in the high-level concept—you need to know that “high-level” means something to you, and “low-level” is what you mean. So that you can understand it better if you can define a term as a synonym for “high level”.
(I’m starting to think I’m going to call it “yitalistic level”. But then why do I call it the “high level”? And I find that definition hard to do.