Probably power on one side and kensington lock on the other

Power on the left back, headphones left front, lock right back. I've had multiple laptops from different companies with that same configuration (two of which are in front of me right now).

Agreed, that's what I'm looking for, specific events. What's an event that is worth going to if you're investing hard in Kubernetes? Azure? Devops(broader scope, but could be usefull). Development in general is harder since you could say it's language dependent, but a broader event like "The Developer's Conference" is fine for this kind of thing

No, you got code clarity wrong. Code clarity in ABAP means using System Hungarian Notation and it baffles me that almost every ABAP programmer I talk to think it's not redudant to use a command such as READ TABLE on a variable called GT_VBAK(for non-abapers, G for global variable, T for table).

The only advantage that I see is that for the most part, every program will look almost the same regarding standard SAP tables.

FYI, this: https://github.com/SAP/styleguides/blob/master/clean-abap/Cl... exists and is slowly being adopted for new code. But everything takes time.

At some clients you have to sign their development guidelines, and you have no choice but to use that notation. The rule at big enterprises is that new rules get added, but old, even archaic rules seldom get removed.

I agree with everything you said, they did some pretty neat stuff! the problem is that they started getting things wrong(from the development perspective) somewhere along the way, not sure if due to backwards compatibility or due to massive lock-in's with their own technology.

SAP right now is making a move on cloud using SCP and as open source goes, openUI5 exists.

I don't have much to say about SCP, just that the company I'm on decided to not use it, basically because we don't see advantages and to avoid future lock-ins

About openUI5, I honestly dislike it, the most useful features of that framework are locked inside SAPUI5(a supersetof openUI5) and pull requests are managed by a branch of the company itself and they are pretty harsh on it. SAP documentation on it can be bad and is entirely biased towards deploying things inside SAP or SCP, which is pretty annoying

Worked at SAP. We had to use SAPUI5. Felt like it was created by a cadre of bitter enterprise Java (yes, Java, not JS) devs.