I’m sure y’all find these things just as useful as I do. They don’t make us lazy, they make us efficient. I know how to make a pattern. I know how to draw a curve with a Pen Tool. I know how to convert SVG into JSX. But using a dedicated tool makes me faster and better at it. And sometimes I don’t know how to do those things, but that doesn’t mean I can’t take advantage. Fake it ’til you make it, right?
Reminds me of a little feature I like in Notion where if you type dash-arrow (like ->) it turns into → — but intelligently — like it doesn’t do that with inline code or a code block.
On one side, an army of developers whose interests, responsibilities, and skill sets are heavily revolved around JavaScript.
On the other, an army of developers whose interests, responsibilities, and skill sets are focused on other areas of the front end, like HTML, CSS, design, interaction, patterns, accessibility, etc.
The form and possibility of the "modern infrastructural ideal" is increasingly under threat, as cracks (sometimes literal ones) show up in our bridges, our highways, our airports, and the nets of our social welfare systems. For these and other reasons, broken world thinking asserts that breakdown, dissolution, and change, rather than innovation, development, or design as conventionally practices and thought about are the key themes and problems facing new media and technology scholarship today.
Attached to this, however, comes a second and more hopeful approach: namely, a deep wonder and appreciation for the ongoing activities by which stability (such as it is) is maintained, the subtle arts of repair by which rich and robust lives are sustained against the weight of centrifugal odds, and how sociotechnical forms and infrastructures, large and small, get not only broken but restored, one not-so-metaphoric brick at a time.