https://www.paulkeeble.co.uk/posts/cff/

Drop-in replacement for java.net.Socket using shared memory (and optionally, futex for notification)

Not sure if it helps. Have not tried the app yet.

Edit: sorry, didn't see the almost identical answer

I was referring to this:

"it is customary in Lua to start arrays with index 1" [1]

Not being a native English speaker, I may have phrased something wrong. I find "one-based indexing" in arrays not particular intuitive, and error-prone.

Better?

[1] https://www.lua.org/pil/11.1.html

The first to write "stored procedures" in Redis (I forget the correct terminology). It allowed to improve the performance of Django endpoints by an order of magnitude.

In the second, I wrote a Wireshark plugin (also not sure of the proper term) to dissect a proprietary protocol.

I don't remember the details but this is not a programming experience I look forward to renew... (Same feeling about Perl btw)

Possibly indices starting at 1 were the most disturbing.

Squashing, dropping commits, rebasing. Even interactive rebase can be done in a few clicks.

I sometimes pop up IDEA to do some non-trivial cleanup in a repo. Even if relatively fluent with the command line, it saves me a lot of time.

This requires configuring the mouse to have sufficient "speed". I've never had any musculoskeletal disorder, probably thanks to making such small moves with my hand and staying relaxed.

https://learn.microsoft.com/en-us/windows/dev-drive/

The "reeducation" consisted in a few 30 minutes sessions (probably around 5, not sure) and I don't remember having done any conscious effort to breathe through my nose after that. It just seemed easy.

That said, I still have to breathe through my mouth when running.

Before that, I was mostly breathing through my mouth. It was challenging even to eat a sandwich while walking :). Since this reeducation, I only breathe through my nose with no effort. I'm willing to believe it indeed has to do with muscle.

- TDD, which as you say describes the system's behavior. But it often deals with the nominal cases. It is hard to predict all that can go wrong in the initial development phase.

- tests designed to reproduce a bug. The goal of these to try very hard to make the system fail, taking inspiration with the bug's context

Maybe this LLM test generator could allow to be more proactive in the second kind?

I would have said point and click is 3-dimensional.

Otherwise, how can you read the text through the edges of buttons before clicking?

Until I left it in my basement for a few weeks, i.e. in a slightly cold and humid environment.

Now, the keyboard is broken: I need to press multiple times on each key (it's better now that it has dried a bit, but not perfect).

The trackpad is also broken: only hard-clicking works.

Next step is to open and clean it up but I don't have much hope.

But I tend to use reader mode on most sites anyway because it's an easy way to get rid of banners (cookies, subscription etc.)

In Chrome, this is not a big issue because the panel is on a separate column (compared to the main panel where variables values can be browsed).

In Firefox, both panels are in the same column. When many breakpoints are set, one must scroll or click to close the breakpoints panel before any work is possible.