I've heard of the "three-star C programmer" https://wiki.c2.com/?ThreeStarProgrammer but I think we should have "three semicolon lisper". When you're organising your code in sections, you're building major projects!
miniblog.
Related Posts
What's your preferred granularity of docs?
(a) A whole module on one page, e.g. https://pkg.go.dev/time, making search easy?
(b) A function per page, e.g. https://www.php.net/manual/en/function.time.php, giving more space for examples and See Also sections?
I'm torn, and I've seen both done well.
I write a considerable amount of markdown these days, but I've developed a numbering style that is deliberately not part of the syntax.
(1) Foo.
Bar.
(2) Baz.
Auto (re-)numbering can be really surprising, and numbered sections tend to be narrower and harder to read.
Arxiv is huge and I find it hard to find things relevant to my interests. Playing with https://scirate.com/ seems like a good solution: you can follow sections that interest you, and 'scite' (basically 'like') papers.
