I mentioned earlier the Architecture Journal n°15 from Microsoft, where the monthly focus is on the role and definition of what's an architect (in software development, in business roles or in systems). And a good initiative has been taken by the IASA (International association for Software Architects ) for trying to streamline the profiles, the core competencies that are needed etc. I believe they are right with that kind of exercise, because every job category needs some basic foundations - which are currently lacking in the software architecture world.
2023, the year of tackling your technical debt ?
Now that the year has started, it's a new dive in the day to day business, running from one client to another, shifting between priorities and deadlines. And what strikes me this year, besides the energy crisis (and the IT CIO costs cut paired to scarce resources), inflation, climate crisis, the Ukrainian war, it's the motivation to change the current status. Let me explain. Now that the majority of budgets has been granted, there is the recurrent pressure to 'do more, with less' (less people, less time to execute or to test, less money to get things done) and a need to address the legacy situation within IT departments. Tackling the legacy (being the old systems and solutions, already obsolete or nearly out of date) is not a walk in the park. You need to get an accurate inventory of what you have in prod (back office, front office solutions, hardware, storage, security solutions, development frameworks, security solutions, language used to code...or even your project
Comments