Welcome to my weekly newsletter! Every week, I bring you the latest news, updates, and resources from the world of coding and architecture. I'm so glad you've decided to join me, and I can't wait to share my insights and expertise with you.

In this newsletter, you'll find a curated selection of articles, tutorials, and other resources that I think will be useful and interesting to you. I cover a wide range of topics, from new tools and technologies to best practices and design patterns. I'm always on the lookout for the latest trends and developments in the field, and I'm excited to share them with you.

I hope you'll find this newsletter to be a valuable resource, and I welcome your feedback and suggestions. If there's something you'd like to see more of, or if you have any questions or comments, please don't hesitate to reach out to me.

Thank you for joining me, and happy reading!

REST and APIs

Something you most likely not using explicitly, but version 3 of HTTP is on its way. Read more on how to use it and where it can be used:

When you build an API, but no developer is able to use it properly, then it will deliver a pretty bad developer experience. This article will talk about what is called API developer experience:

Coding technicalities

A Task and a Thread are not equal to each other. Steven Giesel provides insights in the difference between the two concepts:

I burned my fingers on tuples once where suddenly two strings got swapped and I wished we just used a PoCo there instead. But there is another approach using pattern matching that provides an interesting way to use Tuples:

You learned to write code and add a good dose of unit tests to make sure everything is working fine. At some point you will need to deploy your application and you start creating Infrastructure as Code scripts, like ARM or Bicep. But how do you make sure those are indeed correct and follow best practices? With PSRule you can validate that they adhere to the Azure Well Architected Framework:

A pretty disturbing result after an extensive analysis of the Azure DevOps Marketplace by Jesse Houwing. Read and weep, but luckily it also contains tips and tricks:

GitHub related

Want to make sure an issue is linked, a security scan is done or a test suite is executed? Then the new Required Workflows solution is for you:

Adding code scanning is now easier than ever; no need for an explicit workflow file, just checking some boxes:

We already had forms for issues, allowing you to collect specific data from the issue creator, but GitHub also brings this to Discussions!

When you wanted to use reusable variables in a workflow, then you could use secrets only. With the newly supported configuration variables, GitHub adds an option to store variables at Organization, Repository or Environment level.

Computing in general

A collection of thoughts about things they did not teach you in school:

Microservices, another hype term and misused many times. But what if we are actually talking about modules instead:

Do you know the difference between a Dialogue, Debate and Discussion? Learn and find tips on how to improve communication:

Helpers and utilities

Struggling to find a way to install a specific tool? You do not remember how to install Curl on a Kali Linux machine or run Vim on MacOs? Command-not-found provides details on how to install and use the commands on various systems.

Computer Laws

Putt's Law is a statement that describes the relationship between technical understanding and management in technology-based organizations. The law states that in these organizations, there are two types of people: those who understand the technical aspects of the work, and those who manage the work.

The first group, those who understand the technical work, are often responsible for designing, developing, and implementing new technology. The second group, those who manage the work, are responsible for making sure that the technology is being used effectively and efficiently.

The law implies that these two groups often have different priorities and ways of thinking, which can lead to tension and misunderstandings.

I hope you've enjoyed this week's issue of my newsletter. If you found it useful, I invite you to share it with your friends and colleagues. And if you're not already a subscriber, be sure to sign up to receive future issues.

Next week, I'll be back with more articles, tutorials, and resources to help you stay up-to-date on the latest developments in coding and architecture. In the meantime, keep learning and growing, and happy coding!

Best regards, Michiel