Corollary: Take a generalist observation about any type of creative work, stick "developer" somewhere in there, and act as if developers are unique and/or the o

Corollary: Take a generalist observation about any type of creative work, stick "developer" somewhere in there, and act as if developers are unique and/or the observation is new. Example: Not long ago I kept seeing some variation of articles about how meetings are bad for developers. Specifically developers. Guess what? This is true for pretty much any creative type work like writing, design, or any type of work that involves deep thinking. But it was treated like a revelation because it was about developers and made no case for all the other workers in the same boat. This piece? I could've written this 20 years ago as a freelance writer. Generally I refused to stick an hourly rate when dealing with clients for lots of reasons, not least of which that when I know a topic and it's in my wheelhouse I write very fast. (And if I struggle with a topic, it isn't on the client to pay for extra time...) My dad could've written it 45 years ago as a sign painter and pinstriper. He charged by the job / value of the work delivered, not by how long it took to do. (Insert Picasso anecdote about "but that only took you 30 seconds," "yes, but it took me a lifetime to learn...") At the time his craft was highly valued, hard to learn, and the difference between a good sign painter or pinstriper and a bad one was enormous. If there'd been a Hacker News for his field, maybe we'd have seen the same thing. Then came vinyl signs...