If you're only willing to work 100% remotely then you are competing with everyone in the world. Melbourne, where OP lives, has quite a few developing markets within a few hours of timezone offset. This is especially true of MNC with a strong presence in APAC.

And whether true or not you’re also signaling negative worker traits.

All low engagement employees want to work remote. But not all remote workers are low engagement. How do you properly position yourself?

'Negative worker traits'? - please explain what you mean by this

I suspect he means things that HR thinks are important but aren't.

They are signaling they aren’t a good worker. For example, “I really hate to wake up in the morning. Is it ok if I work from 11 AM - 7 PM”?

Do you manage people? When they put their butt in a seat actually says nothing about their work ethic or productivity.

Feishu is Chinese Slack

Then don't hit on people. Go there with no expectations other than enjoying the activity, it makes you a better and more interesting person anyway. The people who get banned are the creepy ones who go purely for the sake of hitting on people.

The article misses it off but you can see the evolution of the sticker on the FamilyMart webpage: https://www.family.co.jp/content/dam/family/sustainability/t...

"steering rules" is a core feature baked into Kiro. It's similar to the spec files use in most agentic workflows but you can use exclusion and inclusion rules to avoid wasting context.

There's currently not an official workflow on how to manage these steering files across repos if you want to have organisation-wide standards, which is probably my main criticism.

It's like comparing a Fiat to a Ferrari

There are many licenses with mortality clauses but they are general not popular because the ambiguity and "supply chain risk" of having such a license in a dependency tree tends to limit adoption of any projects that use them.

They could definitely add a maker-checker process (similar to code review) for new versions and make it a requirement for public projects with x number of downloads per week.

I'd say the software is an asset more than the code itself, much like an interstate is an asset rather than the concrete that it consists of. The quality of the concrete impacts the depreciation (reduction of value) of the asset and how much operational expenditure is required to upkeep the asset which would again impact the asset value. There's probably also a risk management angle which should be considered.

When I buy a stock the seller gets the money. The money doesn't "go in to the stock market".

Question really comes to what does the seller do with that money? Buy some other stock? Buy some other asset. What fraction they actually spend to buy goods and services?