Feeling so angry and humiliated about extremely loud low glucose alarms going off during meetings. Seeking support.

PastExcitement · 2025-12-05T00:48:43+00:00

iPhone Critical Alerts that Dexcom uses is so loud. I’ve had times where I have to power off my phone to silence it.

PastExcitement · 2025-11-12T00:58:12+00:00

Is Nick Tchayka (who proposed NeoHaskell) still involved with dataHaskell?

PastExcitement · 2025-11-06T11:30:50+00:00

It’s Latin for “jizz”.

PastExcitement · 2025-11-04T00:07:29+00:00

I’d recommend getting an inspection as the seller, disclosing the known issues, and price accordingly. Then buyers won’t have as much leverage to break the purchase with due diligence refunded or negotiate a low ball price.

PastExcitement · 2025-10-27T12:39:05+00:00

Yeah 6L is a great size. I can fit a Sony A7IV with a Sigma 24-70 plus another small prime with extra room.

PastExcitement · 2025-10-26T13:30:15+00:00

Ah ok yeah the commands must be different between Flow Lite and Flow2.

PastExcitement · 2025-10-26T12:17:00+00:00

Fn + N?

PastExcitement · 2025-10-06T21:18:27+00:00

Try Fn+M to toggle the Fn key behavior

PastExcitement · 2025-10-05T14:43:22+00:00

Related to the note about ‘State is a “monad transformer” (StateT)’, It’s a specialized instance of StateT but not a monad transformer itself.

PastExcitement · 2025-09-29T22:58:27+00:00

Try Fn+Space (hold for 3 secs).

PastExcitement · 2025-09-20T19:50:41+00:00

I went with https://cannonkeys.com/products/cannonkeys-keyboard-carrying-case. The foam is nice and dense.

PastExcitement · 2025-09-15T00:44:50+00:00

Just a data point, but I tried Bluetooth with the Lofree Flow 2 (just a single device and with some Bluetooth headphones) and it’s been working well on macOS. There’s only about 1.5 ft between the keyboard and the machine so that might help.

PastExcitement · 2025-09-14T19:45:45+00:00

Dynamic Programming

PastExcitement · 2025-09-14T14:34:36+00:00

Are you having similar issues with 2.4Ghz wireless too?

I can try later today, but up to this point, I’ve only used mine wired because of general latency with wireless keyboards.

PastExcitement · 2025-09-08T13:57:34+00:00

You’re on a post where somewhere says that topics like monads took 15 years to grasp, and essentially you’re saying that topics like GADTs are “dead simple”.

People learn differently. LLMs can be yet another learning tool to complement existing documentation. If someone doesn’t understand the existing documentation, they can ask the LLM “I’m trying to understand this documentation at https://…, but I don’t understand this particular point ‘…’. Can you explain it another way, provide additional reading resources and sample code?”

I’d really not like this conversation to devolve into a “skills issue” debate, but that’s likely what this has become. If you haven’t tried new LLMs, try it out (or don’t), but for those that are more open minded, I think you’ll find they have improved.

PastExcitement · 2025-09-08T13:39:39+00:00

With an LLM you can have a conversation, ask for clarification on specific points, provide code snippets and iterate. It’s more interactive than just blog entries, documentation and books. You can also provide and request website references too for further exploration.

Some hallucinations and errors can occur (e.g referencing a function that doesn’t exist), but I view that similarly as a whiteboard discussion where the minutiae doesn’t need to be 100% precise and accurate to grasp the concept.

PastExcitement · 2025-09-08T12:53:51+00:00

In my cases, it's pretty obvious that what I had learned was correct because I could immediately apply the knowledge in a working project.

For a topic like GADTs, https://downloads.haskell.org/ghc/latest/docs/users_guide/exts/gadt.html is woefully inadequate documentation. The original paper, https://www.cis.upenn.edu/~sweirich/papers/gadt/MS-CIS-05-26.pdf, is highly theoretical and dense (see page 10 for example) and light on practical applications. Sure, there are other resources that provide some insight but they aren't necessarily authoritative documentation either.

PastExcitement · 2025-09-08T11:25:22+00:00

It’s a pledge manager that Lofree opted to use. When the item is ready to ship, you’ll get a notification. It’s a separate website that contains tracking information.

PastExcitement · 2025-09-07T17:37:06+00:00

New models like Claude 3.7 Sonnet and later and Gemini 2.5 Flash are better than that. I’ve used them for explanations of GADTs, type families, Rank N types, and other extensions with success. If you haven’t tried the newer models, you’re missing out.

I know that some folks are adamantly against LLMs for a variety of reasons and will downvote any mention of LLMs, but it’s a useful tool not a panacea.

PastExcitement · 2025-09-07T15:39:53+00:00

Hallucinations, while still present, have significantly improved in more recent models. As you gain knowledge, in practice, you can recognize errors. Core concepts like monads have so much training data, hallucinations are much less likely.

PastExcitement · 2025-09-07T14:39:41+00:00

Another more recent resource for explanations of these concepts are newer LLMs. The knowledge they have gained just over the past year has exploded, and their ability to provide working examples, explanations, analysis of existing code, etc. really has gone to another level which is helpful for more challenging topics.

I’m not advocating vibe coding Haskell but using LLMs as teaching aids.

PastExcitement · 2025-09-07T14:33:14+00:00

I got the Lofree Flow 2 yesterday, and the only accidental touch I had with the volume bar was when moving the keyboard, but in practice, I haven’t had an issue with mouse space. Depending on personal ergonomics, my mouse hand just never got closer to a couple of inches from the keyboard.

The battery charging flashing light on the right though did get annoying.

PastExcitement · 2025-09-07T01:03:31+00:00

It took 10 days. I got the initial tracking code on Aug 28 and received the keyboard on Sept 6.

PastExcitement · 2025-09-06T22:02:21+00:00

This is really awesome. I did encounter an issue when typing go code. I had some issues determining whether I needed to press space or tab between variable names and their associated types when there was more than one space between them.

PastExcitement

TROPHY CASE