In this issue: Is Technical Debt Bad or Just Misunderstood? * Vaguely Information-Shaped Noise * Keep That Open-Source Coming * Learning From SAP Community Migration * Yet More Low-Code * 2024 Tech Trends Commentary
I don't really get the buzz about the new SAP Forum design. Shared pain is half pain as a German proverb is saying. I am supportive to the endeavor to align the developers world emotionally to their users when they have to work with Fiori bonding them closer together in the common agony of modern UX design.
But let's be honest, most of the the blogs.sap.com content was anyway a chaining of SAP marketing terms which could have come out of a large language model and a dozen commentaries beneath praising the authors fantastic work. Now "form follows function" developed an adequate home for it.
This is the future. Everybody who is complaining is simply to old.
There have been many marketing posts on SAP Community (and SCN before that) but it's been always possible to ignore the noise and to find rare gems worth reading.
If the future of SAP Community is that there will no longer be any gems, then maybe it's a problem SAP should address. Or at least, we can all learn from this how not to handle either migration or community relations.
Fun fact Tryton originated from an old fork of Odoo 15 years ago.
I don't really get the buzz about the new SAP Forum design. Shared pain is half pain as a German proverb is saying. I am supportive to the endeavor to align the developers world emotionally to their users when they have to work with Fiori bonding them closer together in the common agony of modern UX design.
But let's be honest, most of the the blogs.sap.com content was anyway a chaining of SAP marketing terms which could have come out of a large language model and a dozen commentaries beneath praising the authors fantastic work. Now "form follows function" developed an adequate home for it.
This is the future. Everybody who is complaining is simply to old.
There have been many marketing posts on SAP Community (and SCN before that) but it's been always possible to ignore the noise and to find rare gems worth reading.
If the future of SAP Community is that there will no longer be any gems, then maybe it's a problem SAP should address. Or at least, we can all learn from this how not to handle either migration or community relations.