jhurliman

Joined 16 years ago

Karma
228
Submissions
71
Member since
Oct 6
https://jhurliman.org/

[ my public key: https://keybase.io/jhurliman; my proof: https://keybase.io/jhurliman/sigs/r1AFYXcqr3HP5OO55Ek27hFX8FIwIjUzHmesSMd86Hc ]

View on Hacker News

Recent submissions

Comment · 6 months ago
Comment · 10 months ago
Comment · 10 months ago
One thing I don’t cover in the blog post is ensuring your MCP tool calls are well documented. (If it’s an existing MCP you can do this with a README or instructions file.) I saw a jump in efficiency when I manually edited the docstrings with examples of when each tool would be used, how to call it, and better argument descriptions.
Comment · 10 months ago
Author here, I think you’re spot on. If I set out specifically to make a mashup and spent the same number of hours working toward that goal I think I could have gotten to the same place. This was a journey that started with wrapping my head around MCP and LLM local software interoperability, and my Ableton knowledge leveled up a lot along the way.

I think this tooling could be useful in the hands of more capable musicians / audio engineers / etc. as there are often repetitive tasks in DAWs and it could potentially unlock new workflows that would have been too tedious without knowing how to program.

Comment · 1 year ago
I think it just got folded under the umbrella concept of model alignment. And it moved from theoretical discussions to practical daily struggles with LLMs deleting failing unit tests
Comment · 1 year ago
Comment · 1 year ago
That’s exactly what I have. The C++ codebases I work on build against a specific pinned version of LLVM with many warnings (as errors) enabled, and building with a different version entails a nonzero amount of effort. Ubuntu will happily install several versions of LLVM side by side or compilation can be done in a Docker container with the correct compiler. Similarly, the TypeScript codebases I work with test against specific versions of node.js in CI and the engine field in package.json is specified. The different versions are managed via nvm. Python is the same via uv and pyproject.yaml.
Comment · 1 year ago
I didn’t see any mention of running a model locally on device like the Hibiki abstract states. Is this available?
Comment · 1 year ago
three.js might not be the right fit for computational rendering/raytracing, optimization techniques like frustum culling are more or less baked into the engine.
Comment · 1 year ago
Was https://hyperaide.com/pricing added after your comment?
Comment · 2 years ago
Comment · 2 years ago
vscode remote containers are still the standard, but I find them very usable nowadays. My setup is a MBP M2 that I use to remote into a Windows WSL setup at home, a Linux desktop at work, and various servers. Nesting remote SSH + remote Docker works seamlessly, that was previously a major headache.
Comment · 3 years ago
Yes, Cruise cars have enough pose/gesture recognition for this. It’s needed for road construction with flaggers.
Comment · 3 years ago
Take a look at the MCAP file format (https://mcap.dev), we invented it for the robotics industry but it’s a generic write-optimized container format for time series data. Since it’s a container format, you need to choose a serialization format as well such as flatbuffers or protobufs.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton