Personally I write with too many asides, normally done with commas and parentheses. It's a comforting habit to fall into, and makes getting your thoughts out so much easier, at the expense of interrupting the reader's train of thought.

I don't normally notice when I'm writing with asides so the jarring em-dashes were a good reminder to try and edit them out where I can.

As you point out, authors use them for the "natural and chaotic shifts of thought we all have" and when there are lots of these shifts it feels like I have to keep track of multiple conversations at once.

For example, in the article we have:

If your goal is to have other people read—and hopefully enjoy—your writing, you should make an effort to edit your thoughts.

When I read this I instinctively pause the 'main' thought/voice, read the aside, then re-establish my train of thought. In my opinion the sentence reads just as well without the aside:

    If your goal is to have other people read and enjoy your writing you should make an effort to edit your thoughts.

    If your goal is to have other people read and enjoy your writing, you should make an effort to edit your thoughts.

Again this is probably a cultural thing, maybe a reaction to AI as well, but I find the em-dash a lot more though-interrupting than the other punctuation choices and I wonder if it's something I'll get used to or not.

As per [0] merge commits are dropped:

Note that format-patch will omit merge commits from the output, even if they are part of the requested range. A simple "patch" does not include enough information for the receiving end to reproduce the same merge commit.

I originally thought it would use --first-parent (so just diff vs the first parent, which is what I would want) but apparently no! It is possible to get this behaviour using git log as detailed in this great write-up [1].

[0] https://git-scm.com/docs/git-format-patch#_caveats

[1] https://stackoverflow.com/questions/2285699/git-how-to-creat...

I know that it doesn't feel like I am doing anything particularly algorithmic when I communicate but I am not the hommunculus inside me shuffling papers around so how would I know?

https://www.masterclass.com/classes/penn-and-teller-teach-th...

> not free software

which it is. As F3nd0 said, it's both.

The impact of uv on our onboarding and utilisation of python has already been huge, and any way I can easily improve their code hygiene is a good one. Yes, I could get them to use ruff standalone, or set up pre-commit hooks etc for them, but the simple mental model that comes from `uv ` is really beneficial.

Will have a play around with this and see how it goes. Would love to be able to hook into other formatters too, but not sure if that's easy or even possible already. For example, I would love it if `uv format` also formatted our SQL/dbt models.

Someone mentioned recently that the slowness of rustc is in large part due to llvm. I know that is probably orthogonal to the work here, but I do like the idea of building the compiler with different toolchains, and that there may be follow on effects down the line.

    uv add --dev uv-bump
    uv-bump

https://pypi.org/project/uv-bump/

It seems like you might also be absurdwebsite which doesn't seem to be banned (but does have a hidden post from a month ago).

If you plan to use this account it's worth dropping an email to the admins, they are very responsive :)

I enjoyed the summary and highlights, and learnt about some details I would likely have never otherwise seen, so I think it's just the framing that seemed 'off'.

Depending on your intent consider reframing or adding critique, but I think the content is good and I appreciate you making it.

[edit] There is some critique and comparison in the opening: "Shakespearean tragedy" and "The result is equal parts invention history, boardroom knife-fight, and forensic accounting thriller." but I think these are the only ones. I would love to know why you think this, and what you like about your "favorite ideas" (and any things you didn't like!)

I expect 41+14 to be 12 (two right plus two up equals two right and two up).

Long addition in long form below uses:

'=' to show equivalent lines (reordering of terms (1+2=2+1), spliting numbers (41=40+1), adding single digits (1+4=22))

'->' for when the algorithm gives a digit

'<' for when we move over a column

    41+14
    = (40+1)+(10+4)
    = 40 + 10 + (1+4)
    = 40 + 10 + 22
    -> 1s digit = 2
    < 4 + 1 + 2
    = 22 + 2
    = 20 + 2 + 2
    = 20 + 41
    -> 10s digit = 1
    < 2 + 4
    = 0
    -> done
    == 12

It still works in the alternative system (14+21 should equal 12)

    14+21
    =10+20+42
    ->2
    <1+2+4
    =13+4
    =10+3+4
    =10+31
    ->1
    <1+3
    =0
    ==12

If they'd previously been up in sounding rockets, or high altitude aircraft, or like a Blue Origin sub-orbital hop we would likely have an interesting discussion here - I will take anything that has surpassed the McDowell line as being 'in space' but think making orbit is more impressive.

https://en.wiktionary.org/wiki/McDowell_line

I wasn't sure how to chain function calls so had to look that up to implement movei, but apart from that was fairly straightforward (it's (do () () ...)).

My UI was pretty simple and ended up being

    (defn looki [] (display-html (look-html (look))))
    (defn movei [dir] (do (move dir) (looki)))
    (looki)
    (movei :south)
    (movei :east)
    (movei :north)
    (movei :south)
    (movei :west)
    (unlock-function :spoiler)
    (stack)
    (push :picture)
    (push :spoilers)
    (peek)
    (pop)
    (reset)