@jeantimex@threejs Bro, i thought it's true😅 This video depicts AI-generated footage falsely presented as behind-the-scenes filming of a disaster movie
Scrolling X can be mentally exhausting, it can also leave you feeling surprisingly anxious.
So I built a tiny tool for myself to filter out the noise.
Right now it just lets me journal and schedule posts.
Not sure where it'll go yet, so for now... I'm just using it myself. 🫠
After digging deeper into Ethereum's execution model,
I understand why it chose the account model over UTXO.
For simple value transfer,
UTXO feels more natural while the account model makes state management much simpler
2 major issues when automating upgrades of legacy projects with AI:
1. LLM tends to “approximate” fixes instead of strictly following rules.
2. When you add too many correction scripts, they start conflicting with each other and create inconsistent fixes.
Object pooling makes sense in game, but usually not in flutter/dart.
dart’s GC is generational and optimized for short-lived objects. Pooling can actually confuse allocation patterns and reduce GC efficiency.
sometimes “reusing objects” is worse than just letting them die young.
In V8, closure is a heap function object that references a heap-allocated (or optimized-away) lexical context, depending on escape analysis
So scope ≠ lifetime.
One of the biggest lessons I've learned from AI coding:
Don't just tell the AI what's broken.
Tell it why it's broken.
Otherwise, it'll keep fixing surface bugs instead of the actual problem..
Bug reports are helpful.
Root cause analysis is even better.