<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Modern C++ on [ MECANIK DEV ]</title><link>https://mecanik.dev/en/tags/modern-cpp/</link><description>Recent content in Modern C++ on [ MECANIK DEV ]</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>Copyright © 2020-{year} by [ MECANIK DEV ]. All Rights Reserved.</copyright><lastBuildDate>Sun, 02 Aug 2026 19:00:00 +0100</lastBuildDate><atom:link href="https://mecanik.dev/en/tags/modern-cpp/index.xml" rel="self" type="application/rss+xml"/><item><title>Hire a C++ Developer: Rates, Specialisms and Vetting</title><link>https://mecanik.dev/en/posts/hire-cpp-developer-rates-specialisms-vetting/</link><pubDate>Sun, 02 Aug 2026 19:00:00 +0100</pubDate><guid>https://mecanik.dev/en/posts/hire-cpp-developer-rates-specialisms-vetting/</guid><description>The decision to hire a C++ developer usually arrives with a specific problem attached. Something has to be fast, or has to run on hardware, or has to interface with a library that only ships a native interface. What follows is a hiring process that treats C++ as a single skill, and that assumption is the source of most disappointing outcomes.
C++ is not one job. A brilliant games engine programmer can be genuinely unproductive on embedded firmware, and a low-latency trading specialist may have never shipped a graphical application in their life.</description></item><item><title>Hire a Qt Developer: Skills, Rates and Licence Traps</title><link>https://mecanik.dev/en/posts/hire-qt-developer-skills-rates-licensing/</link><pubDate>Sat, 01 Aug 2026 19:00:00 +0100</pubDate><guid>https://mecanik.dev/en/posts/hire-qt-developer-skills-rates-licensing/</guid><description>Companies that need to hire a Qt developer are usually building something that has to run on a machine rather than in a browser: an instrument panel, a diagnostic tool, a control application for hardware nobody else supports. The candidate pool is a fraction of the size of the web market, the vocabulary is different, and the usual hiring shortcuts do not work. A recruiter filtering on &amp;ldquo;C++&amp;rdquo; will hand you people who have never written a line of QML.</description></item><item><title>C++ vs Rust Memory Safety - Practical Examples with Modern C++</title><link>https://mecanik.dev/en/posts/c++-vs-rust-memory-safety-practical-examples-with-modern-c++/</link><pubDate>Sun, 15 Feb 2026 20:00:00 +0100</pubDate><guid>https://mecanik.dev/en/posts/c++-vs-rust-memory-safety-practical-examples-with-modern-c++/</guid><description>The memory safety discussion between C++ and Rust has become one of the most active topics in software engineering. Government agencies have weighed in, conference talks are dedicated to it, and opinions run strong on both sides.
Let me be upfront: Rust is an excellent language. Its ownership model and borrow checker are genuinely innovative, and they catch entire categories of bugs at compile time. If you&amp;rsquo;re starting a new project and Rust fits your team and ecosystem, that&amp;rsquo;s a great choice.</description></item></channel></rss>