|
|
|
|
|
by franga2000
1 hour ago
|
|
So much LLM marketing/hype speak in the readme, so many moving parts, failure points, wasted CPU cycles, added latency, not to mention the externalities of the tokens that were burned on this...all to do what even the cheapest audio processors are able to do. Back in the day you could dismiss all of that as "it's part of the learning path" and yes, I made over-engineered non-solutions to long-solved problems when I started programming too. But this isn't learning. It's pure LLM slop. LLMs are doing the thing that greedy/unethical programmers used to. They'd quote a client a dozen microservices and four months of work for something that could be solved by writing a slightly longer Excel formula. Not that the quote was crazy or the work was poorly done, it just wasn't anywhere near necessary to solve the problem. But they got paid and the client was happy because they didn't know any better...until I showed up to ruin the fun. |
|