Softellar

C++ Staff Augmentation

C++ Staff Augmentation for Native Code

C++ leaves memory, threads and the build to your team. An engineer from our in-house team joins your codebase, your reviews and your releases, finds what the code leaves unchecked and modernizes it module by module. You lead the work.

Discuss your C++ codebase

We reply within 24 hours

Clutch rating, 12 reviews
5.0
Projects since 2021
70+

Companies we have built software for

  • Multi Radiance Medical
  • Loma Lux Laboratories
  • WellVu
  • Commercial Capital Group
  • Grand Auto
  • HostMy
  • Land Base
  • Auto Tuning

No Runtime to Catch It

In C++, nothing checks a pointer, a thread or a copy while the program runs. The engineer adds the checks your code is missing.

A program that measures parts from camera images

Illustrative program

  1. configreport bufferpart list

    A buffer for every failed report, never freed

    01

    Old code with raw pointers

    • C++17
    • STL
    • GoogleTest

    Where it goes wrong

    A function written in 2004 returns early on an error and skips the delete at its end, so every failed report leaks its buffer and the program is restarted each night.

    What the engineer adds

    One owner for each resource, so it is freed on every path, and a test that reproduces each crash before it is fixed.

  2. frame 41frame 42

    The camera writes a frame while a filter reads it

    02

    Threads that share data

    • STL
    • Boost

    Where it goes wrong

    The camera thread writes the next frame into the buffer a filter is still reading, so one part in a few thousand is measured from two half frames.

    What the engineer adds

    A queue that hands each frame to one thread at a time, and a stress test that runs the pipeline at full speed for hours.

  3. framecopycopycopycopy

    Four full copies of every frame

    03

    The image pipeline

    • OpenCV
    • perf
    • VTune
    • Tracy

    Where it goes wrong

    Each filter copies the whole frame before it works on it, so memory is allocated and freed for every frame, and a second camera halves the frame rate.

    What the engineer adds

    A profile before any change, buffers allocated once and reused between frames, and the frame rate measured before and after.

  4. main windowclosed dialoglate result

    A result sent to a dialog that already closed

    04

    Qt desktop screens

    • Qt

    Where it goes wrong

    Measuring runs on the thread that draws the window, so the screen freezes, and a result that arrives after its dialog closed is written into freed memory.

    What the engineer adds

    Measuring moved to a worker thread, and results sent back through queued connections, so they arrive on the window’s thread or not at all once it closes.

  5. imagefreedPython view

    A Python object still points at an image C++ freed

    05

    Libraries called from other languages

    • pybind11
    • Python

    Where it goes wrong

    A Python script keeps a view of an image after the C++ object that owns it is freed, so an analyst’s notebook crashes an hour into a run.

    What the engineer adds

    Bindings that state who keeps each object alive, and the Python lock released during long C++ calls so scripts do not stall.

  6. 1 part_id2 width3 reused4 status

    Field 3 was removed, then given to a new value

    06

    Services and networking

    • gRPC
    • Protocol Buffers
    • Boost.Asio

    Where it goes wrong

    A field was removed from a message and its number given to a new one, so older clients read the new value as the old one.

    What the engineer adds

    Removed field numbers marked as reserved and never reused, and a deadline on every call so one slow client cannot hold the service.

Imaging and Older Systems

Real-time image processing, hardware telemetry and older systems our engineers took apart and moved forward.

United States

Imaging Data Processing For A Healthcare Technology Company

High-performance thermal imaging data processing solution for healthcare technology providers.

  • Java SE
  • OpenCV
  • Android SDK
  • Kotlin

Modernized Without a Rewrite

A C++ codebase is often older than the standard it could use, and few teams can stop the product to rewrite it. So old and new code build into one program.

The codebase, module by module

Illustrative codebase

ModuleOwns its memoryHas testsBuilds on LinuxOn C++17
Measurement coreSince 2003In progressIn progressNot startedIn progress
Image pipelineSince 2011DoneDoneDoneDone
Qt screensSince 2014In progressNot startedDoneDone
Python bindingsSince 2019In progressDoneDoneDone
Report serviceSince 2021DoneDoneDoneDone
Export moduleRustNewWritten in Rust and linked through a C interface, so it builds into the same program
  • Done
  • In progress
  • Not started
A clean build, 41 minutes

Illustrative codebase

  1. 1Headers included everywhere

    Includes trimmed, and precompiled headers for the rest

    Before: 14 minAfter: 5 min

  2. 2Dependencies built from source

    Prebuilt packages from Conan or vcpkg, cached in CI

    Before: 12 minAfter: 2 min

  3. 3One large link step

    The core split into libraries that link on their own

    Before: 6 minAfter: 3 min

  4. 4Tests

    Tests run in parallel, split by module

    Before: 9 minAfter: 4 min

So the old code keeps shipping

Is the whole system due for a rebuild? Legacy modernization covers the plan and the move to a new platform, as a project we run.

See legacy modernization

Clients on Hard Technical Work

An imaging pipeline that keeps up with the camera, older systems moved forward and data work automated.

C++ Engineers for Long-Lived Code

C++ staff augmentation adds a C++ engineer to your team, and you lead the work.

The engineer finds the memory and threading faults nothing checks at run time, measures before speeding anything up, and moves older modules to modern C++ while the program keeps shipping.

The goal

A program that runs for weeks without a restart, and a build the team does not wait on.

What the engineer works in

  1. Written in

    • C++11 to C++23
    • STL
    • Boost
  2. Built with

    • CMake
    • Conan
    • vcpkg
    • Docker
    • GitHub Actions
    • GitLab CI
    • Jenkins
  3. Linked against

    • Qt
    • OpenCV
    • gRPC
    • Protocol Buffers
  4. Checked by

    • GoogleTest
    • Catch2
    • perf
    • VTune
    • Tracy
  5. Runs on

    • Linux
    • Windows
    • WebAssembly
    • Emscripten
  6. Beside it

    • Python
    • pybind11
    • Rust
From the source file, through the build and the libraries it links, to the tests and profiles that check it and the platforms it runs on, with the languages that sit beside it.

A Crash Nobody Can Reproduce?

Tell us what the code does and how it fails, and an engineer will tell you who we have.

We reply within 24 hours and can sign an NDA first.

Have files or a long brief? Use the full form

Before the First Clean Build

Four questions we ask before proposing a C++ engineer, then the five steps to their first two weeks.

What we ask

  1. 01

    Which standard and platforms it builds for, and how long a full build takes

    For exampleC++14 on Windows, with a Linux build half done, 40 minutes from clean

    So the engineer knows which language features are open, and how long each change waits to be checked.

  2. 02

    How old the oldest module is, and who still knows it

    For exampleA core from 2005 that one engineer still on the team knows well

    So the first week is spent with the person who knows why the code is shaped the way it is.

  3. 03

    How it fails today

    For exampleA crash about once a week in production, and memory that grows until a nightly restart

    So the first weeks go to reproducing the worst fault in a test before anything is changed.

  4. 04

    What calls it, and what it calls

    For examplePython scripts through pybind11, a camera SDK, and a gRPC service other teams depend on

    So the engineer knows which boundaries other code relies on before any interface moves.

Then, in this order

  1. 01Brief

    You answer these questions, plus the role, the seniority and the start date.

  2. 02Shortlist

    We match the brief against our in-house engineers and send the profiles that fit.

  3. 03Interview

    You test them the way you would test your own hires, then pick who joins.

  4. 04Order

    A short order under the master services agreement names the engineer, the rate and the start date.

  5. 052-week trial

    The engineer joins your standups and opens a first pull request in week one.

Terms at a glance

Read the full agreement
Start
Often within 48 to 72 hours
Trial
The first 2 weeks, before any long-term commitment
Replacement
Within 48 hours, at no extra cost
Notice
One month to scale up or down, with no penalties
IP
Full ownership assigned to you under the MSA
Working hours
Standups and reviews from 2 to 6 PM CET, the US morning

US Office, European Engineering

Headquartered in Warsaw, Poland, with a client office in New York. A European engineering team that works in your hours, with a US point of contact.

Headquarters

Warsaw, Poland

Engineering and delivery, and the main contact point for clients in Europe.

Client office

New York, United States

Kickoffs, contracts and account management for North American clients.

Shared hours with North America

Clients in Europe share the full working day with the team.

8 AM to 12 PM New York time, 2 PM to 6 PM in Warsaw.

Staffing and Modernization Awards

Awards for our staff augmentation and modernization work, and for the in-house team our C++ engineers belong to.

Related reading

Reading for Teams With Older Code

Guides from our team on modernizing older applications, the tools for it and reviews that keep code healthy.

All Insights

Frequently Asked Questions

Questions teams ask before a C++ engineer joins a codebase that has been shipping for years.

Have a different question? Talk to our team

How Long Is Your Build?

Tell us about the codebase, the platforms it runs on and what slows the team down.

We reply within 24 hours, and we can sign an NDA before you share details.

Talk to the people who will scope your project