It’s September! The kids are all back in school, the leaves will start turning colors soon, and your boss is sure to give you that huge raise you’ve earned any day now. We daresay you deserve to enjoy some Boring Enterprise Nerdery, instead of cleaning up the giant mess your inbox has become.
Sep 15, 2023·edited Sep 15, 2023Liked by Jelena Perfiljeva
Yeeeeeeeeeees! Finally we can break up the monolite and push everything into the cloud!
Today we had a wonderful events of the benefits: We had an meeting with developers of a in-house-add-on which was developed the spearhead enshitifaction of SAP technology called CAP. The never-finished-but-always-unstable add on is supposed to check if an PP-order is already set technical completed before processing in the add on. This used to be two lines of code (one select and one for checking sy-subrc). Not anymore with the power of cloud: Define a service in ERP to provide the information, define some classes and method to read everything nicely with a CDS view, publish the service in BTP and finally it can be accessed from our CAP add on. But only when the PO puts in the backlog and sprint is done. Next year.
Elegant! Easy! Scalable! Cloud Ready!
Development effort increased by 3 orders of magnitude, execution speed decreased (estimated) by 5 orders of magnitude, number of points of failure increased not estimetable and complexity increased by *out of range error* orders of magnitude!
I am really, really looking forward to see the test class for this functionality! Will be beauty!
What a win for the developers! Never go out of work anymore!
Sep 14, 2023Liked by Paul Modderman, Jelena Perfiljeva
"traditional ERP systems (and the people and processes that run them) are built around the idea that stability is king above pretty much everything else"
That's probably a key differentiator between these and odoo (and other new systems in that space probably), they don't shy away from big changes.
You are spot on. Enterprises take managing risk serious to an otherworldly degree, and I imagine, leaving aside everything else, pull requests like that would scare the big potential customers away.
Sep 22, 2023Liked by Paul Modderman, Jelena Perfiljeva
This was (one of) the reasons the Agile methodology took so long to take in SAP world. You could spend months convincing management to at least allow read only stuff (ABAP reports, data extracts, SQnn changes etc) to be imported into PRD on a weekly basis.
Then one of them brings starts chewing all the disk space, or DB or CI CPU, and you're back to square one (because no one tested against PRD sized data volumes).
It's one thing to say Developers should test better, but I saw so many systems where the only place to test against PRD sized systems was to run in PRD.
It was the 2nd or 3rd consequence of business decision, and the business often abdicated responsibility for the trade-offs.
My apologies to those who were misled to believe that SAP event story would be about SAP event mesh and such. If it’s those other events you’re interested in, then take a look at this story from issue 9: https://boringenterprisenerds.substack.com/p/the-boring-enterprise-nerdletter-9-women-s-day-python-gooddata-sap-event-mesh-carbon-footprints-1054130#%C2%A7smash-that-sap-event-mesh
Apology begrudgingly accepted. Extra forgiveness can be gotten in exchange for cookies.
Yeeeeeeeeeees! Finally we can break up the monolite and push everything into the cloud!
Today we had a wonderful events of the benefits: We had an meeting with developers of a in-house-add-on which was developed the spearhead enshitifaction of SAP technology called CAP. The never-finished-but-always-unstable add on is supposed to check if an PP-order is already set technical completed before processing in the add on. This used to be two lines of code (one select and one for checking sy-subrc). Not anymore with the power of cloud: Define a service in ERP to provide the information, define some classes and method to read everything nicely with a CDS view, publish the service in BTP and finally it can be accessed from our CAP add on. But only when the PO puts in the backlog and sprint is done. Next year.
Elegant! Easy! Scalable! Cloud Ready!
Development effort increased by 3 orders of magnitude, execution speed decreased (estimated) by 5 orders of magnitude, number of points of failure increased not estimetable and complexity increased by *out of range error* orders of magnitude!
I am really, really looking forward to see the test class for this functionality! Will be beauty!
What a win for the developers! Never go out of work anymore!
Ha.... Seems to be missing /s at the end.
I feel your pain, as a developer. :)
"traditional ERP systems (and the people and processes that run them) are built around the idea that stability is king above pretty much everything else"
That's probably a key differentiator between these and odoo (and other new systems in that space probably), they don't shy away from big changes.
Can be a bit unnerving to find these kinds of pull request as an integrator: https://github.com/odoo/odoo/pull/78857
You are spot on. Enterprises take managing risk serious to an otherworldly degree, and I imagine, leaving aside everything else, pull requests like that would scare the big potential customers away.
This was (one of) the reasons the Agile methodology took so long to take in SAP world. You could spend months convincing management to at least allow read only stuff (ABAP reports, data extracts, SQnn changes etc) to be imported into PRD on a weekly basis.
Then one of them brings starts chewing all the disk space, or DB or CI CPU, and you're back to square one (because no one tested against PRD sized data volumes).
It's one thing to say Developers should test better, but I saw so many systems where the only place to test against PRD sized systems was to run in PRD.
It was the 2nd or 3rd consequence of business decision, and the business often abdicated responsibility for the trade-offs.