LLM-written code is typically over-commented and under-logged. So much so that I've given up pleading with them to stop commenting and start logging. Instead I say 'Great, now that you've written the code please replace the comments with logs.'
Readit Newsmbanerjeepalmer commented on My favorite use-case for AI is writing logs newsletter.vickiboykis.co... · Posted by u/todsacerdoti
mbanerjeepalmer commented on About AI Evals hamel.dev/blog/posts/eval... · Posted by u/TheIronYuppie
I'm biased in that I work on an open source project in this space, but I would strongly recommend starting with a free/open source platform for debugging/tracing, annotating, and building custom evals.
This niche of the field has come a very long way just over the last 12 months, and the tooling is so much better than it used to be. Trying to do this from scratch, beyond a "kinda sorta good enough for now" project, is a full-time engineering project in and of itself.
I'm a maintainer of Opik, but you have plenty of options in the space these days for whatever your particular needs are: https://github.com/comet-ml/opik
Yes I'm not sure I really want to vibe code something that does auto evals on a sample of my OTEL traces any more than I want to build my own analytics library.
Alternatives to Opik include Braintrust (closed), Promptfoo (open, https://github.com/promptfoo/promptfoo) and Laminar (open, https://github.com/lmnr-ai/lmnr).
mbanerjeepalmer commented on It doesn't matter if RSS is 'dying' zacusca.net/blog/rss-dyin... · Posted by u/mbanerjeepalmer
Aside from the clickbait headline (hey, it worked on me) this seems cool...but I don't see myself using it. Why? I have a bunch of unread posts (either new or old) that I would lose by doing an export/import. Import would result in me only having the most recent posts from each feed. And I'd have to use this tool frequently to categorise new feeds? Painful. Unless I'm missing a way to import just the categories and keep all my existing posts and unread items? I use FreshRSS.
Clickbait headlines are a necessary evil.
Note first that the piece is not about zacusca.net itself. It's saying 'You should go out of your way to build on a protocol. Even if the protocol is 'dead'. Perhaps I can clarify that.
Regarding Zacusca, I appreciate you explaining why it doesn't seem useful. First, it's not for everyone. Some people like reverse chron as an algorithm. Second, let me clarify how the pipeline works. But I think I explain the import/export poorly: - you export the feed addresses - you set up the categories - Zacusca continously polls the imported feeds, sorts them into the categories and exposes the categories as new feeds
So it's fire and forget. And you can keep your existing feeds as duplicates if you want.
mbanerjeepalmer commented on Ask HN: What API or software are people using for transcription? · Posted by u/indigodaddy
This wrapper for whisper.cpp https://github.com/akash-joshi/better-whisper
mbanerjeepalmer commented on What Elon Musk's personal feed on X looks like nytimes.com/interactive/2... · Posted by u/bookofjoe
This is a pretty poor article. It makes a bunch of unremarkable claims and somehow we're supposed to be outraged: https://bsky.app/profile/mbanerjeepalmer.bsky.social/post/3l...
Nice idea. Would be good to see a demo video on the homepage.
what about Substack's TOS?
I don't think Substack's terms are a problem: https://substack.com/pa
Regarding copyright I believe that this is fair use. It lets individual readers print their subscriptions. It's indistinguishable from them using a printer at home, except that it's delivered automatically.
But yes it's a grey zone. It's making a copy of someone's copyrighted work without their permission. (Remember it was technically illegal to load songs onto your iPod.) And so that's why the book product (which brings together all posts from one publication) is for authors, since I think that strays more towards publishing rather than mere printouts.
Aider! Use the editor of your choice and leave your coding assistant separate. Plus, it's open source and will stay like this, so no risk to see it suddenly become expensive or dissappear.
I used to be religiously pro-Aider. But after a while those little frictions flicking backwards and forwards between the terminal and VS Code, and adding and dropping from the context myself, have worn down my appetite to use it. The `--watch` mode is a neat solution but harms performance. The LLM gets distracted by deleting its own comment.
Roo is less solid but better-integrated.
Hopefully I'll switch back soon.