My intuition was clear, it's made from a Japanese company! While the style is of course inspired on old Japanese games, the clear clue was "SNS" (confirmed by visiting the company link). If the authors are here, this is an example of wasei eigo not used at all in international English, like "salary man" or "office lady".

Relevant: https://ell.stackexchange.com/questions/10624/is-sns-social-...

Mandatory only to transfer to the new role, not for remaining employed. However, the program this person was in was finishing, so it was either take that or stop working there...

There is a schema that I've seen used in Nestle which is quite bad TBH: they offer a course that you have to pass for a position this guy was trying to get to. This training course was fairly long (4 years) and expensive for an individual, however the company would pay for it. BUT only on the condition the student/employee would finish it and stay in the company for at least 1 more year.

Now I hear you, they cannot force you to stay in a company (slavery laws and such). Well, the way it was structured legally is that Nestle was loaning money to the individual for Nestle's course. Then the debt would disappear as long as you stay the right amount of time. Oh, and also it was mandatory to take the course for the role this guy was trying to transfer to.

Of course, the employee would study on the side while working the normal fulltime job and even get complains for missing 2 days for the tests.

If I recall correctly (but don't trust this paragraph so much), the training was internal but it was preparing for 2 external tests (once every 2 years).

I agree about those statements, just curious since that was probably the most important concept I had to learn about "advanced" React.

Is React.memo comparing deeply/recursive or at least deterministic JSON.stringify comparison? Or still going for shallow comparison?

Maybe when my Japanese gets better (I'm learning!) and I've been here a bit longer (don't want to seem a job-hopper, specially in Japan).

Oh, I am great now. While it's not fulfilling, I have a fairly relaxed timeline (since it's the same deadline as the back-end) so I've done some learning, refactoring, cleanup, and extensive testing without any overwork.

The project is new, so he has to create those 10 microservices from scratch. Someone is helping out managing the infra, but still there's quite a big burden on the dev.

I think some optimal solutions might be to put a manager/dev lead in the middle to help out, let the team self-organize properly (cannot do that though since it's finance) or hire more devs. All of those would take months probably.

They wanted the back-end guy to be only 50% of his time in this project and the other 50% in another project initially! Luckily they understood it didn't make any kind of sense at some point. Not that now it makes more sense, but...