You really shouldn't and often cannot legally send off data or information about data to 3rd parties. Maybe schemas are okay but 1 mistake and your company can be in serious trouble. So local models is a good idea.
This is a safer workflow if implemented correctly to prevent certain types of mistakes when LLMs inevitably hallucinate or make a mistake.
That said, 200 usd? I don't believe the value is there. Someone can run a local model very easily, 1 command line call and do this themselves. For free.
the best you can do is show them the code and hope they catch mistakes. Data scientists who can't read code probably shouldn't be running AI generated analysis on real data.
Two paragraphs in and I have no idea what they’re selling me. A timeline on how to write a book? A font? A solution to a problem? Just casual lording? AI slop at its finest.
Dangerously skip permission is the goat, until it isn’t. I’ve seen so many engineers shrug when asked about how they handle permission with CC. Everyone should read for Black Swan, especially the Casino anecdote.
People seem to think prompt injection is the only risk. All it takes is one (1) BIG mistake and you’re totally fucked. The space of possible fuck-up vectors is infinite with AI.
Glad this is on the fail wall, hope you get back on track!
> The most underrated skill to learn as an engineer is how to document. Fuck, someone please teach me how to write good documentation. Seriously, if there’s any recommendations, I’d seriously pay for a course (like probably a lot of money, maybe 1k for a course if it guaranteed that I could write good docs.)
I have ~40 demoes from a music career that never took off. Now I am feeding little Suno with this demoes, turning them into afrobeat with oboe, deep house with harmonica, etc, and reliving the creative joy.
You can make a decent demo in a DAW and run it through AI for a nice production. The art of writing songs is still equally hard IMO. And a good song is still good, no matter what costume it wears.
reply