neoncontrails

I'm sure that's true, and sad. I ask because the study identifies differences between the medicated and unmedicated cohorts, and I'm curious if the incarcerated population falls squarely into one of those two categories.

That is a fun fact. Do they receive medication for it?

This looks like it could potentially be a huge productivity win. The ergonomics seem tantalizingly similar to the infamous scene from Minority Report where Tom Cruise manipulates translucent data streams with his bare hands.

Could I suggest that you shoot a new promotional demo video with enough lighting that viewers can see your hands? Personally I'd be very curious to see and understand the actual gestures that support a real world workflow involving multiple desktops and applications, with the hands transitioning as needed between neural band mode for navigation vs. keyboard/mouse mode for fine-grained motor inputs.

And it will have the effect of making these tools more popular, as it boldly proclaims how effective they are against even nation-state–level threats.

I know you jest, but both the IPFS contributors I knew in college graduated to become web3 degens working on decentralized file storage projects. Specifically Walrus, which grew out of Meta's Libra project.

Well, the alternative is a lot of us spammed A to get to the end, so the data quality is already horrendous.

Exactly the same here. 4/5.

The difference is twofold. First, junior devs who ask for code reviews on massive, 2000+ line diffs get coached, and eventually fired if they persist at it. And second, even the most prolific junior engineer would take years to write what Claude is capable of generating in an afternoon.

When Sundar Pichai announces that 75% of all new code at Google is AI-generated, their stock price goes up. If he were to announce that 75% of all new code at Google is now written by junior engineers, this would trigger a massive sell-off and a lot of employees would resign.

Can you name an active filesharing app that's in use today? The action against Napster might not have killed filesharing, but it was p2p's Antietam.

I'd be interested to try this out. I'm especially keen on AI tools that implement a native RAG workflow. I've given Cursor documentation links, populated my codebase with relevant READMEs and diagram files that I'm hoping might provide useful context, and yet when I ask it to assist on some refactoring task it often spends 10-20 minutes simply grepping for various symbol names and reading through file matches before attempting to generate a response. This doesn't seem like an efficient way for an LLM to navigate a medium-sized codebase. And for an IDE with first-class LLM tooling, it is a bit surprising that it doesn't seem to provide powerful vector-based querying capabilities out of the box — if implemented well, a Google-like search interface to one's codebase could be useful to humans as well as to LLMs.

What does this flow look like in Brokk? Do models still need to resort to using obsolete terminal-based CLI tools in order to find stuff?

I have such a love/hate relationship with dunders. On the one hand, I get warm fuzzies from simplifying a module's interface with `__call__`. More than once I've seized an opportunity to rewrite some ugly conditional logic with a partial ordering by leveraging `__gt__`, `__lte__` and friends. `__setattr__` remains an interesting alternative to using decorators to execute some pre- or post-call behavior to a class method. (IIRC it can also be more efficient than wrapping a method with a decorator, since the `__setattr__` override gets precompiled into Python bytecode along with the rest of the class def.) Probably some other sleights of hand along these lines that I'm forgetting. I'm sure they were fun to write and I probably felt clever doing it.

Unfortunately in almost every case, dunder methods made it harder for me to collaborate with other people on the same codebase. And I get it. Tinkering with `__setattr__` leads to recursion errors if you're not careful, `__call__` introduces state in an unexpected place (wait, foo is a class instance? But but it behaves just like a function...). It's one of the only "stupid Python tricks" I can think of that lacks a clear analog in other programming languages, so polyglots without a strong Python background tend to hate them. I've tried to make the case on two separate occasions that dunder methods represent a more object-oriented approach to dealing with systemic complexity than type dispatch, and I stand by this. But I concede that the benefits of making the codebase nicer and more ergonomic in some places invariably requires writing class definitions that look horrendous in other places. So it's not so much that dunder methods reduce that complexity, so much as try to contain it and hopefully prevent it from spilling out into the main execution logic.

P.S. - Trey, if you're reading this, hello from a former TA!