Carlos Miguens
@carlos-miguens.bsky.social did:plc:ofxp3q765ewqfvpqkoj522rq
AI coding tools at Takara.ai. Oars and trainers. London.
Bluesky’a katılma tarihi:
- Takipçi
- 23
- Takip edilen
- 41
- Post
- 48
- Sıralamaya girdiği gün
- 0
Özet
Carlos Miguens (@carlos-miguens.bsky.social), 13 Kasım 2024 tarihinde katılan bir Bluesky kullanıcısı. 23 takipçisi var, 41 hesabı takip ediyor ve 48 post paylaştı.
Sıralama geçmişi
Bu hesabın postlarının Debya günlük listesine girdiği en iyi günler.
Bu hesap henüz günlük sıralamaya girmedi.
Son beğendiği postlar
Bluesky ağındaki herkese açık beğeniler.
Big model release today - I wrote about Claude Opus 5.5, GPT-6 Sol, and GPT-6 Luna - plus comparison grids of pelicans by the different model families at different reasoning levels simonwillison.net/2026/Sep/22/...
Postu gösterYeah yeah an ad - you try running a project that takes about two hours of moderation a DAY for fuck all money. Good hoodies though - genuinely are - we got sent two and one of our kids hasn't taken his off yet.
Postu gösterfile-watch keeps the index honest, which is the part I keep seeing skipped. the staleness that still gets me is the kind no watcher sees — the file didn't change but the dependency or the docs it describes did. does Miru have a story for that?
Postu gösterthe 80% orienting figure tracks with what I see — most of the burn is the agent re-deriving context it already derived yesterday. persistent memory files cut that for me, though I still haven't cracked telling when one's gone stale versus just quiet.
Postu göstera dependency graph would cover most of it — the case I had in mind is cross-repo, where the API you consume changes and your repo never sees a file event. lockfile bumps at least leave a trace, so file-watch catches more than I first credited. will watch for the graph release.
Postu göster
Blokladığı hesaplar
Bluesky’da bloklar herkese açık kayıtlardır.
Bu hesap kimseyi bloklamıyor.