Architecture

Green IT series — Article 4/4 Two years ago, as part of a CSRD compliance programme, I was handed a non-functional requirement. It came down to a single sentence: the solution must make it possible to have indicators for assessing its environmental impact during operation. An environmental requirement, written in black and white, in a document that binds design. On paper, that is a win. In short Three words are enough to empty an environmental requirement of its force: during operation excludes manufacturing, which is to say the heaviest item of all. What is already manufactured is already paid for. The only remaining variable is lifespan, reuse and decommissioning — which is where the circular economy of IT becomes an architecture subject. Regulatory pressure has receded; the footprint has not. An organisation that has not prepared the ground will find itself at exactly the same point when the demand returns. ⎙ Imprimer / Télécharger en PDF Three words that empty a requirement Let us read it again, because everything turns on how it is worded. ...

Green IT series — Article 3/4 I have a weather station at home. It gives me temperature, pressure, humidity and the variations of the last few hours. With that, I have a fair idea of tomorrow’s weather — and if I am unsure, a dozen outlets publish the forecast for free. And yet the question of tomorrow’s weather is put to generative AI thousands of times a day. Systems which must analyse everything before answering. ...

Green IT series — Article 2/4 One day, an IT department is asked to measure the carbon footprint of its application portfolio. The request is legitimate, the sponsor is solid, the deadline is regulatory. And that is when it emerges that the number is out of reach. Not because the method is missing — because the data it would have to be applied to was bulk-updated some years ago, according to a rule nobody remembers the content of. ...

Green IT series — Article 1/4 A perfectly cooled datacentre, running workloads no one consults any more, will post an excellent PUE. That is the whole problem. And it is only the visible version of a much wider paradox. In short PUE measures the efficiency of the envelope, never the usefulness of the computation — and the same illusion plays out at organisational scale, where a green programme coexists with projects that have no reason to ever cross its path. Enterprise architecture is not there to constrain choices or arbitrate between visions. It is there to make the whole coherent — provided it sits in the right place, with the right levers. Sobriety and the circular economy of IT are not programmes running alongside the value stream. They are quality attributes within the value stream. ⎙ Imprimer / Télécharger en PDF A flawless indicator for an absurd system Let us start with the tool, since the tool is what gets brandished. ...

In short Jack of all trades, master of none: that hire has never delivered Architecture gets decided the moment the org chart and job descriptions are written In the age of AI, the mistake costs more: the real scarcity isn’t model mastery, it’s knowledge of the business being assisted ⎙ Imprimer / Télécharger en PDF Cloud architect. AI architect. DevOps architect. Integration architect. Tomorrow, no doubt, agentic architect. Every technology wave demands its own totem, and the organization complies — a role, a job description, a line in the org chart. ...