It essentially is calling someone a communist supporter. In 1956 Hungry had an uprising against the soviet union (USSR) communist rule. The soviets used tanks to crush the revolutnaries swiftly and used a similar tactic in 1968 to quell similar events in Czechia. When members of the communist party of Great Britain showed support for these actions it became common in GB to refer to them as tankies referencing the attack on hungry. The term has now expanded its use from exclusive to brittish political discourse to more global/universal label for a sympathizer to opressive communist regimes.

From what I heard mastodon is formatted more like twitter whereas lemmy is more like reddit.

Because, at least from my software dev perspective, if upper management realizes how easy it would be to make someone on the team a “team lead” pay them a smidge more and then use metric tools to make sure stuff got done there would be no need for middle managers.

I work for a fortune 500, tons of beauracracy, and the people always moaning about people being in the office are most often the least useful people in the building. Lording over people’s cubes “keeping tabs” is seen as a way to tell their bosses they are valuable.

Ive said it so many times to my boss who is on my side and has fought for me to WFH: “If I stop working you will know it instantly, things won’t work and besides theres an entire dashboard I have to self report my progress to which again I can lie on for a bit, but will be obvious if I do so longer than a week”.

There’s also another factor of the sunk cost fallacy, many corps own buildings or are on long leases, leaving them empty looks like a massive waste of money even though tbh leaving them empty by my assessment would actually save them money.

One issue I see is reports as recent as a month ago of people bringing an instance to it’s knees with a python script on 1 desktop computer. It’s one thing to ask for more instances and investment into the hardware to run them from more people, but it’s another thing not realizing that the code itself is heavily under optimized. For now, and you can see this everytime there’s an outage via the atlassian uptime tracker notes, server owners are throwing more resources to bandaid issues.

I myself am currently running an under optimized application for my company, we are using 4x the amount of money to run it as what it’s meant to replace currently. At a certain point even throwing the kitchen sink at problems stops working.

Lemmy’s code needs to mature more, but im excited about the future for sure.