I don't get the `SCIM doesn’t really have anything to do with data retention.`; if SCIM store data to sync between diff. integration / backend / ERPs / tools it is possibly impacted by data protection law like GDPR and co.
I believe that Eng. Manager and HR are mostly at fault for it, confusing seniority and familiarity as creating and giving higher title to keep people without doing the requirement part of the job: accessing the title, drawing a ladder linked to a skills matrix.
And then one authors of the book state: "if you know nothing about Scrum, implement everything as in the book, otherwise adapt to the situation and the team. If not you will surely fail [...]"
But being "Scrum.org certified PSM", how do you see your colleague from scrumalliance.org?
Like digitalization? Like Solar Panel building (in 2022 like 80% where imported)? Or like in the past about credit cards? ("we don't want plastic money" moment)
> Like renewable energy? 1st quarter 2024: 58,4% electricity from renewable energy. Up from 48.5% last year.
> I call this approach the "API database architecture"
Why people can't search for an existing term before creating a new one, it just add confusion into bucket which already contains "DB as API", "DB over API", "DB 2 API", "DB 2 REST", "DB low-code API"
It's more lack of "second thoughts" skills and possibly lack of State of Art and Decision Records; it is impossible to learn from failure if no trace exist or no one knows who did the decision.
Except that Viet. gov. isn't really good at putting directive..
During Covid, Vietnam had ~20 official applications to track vaccination and half of them could give travel/move certificate. And to not stop, every city & district did manage differently "inventory" from application, google form, excel over Dropbox to hand managed paper.
To finish, I don't even imaging how it could end; IT security speaking.
Not even sure AI could help about it, those software might run over system where the documentation never got out from physical paper support, maybe even hand notes.
Talking Win 3.1, it means using Quick C / MFC 1.0 and co. that I image no today AI would learn as deprecated.
Not even sure it is possible: Visual C++ for Win95 can't target Win3.1 (as I remember) meaning just building will be something.. Talking about CI/CD software working on this target kinda sum-up to 0.
I am already surprised that a company still support this target knowing that most dev tools for this platform are more found over enthusiast website rather than Microsoft itself. And having hardware for making these tools running too!
GraphQL got out just some years after BFF introduction, but even today BFF works nice while having a monolithic after that it brings a lot of hell / problems..
In distributed cases, BFF makes it a lot harder: aggregation or federation of API which are far way more complex subjects. (how to works with teams, who define data constrains, how to ensure data constrains are followed, etc.)