Channels
administrivia
announcements
bot-dark-forest
devlog-together
in-alberta
in-boston
in-germany
in-israel
in-london
in-nyc
in-ontario
in-seattle
in-sf
in-socal
introduce-yourself
linking-together
of-ai
of-end-user-programming
of-functional-programming
of-graphics
of-logic-programming
of-music
present-company
random-encounters
reading-together
share-your-work
thinking-together
two-minute-week
wormholes
Title
k
Kartik Agaram
04/29/2022, 5:03 PMI've been rereading https://www.bloomberg.com/graphics/2015-paul-ford-what-is-code during my latest bout of introspection. It annoyed me out of all proportion when I first read it (even though I could and still can appreciate the craft that went into it), and with the benefit of hindsight (and having joined this forum 3 years later) I think I understand why: it's unabashedly about the present of software, and by nature that endeavor makes a virtue to newcomers out of how things work today.
On the other hand, I argued the opposite direction over at https://futureofcoding.slack.com/archives/C5T9GPWFL/p1645838782428059?thread_ts=1645811249.437739. So it seems to matter how vehemently I feel about the thing being taught to newcomers, whether I consider it important or irrelevant frippery.