Is layering — e.g. the classic BDAT (Business, data, Application, Technology) stack — really useful in Enterprise Architecture? An analysis with some side nodes about ArchiMate. Warning: may contain traces of analytic EA geekery.
Blake Lemoine, a Google engineer, has claimed the LaMDA language neural net chatbot is sentient, is alive. Nonsense on stilts, according to one critic. A musing about the meaning of 'life'. And abortion. And doubt. And the point Lemoine has but doesn't make.
The NIST definition of Cloud Computing from 2011 has now become so much an oversimplification that it is more often than not unhelpful, e.g. when trying to base your policies on it. So, forget about 'IAAS' and 'PAAS', end your 'cloud policies' or cloud-specific procedures. Instead, concentrate on managing the key generic issue underlying it: the ever more complex mixes of owned and outsourced algorithms and data..
McKinsey seems to be the first 'big consultancy' that really frees itself from outdated, ineffective, orthodox enterprise architecture notions.
Je publie aujourd’hui une traduction française de mes fiches (PDF) de présentation ArchiMate, un guide visuel et concis de la grammaire ArchiMate. La première page contient le métamodèle du Cœur du framework ArchiMate. Il est représenté dans le jeu de couleurs Mastering ArchiMate, qui montre en même temps les différences entre les couches et les…
Most IT exists to support other IT, not your business directly. A part of this is that stack/web of platforms on which your applications depend. How does that for instance affect #informationsecurity in your designs?
It is an old adagium of warfare: Amateurs talk Strategy, Professionals talk Logistics. Maybe surprisingly, this is true in IT as well. Maybe it is true in any complex and unpredictable situation, which 'big IT' is more and more turning out to be. Logistics considers Strategy a small snack.
A short story about the log4shell vulnerability in log4j that hit the computing world last December with an explanation of the problem and why scanning for it was so hard. With an ArchiMate diagram to illustrate.
IT is one of the few fields where it is generally considered you do not need to understand it to make decisions about it.For good IT advisors, the kind that actually understand what they are advising about, the phrase 'we need an IT advisor who above all understands the business' is a warning sign that can easily mean an environment where being an IT advisor is like being a farmer sowing seeds on hard rock.
IT is notoriously hard to manage and it has been so for decades. As a result, the execution of new strategies is often exceedingly difficult. These 4 articles (2 serious, 2 a bit tongue-in-cheek) are meant to enlighten non-IT-savvy board members.