Microsoft Certified: Azure Fundamentals

Another month, another Fundamentals exam 😄

I got this one because it was free after doing some online training through Microsoft. But - it was about time I got it.

I've been using Azure since it came out but never got certified because there's a lot of Infrastructure stuff in the exams which don't particularly interest me as a developer. In saying that, I found the exam material high level enough to be interesting and I managed to fill in a few gaps. 

Most notably - I enjoyed playing with the Azure Infrastructure map. It's a cool visualisation tool that lets you explore all the Azure infrastructure, all the datacentres, undersea cables, even satellites. You can take a virtual tour of a datacentre and learn about Azure in space! Cool stuff.

Comments

Post a Comment

Popular posts from this blog

Foundations of Humane Technology - Course completed

Image
Back in January (has it been that long!) I completed the Foundations of Humane Technology course from the Center of Humane Technology . You may have heard of them, they made the Netflix Documentary " The Social Dilemma ". If you haven't watched the movie, it's well worth a watch, delving into the often devastating impacts of Social Media. The course explored how to build technology in a more responsible way to minimise the harmful consequences of the technology you build. It's perfect for technology oriented Product owners and developers like myself, requiring us to think about externalities and unintended consequences, and aligning our values with the products we build. I was made to reflect on how technology has impacted me personally, and realised how my health, cognition and attention were impacted by technology overuse. I was obliged to acknowledge that I am very privileged and lucky, I don’t have any major accessibility issues and my demographic allows me t
Read more

Writing Good Acceptance Criteria

Image
As discussed in my last article , Writing good Acceptance Criteria gives the Agile team clarity and helps them work towards a common goal, saving time and effort while increasing quality. Now I'd like to dig into the details of how to write good Acceptance Criteria. Behaviour Driven vs Procedural Driven Mindsets Many of us may be used to writing/seeing procedural driven tests; step by step instructions with actions and expected results. Procedure-driven tests are often imperative and trace a path through the system that covers multiple behaviors. As a result, they may be unnecessarily long, which can delay failure investigation, increase maintenance costs, and create confusion. Acceptance criteria, and indeed Behaviour Driven tests, should instead be behaviour driven. This means they should be Declarative , specifying how a system should behave in a particular scenario. Procedural/Imperative: Given the user opens a web browser And the user navigate
Read more

Story Points are Utter Nonsense

Image
For over a decade, I've lived a lie. I made myself believe that Agile Story points made sense. I rationalised it like we all did. "They map to complexity, not time". Yet we spend hours on Sprint Planning meetings deciding how many jobs we can fit into a Sprint - a unit of time . Also - doesn't complexity relate to time? "They're a rough guide, they're not supposed to be accurate." How on Earth did we end up with a unit of measure that is "not supposed to be accurate"? "It depends on experience of the person doing the job." This is like saying the length of a centimeter depends on the tape measure you're using. "They're a measure of  relative complexity." Relative to what? Another story you did which didn't have an accurate estimate? "We use shirt sizes/Fibonacci/animals/fruit." Is this supposed to make it easier to understand? Why can't I give a task 4 points? "We have to agree on size befo
Read more