π¨ π‘ππͺ: The Champions League Final has been PAUSED for a water break due to the extreme HEAT!
It's currently 24 degrees in Budapest! βοΈπ₯΅
@iamsahaj_xyz Don't remember who it was but someone said for Opus when it got 1M context that it's just the same as it was before as soon as it goes over 150k, so I compact as soon as it hits that point.
open sourcing Marlin-2B π
a tiny VLM to extract structured information from videos
Marlin is finetuned for two questions devs want to ask in their videos: what is happening, and when?
Best open model in its weight class, competitive with Gemini-2.5-flash at only 2B params π§΅
nth time pro players have to clarify their statements because of HLTV journalists clickbaiting everyone
I wonder if this has cost anyone their contract or reputation before
Instead of only reading this title or this post (as most of the people do), I would suggest to people to actually watch the entire podcast. I said and I explained many more things compared to what you see in the title and it will be easier for you to understand what exactly I wanted to say :)
I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.
I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).
It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.
The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.
We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.
I worry.