1,295 karma · joined July 16, 2017
https://github.com/baalimago https://lorentz.app
More likely is the rise of test driven development, or spec driven development.
An agentic media player, intended as home media server for.. uhh.. seasonal vacation videos with subtitles. I've experimented a lot with different "levels" of AI automation, starting from simple workflows, to more advanced ones, and now soon to fully agentic.
Pretty good practice project! All written in Go with minimal dependencies and an embedded vanillja-js frontend built into the binary (it's so small it's negligable)
But ofc, I understand styleguides are... well.. guides. Not law.
I'm not saying the principles themselves are poor, but I don't think they're suitable for a commercial environment.
The monolith agent seems like a generalist which may fail to be good enough at anything. But what do I know
Email validation doesn't work. Ip blocking doesn't work. Captcha? Kind of. Fingerprinting? Very efficient.
My request would be to have an example PRD with premade workflow which works reasonably well for any project. I didn't use the `run_example.py` as it lacked workflows. At the end of the day, I just want to investigate if the project is something I'd like to dedicate time to, I gave up after about 2-3 hours. To have it 'plug-and-play' would be neat.
There's also a lot of references to your local filesystem, which perhaps could be cleaned up.
Couldn't quite get everything to run since there was so much configuration to setup, but the idea is solid.
So feature suggestions:
* Pipe data into qq ("cat /tmp/stacktrace | qq What is wrong with this: "),
* Profiles (qq -profile legal-analysis Please checkout document X and give feedback)
* Conversations (this is simply appending a new message to a previous query)
[0]: https://github.com/baalimago/clai/blob/main/EXAMPLES.md
776 words in a single paragraph
The same reason as why streaming services are being ditched in favor of piracy will happen to social media.
Quite battletested on heavy devops tasks. The design is simple: every command is a subprocess spawned by in -n number of go routines. Then there's some extra fluff to tie the worker pattern together and deliver statistics.
Why not xargs? Ergonomics, and speed. Repeater is faster, see benchmarks.