Software engineer and farmer living in rural Japan.

If you’re looking for a remote senior software engineer (most recently golang, but I’ve worked in a little bit of everything in the last 20 years), I’d love to hear from you. Japan PR, Canadian and US citizenship. Native English speaker, proficient Japanese, learning Norwegian (now between A2 and B1, though listening/speaking is lagging a bit due to lack of chance to practice), and some very rusty German and French I could get back to speed on.

  • 0 Posts
  • 6 Comments
Joined 5 months ago
cake
Cake day: April 25th, 2026

help-circle
  • If a company wants to get rid of a permanent employee, they have very limited tools when it’s non-consential. If they claim it’s financial, they have to (in theory at least) prove that to unilaterally dismiss and that can come with the burden of freezing hiring and other things.

    To unilaterally dismiss otherwise, they need to prove gross/malicious bad conduct, performance problems (this still requires a long PIP process), or reassign the employee somewhere and have the employee refuse. For the last one, it can’t legally be too onerous to on the employee, but case precedent is hit or miss if it makes it to court. As I understand, most prefer to settle out of court and pay the employee to go away.

    In my mind, layoffs are for downsizing head count rather than firing which is targeted to that employee.

    As I understand it, certain numbers of actions to reduce headcount can also trigger things like hiring freezes, but I don’t know much about that.



  • when the original dev leaves and nobody understands the code

    In my experience at work, no one cares about this. They assume the AI will be able to get there with enough tokens/time with the help of the human at the other end. They have done this and decided it was good enough.

    Meanwhile, people like me who don’t use AI coding agents and are PRing and modifying the code are having a hell of a time.