HN user

jweather

281 karma
Posts4
Comments171
View on HN

Remapping a few things can make a full day at the computer much more comfortable. I struggle with RSI in my right thumb and index finger, so it helps a ton to have other ways to click the mouse button. I have a dedicated key for mouse click, as well as using Mod+Caps Lock as double-click. Don't be afraid to move shortcuts around if it makes sense. Brains are more adaptable than we tend to give them credit for.

Pretty fun, needs some improvements:

- wire routing makes most circuits write-only. There's no way to follow the wires once a circuit is completed, it's easier to delete them all and start over.

- some of the later levels seem incomplete, at least as far as test cases: 2.26 Row Buffer you don't actually have to buffer the row to meet the requirements. 2.34 can be completed with a single VDD symbol. 2.37 and 2.38 I expected to have access to components that I had completed previously, but then it turned out neither of them have complete tests so they can be cheesed as well.

- no GPU?

I have a similar sized macropad that I use extensively with AutoHotKey for application-specific shortcuts like clicking on buttons that don't have a keyboard shortcut, or scrolling two panes of a window simultaneously. All things that I could bind a key combo to, but I like having a dedicated button for.

parens are third and fourth finger

=+ is my palm (weird keyboard I know)

[]{} I used a modifier key to put them on O and P directly below () (columnar keyboard)

-_ and \| are actually pinky

I don't feel like any particular finger is overloaded. Dvorak helps a lot with that IMHO.

In my small corner of technology (AV) I regularly use three products with physical USB license keys: Crestron VC-4, Scala Digital Signage, and Dataton Watchout. Two of them have a "virtual license key" option that costs extra, intended for use with a VM. I wish they were more rare...

This is so cool! Having a ton of fun. Only place I got stuck for a while is on instructions adding extra cycles - didn't see the note at the bottom of instructions.md. Did I miss a way to open documentation in the left pane? I keep taking screenshots of the docs that I can view on another monitor while I'm coding.

I think the click logic may be a little twitchy. My trackball button worked okay, but my footpedal button frequently did what you describe here - possibly due to a longer-duration button press?

And yes, that would be helpful, but would remove part of the memory challenge. Maybe an optional feature?

Sonic Pi is by far the most accessible way to play with these tools. It's designed to teach music and coding to kids and has great starter tutorials, and a ton of depth as well. Check it out!

Mode feedback is the only thing I can think of, especially when you're getting used to the keyboard and/or have mode toggles set up. I don't have much use for my keyboard screens personally. Cool place to put a logo I guess.

My daily driver is an Allium58 not too different from the Moonlander. I love having modifier keys to set up macro functions and layers. My favorites from an ergonomics standpoint are Mod1+WASD for arrow keys (Q=home, E=end), Mod1+Capslock for double-click, and Mod1+Tab for middle click (my trackball doesn't have one). It didn't take too long to get to a faster WPM than I had on my previous 101-key mechanical, and I can go back to normal keyboards when I have to.

Well, TinyChat. Still mind-boggling. From the video description:

  I built a small language model in Minecraft using no command blocks or datapacks!

  The model has 5,087,280 parameters, trained in Python on the TinyChat dataset of basic English conversations. It has an embedding dimension of 240, vocabulary of 1920 tokens, and consists of 6 layers. The context window size is 64 tokens, which is enough for (very) short conversations. Most weights were quantized to 8 bits, although the embedding and LayerNorm weights are stored at 18 and 24 bits respectively. The quantized weights are linked below; they are split into hundreds of files corresponding to the separate sections of ROM in the build.

  The build occupies a volume of 1020x260x1656 blocks. Due to its immense size, the Distant Horizons mod was used to capture footage of the whole build; this results in distant redstone components looking strange as they are being rendered at a lower level of detail.

  It can produce a response in about 2 hours when the tick rate is increased using MCHPRS (Minecraft High Performance Redstone Server) to about 40,000x speed.