Jacob
145 posts


Just added in smol-audio: a reproducible NeuTTS Nano recipe for new languages. Want a TTS model in your own language?
- NeuCodec dataset encoding
- fine-tuning CLI + notebook
- Inference script
Change the phonemizer + dataset and train your own TTS model. Italian example includes a 300k samples/around 1000 hours of audio YODAS/Granary config.
English

@saararbel1 הדבר האחרון שמעניין אותנו זה לקום באמצע הלילה לדבג תקלה, מה שמעניין זה להתקדם כמה שיותר מהר. יש לנו מפתחים חזקים מאוד אז לא משנה איזה קוד תתן להם יחד עם קלוד יסתדרו (גם אני)
עברית

@eaglescode מעניין, איך אתם שומרים על mental model אחיד של הארכיטקטורה? כמה מהמפתחים באמת מסוגלים לדבאג תקלה באמצע הלילה בלי לבקש מהמודל להסביר להם את הקוד של עצמם ולהיכנס לפאניקה?
עברית

@DanielSmidstrup USA builds
China copies fast
Europe regulates
English

Codex usage limits have now been reset across all paid plans. Enjoy the weekend!
Tibo@thsottiaux
We found and fixed two issues that could explain this degradation of the capability of GPT-5.5 in Codex over the last ~ 48 hours. We are monitoring over the coming hours to fully confirm and I will reset usage limits this evening. Apologies and now is the time for /fast maxxing.
English

@0xglitchbyte Move fast and break things, the time is short and the work is endless
English

@eaglebuildz @dreamsofcode_io Yeah, just vibe-code unsafe Rust and expect segfaults
English

@dreamsofcode_io hot take:
code doesn't need to be readable and clean anymore with agentic coding.
new paradigm:
- just vibe-shit the code
- have enough tests written by ai
- have enough security checks done by ai
- make manual tests
nobody needs to read the code anymore.
English

The code is so bad though.
Like the worst Rust code I’ve ever seen.
Honestly it’s so bad I’m thinking of fully hand writing code again.
WebDevCody@webdevcody
Bun rewrite from zig to rust in 6 days. 1,009,257 changes. 6,755 commits. all tests passing.
English

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.
English

@rezoundous I use low thinking with fast mode on always, otherwise it's too slow (almost unustable IMO)
English

@charliermarsh Running an experiment where I do NOT restructure the project with uv (it already uses uv instead of requirements.txt) 😉
English

@themishra4402 Yes, we don't need much smarter agent, we need more affordable agents, they already gets the job done
English











