Funny, isn't it. They ruin API access and overcharge for it, so everyone scrapes, and in trying to stop that they ruin the product for the users, without whom it's worth nothing.
It's funny, I wrote it very much tongue-in-cheek of course, but as someone who grew up writing HTML and then CSS and using "color" all the time there's probably a little nugget of genuine pent-up irritation hidden in there somewhere.
I've been on both ends of 1:1s. For a manager, they seem great - a regular meeting, a chance for staff to talk about things. But they're not. They're window dressing. If you need the 1:1 to see what mood your staff are in, you're not paying attention. If you need the meeting for your staff to be able to tell you what they could do with to make their work easier, you're not approachable.
From the perspective of a developer, they are an unwanted interruption, and a great example of the kind of make-work that gets in the way of productivity. You'll waste an hour in a 1:1, plus whatever time it takes to get back to what you were working on, and that is time that you usually can't spare.
I made https://readability-score.com/ - a site for measuring the readability of text. It's been a bit of an accidental success, but it's proving to be a great project.
SEEKING FREELANCER - LaTeX nerd, remote is fine (I'm based in the UK)
I've been tearing my hair our with a LaTeX template generator and builder. I need help, while I still have some small coverage of my head. I'm looking for someone who knows their way around LaTeX, especially if they have worked with complex nested tabular layouts, UTF8 issues, and so on.