"Do Things that Don't Scale" by @paulg is a valuable lesson. But it's been misunderstood: you can't grow a company from one hack to the next. You need to first see the big picture, then start with small, actionnable objectives.
That is empirically false. The way the most successful startups have grown was "from one hack to the next." Because the founders were living in the future, their hacks seemed brilliantly prescient. But the big picture is only visible in retrospect.
-
-
From my experience, it sometimes leads founders to try to solve a small problem and wishing it will become a bigger one. I think it's better to imagine what the bigger problem is, and then coming up with the first step to get started.
-
I’m all for “coding late” but imo if you don’t keep an eye and have clarity on what will be strategic in achieving real scalability and anticipating issues you’re missing a beat.
End of conversation
New conversation -
-
-
"What we need to do is gather requirement, figure out the design, and then implement" is a statement I've heard so many times it makes me wonder if I'd be happier as a janitor.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.