Evrone

C++ is one of the most popular programming languages. We know and love it for its reliability, speed of code execution and versatility - in due course it made a splash among web developers. However, none of this would have happened if it were not for Bjarne Stroustrup, who designed and developed this language, and also dedicated three books to it, which have gone through many editions.

Today we want to introduce Bjarne to you closer, and at the same time demonstrate clearly why success is almost always the result of hard work.

📌 As always, you have a choice - a short summary of the interview in slides and an entire article, which can be found here.

Evrone is in touch! We are here to remind you of simple truths on this beautiful day:

Truth No. 1 - optimize processes, and you are bound to succeed.
Truth No. 2 - open-source makes our world better and more understandable.

These statements are much more closely related than it might seem at first glance, and we have confirmation of this. For example, our update-informer is an open-source library, and it saves the developer a lot of time on really important things - checking for updates is obviously not one of them.

Sounds cool, right? That's what we thought, devoting an entire article to update-informer.

Well, if there is no time for this, and the bright May sun is already calling for a walk, then we recommend scrolling through the slides.

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

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.