I guess since fable has learnt deeply about 10+(maybe 100+) popular programming languages, it can just easily reason about the new 101st programming language.
It is almost happening in a different way, for automating physical labor, some companies are collecting data by making people wear camera on their heads
The Indian workers training AI robots to take their jobs
I follow this approach and still get the same merge conflicts coming repeatedly while doing rebase.
Let's say in my feature branch in the first commit I change a line in a file which also gets changed in the main branch. Then I have done 3-4 change commits doing changes in the same file. Now while doing rebase, I will have to resolve this conflict 3–4 times again and again while git re-applies commit one by one, during rebase.
I think I get this sometimes even if rerere is enabled, I am doing rebase using Intellij though, so maybe rerere doesn't get used here somehow or maybe diff context changes, so rerere is not applicable.
Leaving the place you have lived your whole life, the place where your family and personal life is and going to another country for work for 5 to 10 years will destroy the past life they had.
After 5 10 years that person will almost become part Saudi due to living in another country. And after he comes back no one will be that close, even close family members will feel something different due to the person being away/(out of physical touch) for 10 years
Similar thing applies to SAP ABAP. It is like Java from a parallel world, where the accumulated cruft for maintaining backward compatibility is 3-4 times more than Java. It also like a low code/no code environment where the language, the UI, ABAP IDE etc is tightly coupled to one another. Like Java, it has continued to add more language features with time, but the legacy code using old constructs is still there in the codebase of many of the orgs.
Initially and up to some extent still now, it is verbose and wording wise, very similar to COBOL, then somewhere I guess in the late 90s, OO paradigm wave came in, and it had "OO ABAP" with classes and methods. Now cloud wave is influencing it and ABAP now has a new cloud flavor "ABAP for cloud" where most of the old constructs are not supported.
Spring/JPA and other related APIs has lots of stuff to learn. It is like the modern Java EE. It will require at-least 50–60 hours to learn basic stuff and their history. Learning history like how XML configuration works might be required because some codebases might be still using it.
Otherwise, just learning spring boot, assuming some things happen "by magic" will take fewer hours.
Yes, I was talking from the POV of employee. If I am going through the trouble of setting my own company and doing contracting job which involve similar work, then to maximize money for work, I would be thinking of offering some SaaS service via the company. If so many companies want a similar thing, then there is some gap in the market.