Category: Architecture. A formal description of the system
Architecture is a formal description of the system. Also of components of which system is made. In every modern enterprise, IT Architectural roles are wide and varied. Most importantly, here you might gain some useful insight into the creation of architectures for all sizes of businesses, systems, technologies and software too.
By no means do not hesitate to leave comments. In case the nature of your contact request is commercial please do mail us using firstname.lastname@example.org
Here is why. It seems Microsoft marketing has overwhelmed the target audience with dozens of made to be equally important Azure “services” (for the lack of better word). The “full Monty”: Posters, charts and animations. It is enough for Azure newcomer (developer or decision maker) to make and keep her dizzy, instead of producing focused and relaxed visitor, when entering the Azure yonder.
There are organizations making a mistake of not clarifying that one. Alienating in that oversight, a lot of good architects. An illustration? To illustrate this “knot-weed of legacy thinking and contemporary errors”, that can grow out of fertile misunderstandings of architectural roles in a real-life organization, perhaps this might be one sobering example. Reading this amazing (hilarious?) job description, one might think, for a single person, even “Neo” has no that much powers, as they ask from a poor architect.
But it might contain some pieces of information that might come handy to more than few CxO ‘s right now. Especially if the said CxO ‘sare given the responsibility to “own” the IT landscape in some medium or large organization. Approx 50 seats onward, complexity depending.
In this context, and perhaps because of this post, I might be called a bit of a pessimist., which is calling himself a realist.
Side note: Perhaps looking for good copy/paste opportunity? Click here for your required dose.