8,351 karma · joined June 7, 2016
Twitter: @tomduncalf
I’d definitely pay more for a Waymo, which is a much more reliably pleasant (and very cool!) experience.
They probably can’t solve totally novel problems but they are good at transposing existing solutions to new domains. I’ve built some pretty crazy stuff with just prompts - granted I can prompt with detailed technical instructions when needed as I’m a SWE, similar to instructing a junior. I’ve built prototypes which would take days in hours which to me is hugely exciting.
The code quality of pure AI generated code isn’t great but my approach right now is to use that to prototype things mostly with prompts (it takes as much time to build a prototype as it would to create a mock up or document explaining the idea previously) then once we are committed to it, I’ll rebuild it mostly by hand but using Cursor to help.
Also it doesn’t hurt that React has quite a stable/backwards compatible API, so outdated snippets probably still work… and in Tailwind’s case, I suspect the direct colocation of styles with the markup makes it a bit easier for AI to reason about.
For WASM with C++, I recently created a simple example using the new-ish AudioWorklet support in Emscripten, showing how to create an AudioWorklet oscillator with parameters. It removes a lot of the boiler plate you used to have to do, but the docs are a bit lacking.
https://github.com/tomduncalf/emscripten-audio-worklet-examp...
If he wants to generate audio, Tone.js can be a useful higher level abstraction for WebAudio.