Between 20% and 25% of the az-204 is related to security, knowing what Azure offers regarding security is one of the main goals of the exam. Here, we will go over different services, such as Active Directory (one of the most popular products from Microsoft), ADB2C, encryptions, azure key vault, Authorization, Authentication, App gateway and permissions.
Storage is one of the main concepts to get familiar with for AZ-204 and also other exams. In this section we will go over different aspects of the storage account in microsoft and its services, more specifically, the following services; access keys, azcopy tool, blobs, redundancy and cosmosdb.
Azure offers different compute services such as Azure VMs, Azure containers, Azure functions, Azure Kubernetes and Azure app services. In this section we will go through the compute solutions that Azure offers as well as share references to specific microsoft documentation where more information can be fetched accordingly. The main goal here is to go over all the compute services that are listed in the exam topics, compute solutions is the biggest portion of the exam in total 25 - 30% of the total).
This is a follow up on a series of posts around TDD anti-patterns. The first of this series covered the liar, excessive setup, the giant and slow poke, those four are part of 22 more, the anti-patterns is a list formalized in James Carr post and also discussed in a stackoverflow thread. In this blog post we are going to focus on the last two anti-patterns from those lists and also two new ones - the flash and the jumper. Both of them are focused on the practice of test driving code instead of the pure code itself.
I am not sure how this post is going to be, but the idea is to brain dump what is my current understanding of hexagonal architecture and try to make like a journal of that. As I improve my understanding I can improve this post and so on. Hexagonal architecture is usually mixed with the clean architecture, even though, it was used as an inspiration to the clean architecture, they are different. Valentina Cupác describes that on her talk in details. Found something that seems wrong and would like to contribute? Leave a comment and I can reply as fast...
In this blog post we are going to focus on four more of them, named The stranger, The operating system evangelist, Success against all odds and The free ride. Each one of them focuses on a specific aspect of code that makes testing harder, sometimes it comes from not doing TDD, sometimes it just comes from the lack of knowledge on designing code. Either way, this is an attempt to explore those flaws and avoid them in our own code base.
In this blog post we are going to focus on four more of them, named The greedy catcher, The sequencer, Hidden dependency and The enumerator. Each one of them focuses on a specific aspect of code that makes testing harder, sometimes it comes from not doing TDD, sometimes it just comes for the lack of knowledge on designing code.
Katas are the way that developers use for sharping their skills in a particular subject. For example, TDD, design patters, SOLID principles or any kind of design to develop software - out there, there are katas for software architecture. Katas, have their name and inspiration from the Japanese karate, that focus on a specific and only one thing at time and bet on repetition to improve little by little. As already mentioned by Felienne in her book The programmer’s brain repetition is not something that programmers rely on to improve their skills, in that sense, repetition seems to be something...
In this blog post we are going to focus on four more of them, named The nitpicker, The secret catcher, The dodger and The Loudmouth. Each one of them focus on a specific aspect of code that makes testing harder, the four presented in post are somehow connected to starters in TDD, most of them are patterns found in who has not experience writing applications guided by tests.
