Raw hours
On Twitter yesterday, @RJoads asked me how I got good at styling (CSS).
I replied: "Raw hours. I’m obsessed with how things look and feel—probably more than the median engineer. Mind you, this has not always been a positive. I’ve been wildly distracted for hours and hours on the smallest items, things that truly do not matter to the business. But that’s how I’ve gotten better."
If you want to get really good at something, forget about shortcuts. You simply have to inject a ton of raw hours.
"Work smarter, not harder" is a common refrain these days—particularly in sophisticated circles. The thing is, for most people I think it’s bad advice. My experience learning to code has suggested you have to work hard before you know how to work smart. No substitute for raw hours.
It’s similar to what Brian Armstrong says: "If you’re pre-product/market fit, the best advice that I have from that period is: action produces information. Just keep doing stuff."
People with limited experience are similar to startups pre-product/market fit. Of course you should aim to work smarter! The catch is that you have to work extremely hard in order to know HOW to work smart. You must first go down dozens of dead-end paths to know where the smarter paths lie.
The second catch is that in order to be able to inject a ton of raw hours in a natural, sustainable way, oftentimes you need to be OBSESSED. Otherwise - you’ll be banging your head against the wall year after year. Some people are so dogged they're able to do it. But this is exceedingly rare and probably not worth aspiring to.
"It's hard to do a really good job on anything you don't think about in the shower." - Paul Graham