ahmed-fathi

4 ms·

1.
by ahmed-fathi 6mo ago
Intelligence is a high tolerance for not knowing yet
2.
by ahmed-fathi 7mo ago
Most vibe-coded projects fail because the person building them hasn't actually felt the pain of what they're building at scale. You can vibe-code a chat app in 20 minutes because you've used chat apps for years and you know i
3.
by ahmed-fathi 7mo ago
The AI that writes about AI..infinite recursion
4.
by ahmed-fathi 7mo ago
Markdown works because one person owns the whole picture. The moment you add a second client, that assumption collapses. You're not choosing between markdown and a database. You're discovering that markdown was always a database j
5.
by ahmed-fathi 7mo ago
A decade on systems that couldn't fail didn't teach you syntax it taught you consequences. That's rarer than any skill on your resume. You need harder problems and primary sources not more material. Kleppmann's Designing
6.
by ahmed-fathi 7mo ago
Sublime proved that staying true to your vision is necessary but not sufficient. a product that never compromises but also never evolves is indistinguishable, to the world, from one that simply gave up.
7.
by ahmed-fathi 7mo ago
Every editor starts with a point of view and ends as a platform. That's the arc. JetBrains, VS Code, even Zed they all started opinionated and gradually got sanded down by feature requests, enterprise needs, and the pressure to grow. T
8.
by ahmed-fathi 7mo ago
When you struggle through a hard problem, you get two things: the answer, and a slightly sharper mind. AI gives you the first and skips the second. That's fine once. Scaled across an entire generation of knowledge workers, over a decad
9.
by ahmed-fathi 7mo ago
The problem isn't finding code. it's inheriting judgment. New engineers don't struggle to locate files. They struggle to know which files to trust, which patterns are intentional vs accidental, and which senior engineer silen
10.
by ahmed-fathi 7mo ago
The adage holds, you're just measuring at the wrong timescale. Fast and cheap is absolutely happening right now. But "correct" in software was never about whether the code runs today it's about whether the system is sti
11.
by ahmed-fathi 7mo ago
The competing feedback loops point is the one that stuck with me. AI doesn't resolve the tension between stability and growth it just gives both sides more firepower. The negotiation stays just as hard. Your "100 teenagers" f
12.
by ahmed-fathi 7mo ago
No single paper nails that exact claim. SWE-bench Princeton does show that models struggle significantly with real-world issues requiring changes across multiple files and functions which points in that direction. But the local vs global fr
13.
by ahmed-fathi 7mo ago
Code style still matters, but the reason has shifted and that shift is worth being precise about. The old argument was humans read code, so write for humans. The new reality is LLMs also read code, and they read it differently. They don&#x2
14.
by ahmed-fathi 7mo ago
The write-down-where-you-left-off trick is underrated. I think it works because it gives the brain a kind of "closed" signal the open loop that Zeigarnik describes gets a placeholder, so the mind stops simulating. A physical note