After having roamed the savanna on the back of an elephant (PHP) and having drunk a few pools of blue coffee (Java), I finally succumbed to the charms of the snake entwined to its branch. And for good reason, Python is a vast and powerful programming language that meets all my expectations. Its simplicity of use and its vast ecosystem make it an excellent choice for anyone who wants to work efficiently.

Django is a Web Framework for those who want to go as fast and as simple as possible, without compromising on quality. Its philosophy, closer to the declarative "lego" code, allows answering many topics in record time. In many situations, it keeps a privileged place in my toolbox.

After spending 3 years with a PHP CMS, I quickly had the chance to discover the Wagtail CMS! Open-source, I was surprised to be able to contribute to this project thanks to an open and accessible community.

Designed by developers for webmasters, the bias is to dissociate the content and the form: the developer develops, and the webmaster takes care of the content.

Without futile promises, an informed Djangonaut can quickly set up all the tools expected from a CMS, without going through a plethora of plugins:

• Content management: scheduling, permissions, preview, workflow, multilingual, multisite, etc
• Media (images, videos, documents): library, conversion, auto-crop, face detection, etc.
• Additional content: page fragment, tagging, AMP page, etc
• Backoffice: well-designed and responsive
• Search engine: integration with PostgreSQL or ElasticSearch (fulltext, facet, highlighting)
• SEO: best practices, redirects, sitemap, etc
• Headless: REST API integration, easily extensible
• Performance: your database will no longer suffer unnecessarily in connected traffic and the possibilities of front-end caching are diverse and varied

To show my knowledge, this website has been designed with this CMS and and I strongly invite you to visit this demo website for a more in-depth hands-on experience. What's more, the source code is available on GitHub for the more curious.

Although this CMS still hasn't achieved its rightful place among the general public, the fact remains that it hasn't aged a bit over the years, and will continue to defy the ravages of time.

Because manual delivery are only bad and distant memories, developers today have no excuse to automate application delivery. Therefore, my skills as a backend developer do not stop at Python Django. With my devops hat on, I can also deploy and host your applications. Usually, I use the following tools:

• Ansible: to automate the delivery of projects with a simple layout
• Gunicorn: WSGI Python server
• Nginx: HTTP Web server

Of course, I also have some notions of Docker, but I'd need to develop my skills further to be able to claim a confirmed level.

When it comes to hosting, I personally work with OVH for its reputation and expertise. On a professional level, I've worked with other cloud hosting providers, notably with the help of tools like Openshift.

Climbing a cliff without a safety harness? No thanks! I always protect my rear with 100% branch coverage... and so, for good reason! As a guarantor of quality and durability, Python is full of test frameworks : nose, pytest, coverage, unittest, selenium (python integration)... Most of the time, I use Django's test framework, which is a perfect fit for the tool, but also Pytest for FastAPI applications.

A programming language is a language like any other. To be understood by everyone, it is necessary to respect some conventions, and Python is no exception to the rule. PEP8, package sorting, simplification and best practices are the guardians of a good cohesion for a successful teamwork. Since to err is human, you should automate these standards as early as possible in your continuous integration (CI) processes. To achieve this, I use tools like :

• Black: to format code that facilitates teamwork
• Pylama : the Swiss army knife to complement Black
• Isort : cleanup your imports
• Tox: automated tests and much more