← Back to context

Comment by nwyin

6 hours ago

i think this take gets misinterpreted and misapplied. here are some other sentences to think about.

to become a good chef, eat a lot. to become a great producer, listen to a lot of music. to direct great films, watch a lot of movies.

these sorts of advices superficially soothe the reality that you're spending too much time consuming and not actually creating. or even practicing creation.

false dichotomy, no? critical consumption is an entirely separate matter than mindless consumption. great filmmakers watch great, historic films to learn technique, just like great chefs eat different cuisines to learn new elements of flavor. great music is often a delightful gumbo of genres, artists, styles that came before.

we're not talking about watching whatever happens to be on netflix.

personal taste is developed by... actively developing a sense of taste.

It’s more akin to.

Why aspire to become a good chef, if you don’t enjoy culinary experiences ?

Why aspire to be a director, if you don’t love watching movies and living those experiences?

Many people want to build great apps, but don’t want to to debug and read code. Just let codex rip.

  • I’ve been debating a lot of people on that last point.

    A lot of anti slop professors want to bring the debate back around to the mechanical process of coding. I think that’s misguided.

    To me, building software is about understanding the users’ needs, knowing what UI patterns work well, how to integrate into the larger platform ecosystem, and ultimately, solving the problems the users have.

    Making it about debugging arcane, temporary idiosyncrasies in the platform, 3rd party tools etc is like telling writers they should typeset their own book on a printing press.