Well, let's talk business! It's no secret that email marketing is a cool tool that brings business closer to the user. Mailing allows the brand to speak humanely and confidentially, forming a special intimate space - reliable and protected. If you don't yet have your own mailing, we recommend you at least think about it.

We've long left behind the thought of the need for mailing, and every month we release digests dedicated to different technologies. In digests, we talk about tools that make development easier, key updates, and important industry events.

Today is a special day for our digests, because we want to tell you what steps precede their creation. There are rumors that creating your own mailing will be almost completely simple with this quide!

We have spoken to Sebastian Ramirez, and he told us some secrets, many of which will be useful to you too.

Why is his opinion useful? Because Sebastian is not only a wonderful man with a beautiful mustache, but also a well-known open source enthusiast. He is a creator of FastAPI, Typer, and SQLModel. Sebastian is building products and custom solutions for data and machine learning systems, and has led teams of developers around the world. In a word, he daily makes our world a better place.

📌 Sebastian's example inspired us not only for this post, but for an entire article. You can read it here.

In programming, there are many things that developers have to consider and keep in mind when writing code. Those issues and practices differ from company to company and from team to team, and every time something has to be changed in the usual algorithm. In order to make the changes more experiential and less stressful, you can create a detailed guideline.

💡 Guideline?
Yes, guideline. This is a detailed instruction that builds a common denominator for writing code within the company.

💡 And why is it necessary?
In short, it will save you a lot of time.

For more details, scroll through the slides. There we described 4 situations in which there is no way without a guideline. We're sure this has happened to almost all of you.

Let's go back to talking about guidelines for a moment. As you may have guessed, we have created our own one. Well, today we are talking about our Python guideline.

This project was born from the mistakes that we saw at a large number of projects during technical audit and now it makes life much easier for pythonists. The repository is designed to be reusable and is available right now - we hope that the experience we have gained will help you. Well, to make this process easier and clearer for everyone, we have prepared a visual navigation. Scroll through the slides!

📌 The repository is available here