
Kimi K2.5 1T runs on 2 M3 Ultras with mlx-lm in it's native precision. It's actually quite usable. Here it's making a space invaders game. Generated 3856 tokens at 21.9 tok/sec using 350GB per machine. Thanks to @kernelpool for the port.
kulesh
3.2K posts

@kulesh
Mostly reading; sometimes tweeting. (Personal Account)

Kimi K2.5 1T runs on 2 M3 Ultras with mlx-lm in it's native precision. It's actually quite usable. Here it's making a space invaders game. Generated 3856 tokens at 21.9 tok/sec using 350GB per machine. Thanks to @kernelpool for the port.


@cramforce i really don't get why everyone is saying being a manager of people is like being a manager of agents


sneak peak of the new pi.dev no tools mode. you're gonna love it. you can try it with `pi -nbt`. enjoy!

This is a VERY good take and observation from @levie It feels to me that FDE roles could be replacing what were consultant / solutions architect & similar roles 2010-2022 (where many many new grads and early career devs were hired)



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.


UUID v4 collisions are less rare than you think 💣

Tessa's quality of life has improved a lot with some nagging.

With the model's simultaneous speech capability, Horace has gotten a lot easier to work with recently.


