That’ll show ‘em! Never write tongue-in-cheek blogs or else random weirdos who will never meet you will write you off as a candidate for an engineering team that doesn’t exist and that you don’t want to join in the first place.
"I made that" is the ultimate statement of pride in work. Taking that away is a really awful anti-pattern in management. Let your people be proud of their contribution, and equally proud of the product of the team. The work of a team is the sum of the contribution of all members.
> a reasonable exaggeration in many circumstances
I find people who take credit for the work of the team to be a lot worse than people who take pride in their contribution to the team.
But if they use the same language to describe the entirety of a team project, not just their contribution, as "my doing" alone, that often crosses a line into toxicity in the ways you mention in your second paragraph.
> . You can paste source code directly into your Markdown document without any changes, and it will appear as expected in the rendered HTML. That’s my doing.
It makes it sound like the author of this blogpost actually did the change, while in reality they suggested the change. Of course it's good to suggest something, and even nicer when whoever you suggest it to implements it. But I'd never claim "that's my doing" after suggesting any features/fixes.
A bit like writing an email to Apple suggesting something, then they do that thing and I wrote a blogpost saying "That's my doing, I was there first. And you’re welcome.". It just doesn't taste well.