Posts
-
Resume as Code
LinkedIn’s ‘Easy Apply’ feature streamlines job applications, enabling candidates to submit their profiles directly to recruiters. This bypasses the need for filling out additional forms or attaching separate resume files. Kudos to the employers who embrace this feature, as it helps them stand out in the competitive candidate-driven market.
However, the current employer-driven market often has different requirements, including the need for a detailed resume in a printable document format. This presents a challenge since LinkedIn’s existing functionality restricts the export of profiles to PDFs with significant data loss and limited control over layout.
This post explores how you can use LinkedIn as your primary data source to craft adaptable resumes in both PDF and web page formats, leveraging open standards and automation for greater efficiency.
-
General thoughts on IaC practices for Azure management
In this post, I share my thoughts on established IaC practices for Azure management, often regarded as “best practices.” However, they may benefit from a deeper, critical examination.
We will explore themes such as Centralization and Democratization, Solution accelerators, treating Infastructure as Software, the need to Automate every task, Modularization and version control, Automated testing, State management, and choosing the right Configuration format.
Intended to evolve, this document will be periodically revised and expanded as I learn new insights and industry shifts occur.
-
Choosing the right level of IaC management tools for Azure
Tools such as CLI & PowerShell, ARM & Bicep templates, Terraform & Pulumi – all serve as management interfaces between your code and the Azure API, and, in the absence of a better term, just called “Infa as Code management tools”.
When choosing such a tool, it’s important to make an informed decision based on your actual needs and capabilities. Various IaC tools span different levels of complexity and abstraction. Let’s explore these options and determine which level best fits your situation.
My thoughts on general IaC practices, such as version control, code reuse, CI/CD, and testing will follow separately.
-
Name Resolution for Azure Private Endpoints
In my previous post, I explored the use cases and constraints of Private Endpoints.
In this post, I will delve into the topic of name resolution for private endpoints and why it is critical. We’ll explore the available approaches and my generally recommended solution.
Tech nerd content warning, open with caution!
-
Choosing between Public, Service, and Private Endpoints in Azure
When deciding between Public, Service, or Private endpoints in Azure, it’s essential to make an informed choice rather than blindly following generic recommendations.
Tools like Azure Secure Score, various benchmarks, and CAF documentation may seem convincing, but uncritical adherence can result in less resilient solutions and increased maintenance costs.
In this post, I will explain the differences between Public, Service, and Private endpoints and share the pros and cons of their use in common scenarios.
-
Visual editors for Markdown
Markdown became an industry standard for Docs as Code a long time ago. It is used on Azure DevOps, GitHub, MS Docs, and even on my humble blog. However, one thing has been bothering me for all that time: working with tables in Markdown when you need more complex formatting. On the cover picture, you can see how unfriendly it is. In this post, I will share which visual editors for Markdown can solve this issue.
-
Naming Convention for Azure Resources
In this post, I’m sharing the naming convention I’ve been using for the biggest Azure infrastructure projects during my career at Microsoft and EPAM. Since 2015, it has proven to work well in enterprise-scale environments long before Microsoft introduced CAF and the concept of Landing Zones.
I’ve noticed that many customers tend to take CAF’s guidance on naming conventions too literally, which is far from perfect when you move beyond test lab scales.
It’s probably too late for you to change the naming convention of Azure resources, as the cloud adoption curve has been past its peak for years. So, now could be a good time to share my old “trade secret”.
-
Diagrams as Code
Did you know that you can do Diagrams as Code? In this post, discover how to generate machine-made diagrams of Azure Management Groups structure using a declarative approach.
subscribe via RSS