Deprecated: Use of "static" in callables is deprecated in /chroot/home/a40b7614/774635bdc8.nxcli.io/html/wp-content/plugins/moosend-email-marketing/vendor/moosend/website-tracking/src/Utils/Uuid.php on line 15 Deprecated: Use of "static" in callables is deprecated in /chroot/home/a40b7614/774635bdc8.nxcli.io/html/wp-content/plugins/moosend-email-marketing/vendor/moosend/website-tracking/src/Utils/Uuid.php on line 15 Deprecated: Use of "static" in callables is deprecated in /chroot/home/a40b7614/774635bdc8.nxcli.io/html/wp-content/plugins/moosend-email-marketing/vendor/moosend/website-tracking/src/Utils/Uuid.php on line 15 Deprecated: strtr(): Passing null to parameter #1 ($string) of type string is deprecated in /chroot/home/a40b7614/774635bdc8.nxcli.io/html/wp-content/plugins/moosend-email-marketing/vendor/moosend/website-tracking/src/Utils/Encryption.php on line 8 Deprecated: urlencode(): Passing null to parameter #1 ($string) of type string is deprecated in /chroot/home/a40b7614/774635bdc8.nxcli.io/html/wp-content/plugins/moosend-email-marketing/vendor/moosend/website-tracking/src/Payload.php on line 202 Blog – SoftwareArchitect.ca

Category: Blog

  • How Can I Practice Microsoft Azure?

    How Can I Practice Microsoft Azure?

    I make videos for a living teaching almost every aspect of Microsoft Azure to anyone who wants to learn it. And I really enjoy doing that. Just the other day, I finished recording a new course. And at the end of it, I was feeling a deep satisfaction about what I had created. 

    I won’t lie though. Part of the fun I have is using Azure itself. As a teacher, I have an excuse to create new compute, networking, and storage services repeatedly. I create them, I play with them, and I delete them. 

    I say all this to encourage you to do the same.

    You should be in the Azure Portal (or command line) – creating, playing with, and deleting resources. Do it once, and then do it again.

    You learn so much by using Azure hands-on.

    I can’t count the number of times where I go to do something, and it doesn’t work. Why didn’t it work? Why is Azure returning an error? Why can’t I find the exact feature or function that I am looking for?

    That’s when learning happens!

    That’s when I become a better teacher. I become a better teacher by playing with Azure myself and discovering the little hidden secrets.

    Isn’t It Expensive?

    Yes, it can get expensive. I sometimes pay $100s of dollars per month for my Azure bill.

    That’s a true copy of my Azure subscription invoice history for one of my subscriptions. 

    What usually happens is that I leave a service running longer than I expected to.

    Like recently, I started an Azure Bastion service. So I was using Bastion to access a private virtual machine running on one of my Azure Networks. 

    Bastion runs at $0.19 per hour. That’s $4.80 per day. Or $150 per month.

    Needless to say, after a couple of weeks, I relented and deleted Bastion. I’d need another solution to access that machine.

    How Do You Play With Azure Without Spending $100s?

    One option for you is to use a Free account. Azure gives you $200 to spend in the first 30 days. That costs you nothing, and you can learn a lot in 30 days.

    But the time runs out after 30 days, and you can only have one free account. Or you’re only supposed to have one free account.

    So what else can you do?

    You can purchase a lab package with access to Azure hands-on labs that come with the Azure resources you need to learn.

    My site, getcloudskills.com, sells packages of labs that include the time on Azure required to use them.

    What are Hands-on Labs?

    Hands-on labs allow students to practice what they’ve learned on their own time without having to rely on instructors or other resources. Students can use these labs as an opportunity to test out new skills before applying them in the classroom. In addition, it gives students more control over how much time they spend practicing each topic.

    How Does Your Hands-On Lab Package Work?

    When you buy the All Labs package, you get over 700 labs to choose from. That’s a lot! You can find labs on almost anything that you want to learn.

    Each lab has an expected amount of time to complete. So let’s say that we think it will take you 1 hour to finish a single lab. We give you an hour of Azure time (included in the price) to complete that lab.

    You can try each lab up to 3 times. So that means, you can spend up to 3 hours practicing the same skill, in this example.

    And there are over 700 labs. So this means that there are THOUSANDS of potential hours you can be spending learning Azure, AWS, Linux, and other skills.

    I can’t say it’s an unlimited number of cloud hours, but I can’t imagine anyone doing every lab and running out of attempts. (In order to make 2,100 attempts in a year, you need to be completing 7 labs per day!)

    Buy One Year of Labs for Azure, AWS, Linux, Cybersecurity and More!

    What I can offer you is a pretty good deal.

    For less than the cost of what I pay for Azure services in one month, you can get a whole year to play with Azure.

    This package comes with over 700 pre-built labs that you can follow along with. Some are basic labs, intermediate labs, and some are expert labs with very little guidance.

    For only $125, you get 700 labs with 1 year of cloud services to test them with. 

    Check out my site, https://getcloudskills.com/all-labs/ for the deal.

    I also have individual exams if you’re looking for more focused labs to specific learning requirements, that can be bought individually. Check out the site for more details.

  • Dale Carnegie, “How to Win Friends and Influence People”

    Dale Carnegie, “How to Win Friends and Influence People”

    In my last post, I mentioned that the key to landing a job once you have the job interview is to make people like you.

    I should have recommended the classic book, “How to Win Friends and Influence People“, by Dale Carnegie.

    It’s a 1936 classic. 85 years old, but much of the advice is still relevant. Again, I consider this a key life skill that will help you succeed in many areas.

    Six Ways to Make People Like You

    1. Become genuinely interested in other people
    2. Smile
    3. A person’s name is the sweetest sound in any language
    4. Be a good listener. Encourage others to talk about themselves.
    5. Talk in terms of the other person’s interests
    6. Make the other person feel important – and do it sincerely

    We’ve all had that conversation where the other person talked only about themselves the entire time. Their problems. Their life. Their issues. And on and on. Those are not great conversations. You do not go away from them happy, and you are often glad it’s over.

    Don’t be that person.

    In the job interview, of course, you want the other person to know you and get a sense of who you are and what you can do.

    But you want to do that in a way that doesn’t make them feel yucky like when you just talked to a self-absorbed friend.

    Ask them how they are doing. Ask them what’s the job like. Ask them what the key to succeed in the job and the company. Listen to the answers. Smile, nod.

    The Best Interviews

    The best job interviews I ever had were ones where everyone was smiling and laughing at the end. Not that it was meant to be a comedy routine, but where the conversation flowed freely and easily. And everyone felt at ease. Where people in the room could see where I’d fit in on the team, and see us all working together.

    Check out that book, if you haven’t. Look for courses on public speaking, and how to talk to strangers if you have anxiety around that.

  • Job Interview Advice: Make Them Love You

    Job Interview Advice: Make Them Love You

    Since I became a full-time trainer in 2018, I’ve been fortunate enough to not have to apply for any job in the traditional way.

    But, I’ve always considered myself blessed when it comes to landing the job in any interview I’ve ever had. Right from the early days of graduating from university, I found it relatively easy to walk into the interview and walk out confident that I had “nailed it”.

    After a few years as a developer, I was in a position to make hiring decisions myself. Over my career, I have reviewed hundreds of resumes, interviewed at least 100 people as well (maybe 200 even), and have hired dozens.

    I’ll talk about resume skills for landing a job in another post. I’ll talk about technical skills for landing a job in another post too. This post is about interview skills. This is how you conduct yourself to land the job.

    This is it. Here’s the secret to nailing a job interview:

    You need everyone in the interview to really like you when the interview is over.

    But Scott, It Sounds So Artificial!

    Being likeable does not mean being fake.

    It does you no good to have to put on a fake personality to get the job. So I’m not talking about doing that.

    But what you need to do, is find a way to let your true personality show proudly. If you’re quiet, you can project quiet confidence. If you’re reserved, you can project reserved confidence. If you spend your weekends going to Star Trek conventions dressed as a Klingon, you can find a way to express the geeky side of your personality.

    Don’t be fake. But don’t hide under the interview table either. Even if you really want to. You need to find a “you” that is the one that they want to hire for the job.

    Be Aware of the Energy You’re Projecting

    I’m not talking about crystals or aura here. But you do need to come into the interview with a certain energy and maintain it throughout. To me, this means:

    • Come in happy and excited
    • Dress well and be comfortable in your clothes
    • Greet each person you meet, ask their name, and say their name
    • Have good posture – sit straight
    • Pay attention and demonstrate an interest in the other person
    • Maintain energy and interest throughout the interview, but not too much
    • Be friendly, and put the other person at ease
    • Be able to engage in a bit of small talk – weather, traffic, the office they are in, etc.
    • Be able to read the room – detect what is working and what is not working
    • Every part of your body needs to be in tune with the rest – your words, your face, your body, your hands

    This is so important! Don’t neglect this. You’ll notice that nothing that I said above has to do with technical skills or experience, and some developers might scoff at that. If you believe you are qualified for the jobs you have been applying to, and have been landing interviews, but come away without a job offer – pay special attention to this.

    If you find any of the above to be outside your comfort zone, work on that. Watch videos, or take a class. Get advice from trusted friends who seem to have this figured out. Sign up to Toastmasters if you must.

    But you must find a way to be comfortable in a casual conversation with a stranger.

    Dress for Success

    I am not a fan of suits, but I’ve always had a good suit for job interviews. I never wear a suit to work, but wearing one to the interview is expected.

    Never come to an interview in a t-shirt in shorts. Or sandals. Save that outfit for your second week on the job. You are trying to impress them here.

    Be comfortable in your suit.

    I once interviewed a guy who had a suit on that he was “drowning” in. I am not sure if he borrowed the suit from his dad, or had bought the suit but never wore it. But he did not look comfortable in that suit. It was not impressive.

    He did not get the job – not because of the suit. But it stands out in my mind 10-15 years later.

    If you don’t own a suit, or don’t look good in a suit, find a dressy outfit that you DO look good in. A collared shirt and a tie are fine as long as you don’t sweat through the shirt. And depending on the place, you don’t even need the tie.

    But look at yourself in the mirror, and say “I look good in this.” If you don’t look good, don’t wear it. And again, no t-shirts.

    Find a friend who has great fashion sense and get advice on a good “interview outfit” and use that one for every interview.

    Show Up On Time

    Don’t be late. In fact, aim to be early. You can wait in the car, or in the café down the street until your appointment is almost there. Then you can stroll to the reception right on time.

    Make sure you’re still looking good. Hair combed, clothes all set.

    Another benefit of being early is that you have the chance to set yourself in the right mindset. Get rid of any nerves. Check the job description one more time, and be ready to tell them how great you’d be for this job.

    Be nice to everyone you come across – on the road, in the parking lot, in the reception area. The game starts far outside the building.

    Good Level of Energy

    Then when you meet the person you’re supposed to meet, smile. Be excited to be there, and happy to meet them. Ask them how their day is going. Tell them how nice the lobby is (if it’s nice) or how easy it was to get there. You’re going to have to do a bit of small talk. But the purpose is to establish a quick rapport with the other person.

    Focus on them for a bit. How long have they worked for the company? Demonstrate at least some level of knowledge of what the company does, and why they need you. You researched the company first, right? Good.

    Professional Meeting

    I feel a bit like your mother. “Don’t lean back in the chair. Don’t slump your shoulders. Look at the person who is talking to you. Smile.”

    There has been more than one person that I’ve interviewed over the years who came into the interview like a wet bag of potatoes. They just sat in the chair, with no energy. Not smiling. Their answers were one or two words to each question.

    Why did you waste my time today coming in for this interview if you don’t even look like you WANT to be here?

    Look like you want to be there.

    Use Your Words

    Your parents spent good money sending you to years of elementary and high school. Maybe even college. So, they’ll be very pleased to hear that you can speak in full sentences.

    Answer the questions asked to you. Try to avoid single “yes or no” answers if you can. (Unless the interviewer seems to prefer that.) Look at each question as a brief opportunity to sell yourself. Don’t push that too far, but better to make it seem like you’re the perfect candidate than not.

    Example question: “Have you ever had to use Java in a Windows environment?”

    Example answer: “Great question, John. Back when I was working at Vandelay Industries in 2019, we were moving a Java-based system from one environment to another, and someone had the idea to move from Linux-hosted VMs to Windows. I volunteered to test the system on a Windows environment and report back to the team in the next week. So I set up a Windows system and was able to get a Java environment running. There were a few tricky bits, as you must know, and so I can’t say it was easy but once it worked, it was working. I tested the system, ran our existing unit tests, and everything worked. I reported back to the team, and people were pleased. Several of the other developers believed that it couldn’t be done, but the tests came back all green. We ended up sticking to a Linux environment, but it was an eye-opening experience.”

    So in an answer like that, you aren’t just saying “yes” or “no”, you’re giving some background on your experience. Even though in this example, their experience is only 1 week in a testing environment, it tells the interviewer several other things about you. That you volunteered for the task, that you did what you said you were going to do, and that the rest of the team was impressed with your results. All good traits.

    Almost Never Say No

    Sometimes, an interviewer will ask you a question that you don’t have experience in, yet.

    It’s never good to lie – never. And never good to obfuscate the answer so that the interviewer thinks you said something that you carefully avoided not saying.

    But, when asked if I’ve ever done something, I never just say “no”. I always relate the thing they are asking about to something that I have done.

    Example question: “Have you ever operated in a high-availability environment?”

    Example answer: “In the past 10 years in my career, almost all of the environments I’ve developed for have been important to the companies business. While not true “high-availability” in the dictionary sense, we never want to see production have extended downtime. So there are a number of things we did to ensure that production was protected from downtime. And if they did, that the downtime was brief. I can tell you about them if you’re interested…”

    So you see, in this example, I did not have direct experience with the thing they are asking about. But I demonstrated that I knew what they were talking about, and talked about how the experience I did have was similar to the experience they wanted.

    Read the Room

    One skill that is worth developing, in life, is the ability to read the room. This is the ability to be aware of the feelings of the other people in the room with you, and particularly when those feelings change, and adjust your behaviors to compensate for that.

    One time, I was interviewing for a job with the government. The interviewers must have seen 10-15 candidates for this position, and they were cold as ice. They didn’t smile. They didn’t engage in any small talk. They didn’t make any eye contact at all. They had a series of pre-written questions in front of them, and they were writing down my answers on the form.

    That was my read on the room. I saw them as people who were probably a bit tired of what they were being forced to go through, asking the exact same questions to 10-15 people. And I was coming in late in the day, near the end of their day. Maybe I was even the last interview of the day.

    I tried to be friendly and warm. I tried to make them feel like they could trust me with this position. I would take the job, and they wouldn’t have to worry at all about managing me. Hiring me would make their lives easier.

    I had them smiling at the end. They were more relaxed. The energy that THEY were bringing into the room was HIGHER at the end of the interview.

    Of course, I got the job. When I left the room, I called my agent and told her that I probably got the job. And wasn’t surprised a couple of hours later when they made an offer.

    Conclusion

    Again, none of the above has anything to do with technology. With programming or technical skills. Or, with certification. It has entirely to do with projecting a good image during the interview. It’s about having good, positive energy. Someone that can get the job done. Someone that makes the employer want to hire you on the spot.

    Now if you’re not qualified for the job, your positive energy isn’t going to overcome that. But many companies will hire the right person who can learn the skills over the wrong person who already knows the skills.

    I’ve seen too many low-energy interviewees. Leaning back in the chair. Slumped over. Giving barely audible answers.

    Snap out of it. You want the job! Make them want to hire you!

    If you can’t do that, learn how to do that!

    The skill of being able to talk to strangers and make them like you almost instantly will serve you well throughout your life!

  • What I Like About Azure

    What I Like About Azure

    The world of technology is a big space. There are literally thousands of technical topics to choose from, to find something you can be interested in. Some topics are big, and some small. Some with a large community, and some with a small one. You don’t ever have to settle for working on something that bores you or that you hate. The world is so large, that you can choose to work on something that you actually like.

    I like Azure.

    Which is a good thing, because I have to think about it every single day. But why do I like it?

    The Power At My Fingertips

    The first reason may sound a bit strange. However, I can’t think of any suitable analogy outside of cloud computing for the sheer amount of things you can choose to do.

    Do you need a server? How big – you have 200 sizes to choose from? Here you go. A database? Which one? Here you go. More storage? Check. Networking in dozens of global locations? Check. Machine Learning models? Check. Firewall? Here you go. And so on, and so on.

    I could probably list 100+ distinct services that you can create within an Azure environment, but there are probably 1000. Literally, every computing service you can imagine is available to you. And every month, more are being imagined and invented.

    The Price

    How much would you pay for a powerful Linux server? Thousands? Hundreds? How about pennies per hour. Pennies per hour.

    Any company of any size can afford to run a small server in the cloud. They can experiment with some idea, or develop a new app, without wasting tens of thousands of dollars.

    Think of the innovation that is happening in small and solo-founder businesses! The things that are being created that were never going to be created if servers were not cheap.

    The User Interface

    I actually like the Azure Portal. Compared to what I have seen of AWS, I think Microsoft has done a better UI design of their platform that Amazon has. Not everything has to be “command line”. Having a pretty UI that makes it easy to do what you want to do counts for something, to me.

    The Community

    Microsoft has always done an amazing job at developer and community relations. Azure is fully part of the Microsoft culture in that respect. Microsoft has their online events (Build and Ignite), a community of MCTs, a community of MVPs, employees who are active in the community, and all sorts of friendly, helpful people that aim to help.

    I am not here to bash other platforms, but I have not seen those communities. I am not aware of them, and they seem to be smaller. I am willing to bet that the Azure (and Microsoft) communities are working at a scale and quality that the other competitors can only dream about.

    Innovation

    This probably shouldn’t be last, but if you watch some of the announcements coming out of Azure, you’ll notice that they are coming out with things that are not always playing it safe.

    For instance, I haven’t yet had a chance to play with Azure Quantum, but the idea of being able to run my computing workloads in a Quantum Computing environment is interesting.

    Microsoft is also pushing cloud services down to the “edge”, so that you can have Azure Machine Learning models processed on Azure devices in your own datacenter even.

    And not to mention the way they are using Azure Arc to intergrate Azure environments, with hardware you own, and hardware in other cloud computing providers.

    These are just three examples of innovation, but there are many more. Azure seems to be inventing new technology all the time. Instead of just being complacent with the platform that they have.

    Conclusion

    Well that’s it. These are the reasons I like Azure.

    I’m not saying you need to like it too, or that there are not great things about other platforms.

  • Regular Blogging Schedule

    Regular Blogging Schedule

    It is March 29, 2021, just after 12:30 PM. And I suddenly decided to start blogging more.

    I’m going to push myself to blog twice per week on technology, certification, and Azure-related topics.

    I can’t promise that every blog post will be long and amazingly insightful. But there is a certain peace that comes from writing. Allowing thoughts in your brain to form, come together, and then get expressed is a brilliant creativity exercise. And one that I should do more often.

    Creating videos is fun. Creating courses is fun. Interacting with my students on Udemy and in my Azure Facebook group is fun. And so I’ll simply have another outlet for my creative expression here.

    Of course, we’re talking Azure. So it’s not like I’m posting Ever Given-Suez Canal fan fiction. (I’m fully aware this moment-in-time cultural reference will go stale and be forgotten about next week.) But writing is creativity. Or at least, it should be.

    What I SHOULD do, if I was smart, is figure out to get GPT-2 to write Azure blog posts. But I’m not that smart. I’m going to have to use the organic matter inside my skull (my brain) to do this for the foreseeable future.

    The tone of these posts will be more conversational, and less formal. I hope you don’t mind. If you’re looking for really dry, factual content on Microsoft Azure, check out their Docs website.

    Alright, let’s do this!

  • May the Fourth Sale

    May the Fourth Sale

    I usually send these out closer to the end of the month.

    But I just had a look at the calendar. It’s May 3rd right now. May the 4th is tomorrow.

    <Cue the Star Wars-themed sale.>

    Now I’m still waiting to receive all of that cute Baby Yoda gear I ordered at the beginning of the year. I suppose that’s all delayed right now.

    But you don’t have to way to get the biggest discount on my courses. Everything I have for $9.99 or $10.99 each… right now.

    I just launched a brand new course on the Azure DP-200 exam, Implementing Azure Data, which is one of the exams required to get a shiny Azure Data Engineer badge!

    Or I also finally created the TOGAF® 9.2 Part 2 course, which is the second exam required to get fully TOGAF® Certified?

    I’m almost done upgrading my bestselling AZ-103 / AZ-104 Azure Administrator course for the latest beta exam requirements. I invite you to learn the latest on Microsoft Azure with me.

    All of my Azure and TOGAF courses are available for US$9.99 (or $10.99) using the coupon code STARWARS. If there’s a course of mine that you like, “apply coupon” and use the code STARWARS. Thanks. (This coupon expires on Friday, May 8.)

    And May the Fourth Be With You.

    (P.S. Hope you are safe, and doing well.)

    (P.S.S. Please don’t sue me Disney and Lucasfilm. Love your movies!)

  • Join the Beta Testing Club!

    Join the Beta Testing Club!

    For me, one of my goals for 2019 is improving the quality of my products across the board. Not that they aren’t great, but of course, they can be better.

    One aspect of that is having a group of people willing to get early access to the products and being among the first to view them. This way, I can find out quickly what is working, what I should do more of, and what can be improved.

    Requirements:

    • Not everyone will be accepted to be part of this group. Membership is limited in order to manage the beta/early access process.
    • You agree not to share any course coupons you receive with others.
    • You agree to watch at least 30 minutes of any video course that you take a coupon of within a week. You can’t just take a coupon and sit on it for a few months.
    • And you agree to provide feedback at the form provided to you at the time of the offer, letting me know which things you liked or would want to see improved.

    If you’d like to be part of this Beta Group, where you get notified of courses and practice tests the day they come out and an opportunity to get in for free, please sign up at the form below.

    You can unsubscribe from that at any time. There is no obligation to participate in any offer if it does not interest you. Only a limited number of people (probably 25) can be accommodated in any beta testing group but there should be many opportunities for different courses over time.

    Thanks in advance!

    [activecampaign form=23]

  • Happy Thanksgiving!

    Happy Thanksgiving!

    Just a quick video today to wish all my American friends a very happy Thanksgiving Day. Eat a little, shop a little, and have a relaxing long weekend away from the computer. 🙂

    Quickstart Series: Windows Web App in Azure

    In this video, I show you how to create a Windows Web App in Microsoft Azure. Windows Web App. We go through the Azure Portal, and see how form fields get filled in. If you can’t afford to create resources in Azure, but want to see how it’s done in 2018, this is the video for you.

    Or you can see the video directly on YouTube.

  • Another Engineer Blamed for Poor Process

    Another Engineer Blamed for Poor Process

    Back in March, I wrote about the poor Amazon engineer who accidentally brought down a portion of the Internet by removing a larger than expected number of servers from operation in AWS S3. That made for a bad day.

    Well it seems that something else happened in March, around the same time. Another engineer at a different company failed to do something, which would cause him to have a bad month a few months later.

    We’ve all heard that Equifax got hacked this summer, exposing the most detailed personal information of almost every American (140 million, which is almost every adult who interacts with the financial system in some way). I was personally furious when I heard about it, and some are calling it the most serious hacking incident ever.

    It’s debatable, since Yahoo confirmed yesterday that hackers stole the emails and encrypted password of 3 billion accounts 4 years ago. But certainly, getting email addresses is less valuable than credit details and social security numbers.

    The other thing about Equifax is that these are not user accounts, but people who have no direct relationship with Equifax. These 140 million people are the product, not the customers.

    But we can all agree that Equifax was a huge hack.

    Yesterday, the CEO submitted written testimony to congress that says the following.

    On March 9, Equifax disseminated the U.S. CERT notification internally by email
    requesting that applicable personnel responsible for an Apache Struts installation upgrade their
    software. Consistent with Equifax’s patching policy, the Equifax security department required
    that patching occur within a 48 hour time period. We now know that the vulnerable version of
    Apache Struts within Equifax was not identified or patched in response to the internal March 9
    notification to information technology personnel.

    Further detail was provided during his testimony.

    The human error was that the individual who’s responsible for communicating in the organization to apply the patch, did not.

    So to Equifax, the breach comes down to an individual who’s job it was to patch systems when notified of security vulnerabilities who did not patch it.

    To me, a company that has such precious data (such as a bank or credit reporting agency) should have more robust security processes to ensure a single missed patch doesn’t get overlooked.

    And why was it so easy for the “online dispute website” to get access to the full database of consumers and credit info?

     

  • The Future of Enterprise Architecture

    The Future of Enterprise Architecture

    The question I’m asking myself today is, is there a future in Enterprise Architecture?

    That’s a tough question, I admit. And the answer seems fairly clear on both sides.

    OF COURSE, there’s a future. Companies need specialists who can shape their organization to match their business goals. Just like airlines will always need people who understand aerodynamics, companies need people who understand what is important to accelerate success, and what is getting in the way and causing drag. The role is absolutely critical for large companies.

    BUT we live in a time of agile development. We can’t sit back and wait months to execute on plans. If a company sees an opportunity in a new space, it needs to be able to quickly enter that market and establish some type of operation. It can’t wait one or two years for the next ADM cycle to start before deciding to improve it’s customer onboarding to increase retention.

    The solution, then, is that companies need to focus on speed as a capability. Giving business units the capability to operate quickly in changing markets, and putting processes in place to ensure those business units operate in-line with the overall business goals.

    In essence, it turns the enterprise architect role into establishing strong business problem-solving ability in smaller business units and ensure the business supports that, as opposed to trying to solve these business problems in one and two year cycles.

    We see a similar trend in the fashion industry. Fast Fashion is something that has emerged in the past 10 years or so. Fashion trends move quickly from the runway to the stores. If a style or a look becomes trendy, you can expect to see those styles on sale quickly instead of waiting 6-9 months for it to work its way through the traditional “design, planning, manufacturing, shipping, distribution” stages.

    Unfortunately, TOGAF has not yet evolved to meet this new “fast business” world that we live in. There seems to be a strain between the two worlds. There will always be the “big centralized” model that absolutely does not want or need “fast business” and has no incentive to move off these long cycles that make every move slow and deliberate. Meanwhile, many companies (including behemoths like Microsoft and Amazon) realize the need to be quicker to market with innovative products and are not worried about things being a little bit broken or imperfect because they can be fixed.


    I will end this with a bit of a favor. Completely optional of course. I want to ensure I’m giving you information that is useful to you. If you have an interest in TOGAF, enterprise architecture, and big trends that shape how large businesses operate, clicking here will let me know to focus on that. If you’re more interested in cloud technologies from an architect, developer or implementer perspective, clicking here will let me know to focus on that instead. And if they both interest you, then clicking here will ensure I deliver information about both.