Full Width [alt+shift+f] Shortcuts [alt+shift+k]
Sign Up [alt+shift+s] Log In [alt+shift+l]

Improve your reading experience

Logged in users get linked directly to articles resulting in a better reading experience. Please login for free, it takes less than 1 minute.

More from Made by Ollin

Bare-bones Diffusion Models
over a year ago 35 votes
Maple Diffusion

I ported Stable Diffusion to my phone

over a year ago 39 votes
Game Emulation via Neural Network
over a year ago 35 votes

More in AI

AI Roundup 117: Google Killer

May 9, 2025.

2 hours ago 1 votes
Cheaters Gonna Cheat Cheat Cheat Cheat Cheat

Cheaters.

3 hours ago 1 votes
”Everyone is cheating their way through college” with GenAI. Who should bear the costs?

Society is once again left holding the bag

yesterday 1 votes
OpenAI's $3B Bet

Unpacking OpenAI's latest acquisition of Windsurf.

yesterday 1 votes
How projects fail at large tech companies

How do projects fail at large tech companies? As I’ve said many times, failure means executives aren’t happy with how the project turned out. At healthy companies, that typically means that a sensible engineer wouldn’t be happy either, because the project didn’t work or users hated it. But what actually causes the projects to fail? I’ve seen a lot of projects go wrong - both up close and at a distance - in the last ten years. Here are the main reasons why. Doomed from the start Lots of projects fail because there’s no way they could possibly have succeeded. In American law, some cases get dismissed at “summary judgment”: even if the plaintiff succeeds in proving everything they aim to prove, it still wouldn’t add up to demonstrating enough illegal activity to win their case. At tech companies, some projects are like that: even if the plan goes off without a hitch, the project is still doomed to fail. Some doomed projects begin with over-ambitious plans. For instance, an executive…

yesterday 1 votes