3 ms·
I worked in architect roles for a while; I tried to make the architecture documents and systems match, it was impossible: I could not update the architecture do
by AdrianB1 5y ago
I worked in architect roles for a while; I tried to make the architecture documents and systems match, it was impossible: I could not update the architecture documents to match what was in real life systems because on the first internal audit my skin would be on a stick, I cannot make the systems respect the architectural decisions because management not only allows, but is actively pushing for cutting corners for many, may reasons and they over-rank me or simply build systems not approved in non-compliant ways. The architect is that person you ask for confirmation if you think they will agree and ignore the rest of the time.
In the end everyone pretends there is no problem, but everyone knows there is one, including the auditors that selectively raise a bunch of small issues just to cover themselves with "we told you there are issues", but nothing big enough to trigger any alarms.
Non-IT companies do compromise a lot in IT; they don't want to compete for talent (because they are "not core"), they don't invest the right amount in IT (because they "don't need") and at the end of the day they cannot live without IT, so they cut corners with top management blessing. If there would be a SOX-equivalent for IT systems, most CIO/CTO would go straight to jail, don't collect 200.