maybe we'll be able to switch off the downport step, making the execution run a lot faster

sorry 😅🤠

the ##NEEDED in line 18 annoys me the most, as the variable is used in the next line

it looks like a promptfluencer 🤪

yea, the agents are clever enough to act on feedback provided by the linter

and act on unit test results too

#ABAP

SAP really needs to create more transparency as to what is exactly released on which version, and what/if there are changes

This is Flemming, he happily wears signs as a champ. 12/10

🤯

I'm sure customers have many enhancements in the worst category, which have had zero problems over the last 10 upgrades. Just looking at the technology(which is what the new whitepaper does), doesnt tell the full story regarding upgrade stability

keep the code at whatever level, just #keepTheCoreMoving towards a nicer setup. Ie. I find it more important to have an overview of what is missing vs. creating wrappers that is basically legacy before they are created

let me know if you'd like some input on setting up Continuous Integration

to find the real bugs. And not having to consider what is real or mocked code is one indirection less. Plus full/easy overview of what the database changes actually are.

Refactoring, if talking about Fowler, martinfowler.com/books/refact..., then its a prerequisite to do testing before refactoring. I also think testing is more important.

I like to do testing without dependency injection or the test double frameworks, test it all as it would run, then its easier