To celebrate Global Engineering Day, we’re looking at what it’s like to work as a truly global engineer, collaborating with international colleagues from all over the world to advance software development.Read on to learn about the career paths of Claire Dross, Head of Static Analysis at AdaCore, based in our Toulouse office in France, and Tõnu Näks, Deputy Head of Toolchain and Managing Director of AdaCore’s Estonia branch in Tallinn.<h3 dir="ltr">What's your educational background?</h3>Claire: I studied Computer Science at the Ecole Polytechnique, a French Engineering School. The degree there is equivalent to a Master's elsewhere.In my last year of Engineering School, we each chose a specialization. I was studying part-time at a university in Paris for a technology research degree called MPRI -&nbsp;Master Parisien de Recherche en Informatique. Someone from AdaCore had posted an internship proposal on a board at the university and I found it unique because this university is a research university, so usually you wouldn’t see internships posted there. I interviewed both for this internship which included the opportunity to do a PhD, and for another opportunity with Dassault Systèmes. AdaCore sounded like the most interesting one with complex, challenging research to work on with very smart people.During my first three years at AdaCore, I completed my PhD on Generic Decision Procedures for Axiomatic First-Order Theories, which was a subject that was relevant to my work here. After finishing my PhD in April 2014, I continued at AdaCore as a software engineer.Tonu: I studied at the Tallinn University of Technology, graduating with an MSc in Systems and Software Engineering in 1998.My research topic was modeling time constraints using UML/SysML models. I was fascinated by the idea of mixing the models of real-world objects with system requirements and then doing some magic to get a computer program out of it. This got me involved in model-based development.I worked alongside my studies, starting out as a C/C++ programmer in an industrial automation startup in 1990, and later becoming a project manager at the university. While working on my master’s thesis in 1997, I was assigned a research project to create a UML tool for describing system behavior with time constraints and doing formal analysis on the consistency of those constraints. This led to me and two of my colleagues founding a startup called IB Krates to commercialize this tool.<h3 dir="ltr">How has your career progressed at AdaCore?</h3>Claire: When I was doing my PhD, I was naturally very focused on its subject, which was really technical. Gradually over time, I began to look at SPARK as not just a technology but as a product, and my work shifted to involve much more development than research.As the years passed, I was given more responsibility, working on projects like the SPARK roadmap. Thanks to this experience, I was offered the role of Team Lead for SPARK. This was my first experience with management.I had also been building my skills in this area and had attended AdaCore’s internal management training course, so all this contributed to me becoming the right person to lead the team. I really enjoy being a manager, it’s fantastic. I never get bored with helping people prioritize their workload, listening to their ideas, and generally just being present to support them when projects become challenging.In July 2024, I was promoted to Head of the Static Analysis Unit. By this time, I had been working in SPARK for over 10 years. It felt like a good time to broaden my understanding of our technologies to learn more about our activities in other Static Analysis sub-teams. I’m enjoying learning more about our work with Dynamic Analysis and have just started a project in the Dynamic Analysis Unit. I’m always able to find a new intellectual challenge here.Tonu: I started working with AdaCore as a partner in 2009 when AdaCore joined the GeneAuto research project. GeneAuto was a consortium led by Continental and driven by requirements from Airbus, Thales, and Barco. The initial GeneAuto project ended up with a prototype of a Simulink → C translator written in Java. Our first joint project with AdaCore was the development of an Ada printer for this prototype as a proof of concept. This was also my first real encounter with the Ada language.Following a series of joint projects, the software tools group from IB Krates joined AdaCore in 2018. I became the head of the company’s Estonian branch and a member of our joint tool’s Lead Team, responsible for coordinating its development and defining its architecture.Joining AdaCore felt like a natural transition. We had good synergy practically working as one team years before the merger. When we formally joined the company, the reception was warm and people were extremely welcoming.Following this project, I moved to the Toolchain unit and became Deputy Head of Toolchain. Looking to apply my extensive experience in project management and keep my engineering skills fresh, I took the position of Front-end Team Lead at the beginning of 2024 and became Rust Team Lead later that year.<h3 dir="ltr">Can you tell us about your work with SPARK at AdaCore and how your work with the language has evolved over time?</h3>Claire: When I first joined AdaCore, SPARK was still a really novel technology and certainly more research-focused than development-focused. Over the years, this has changed a lot - the technology is now much more efficient and user-friendly. As customer demand has increased, it has grown into one of our core products. When we talk about Ada technology, we talk about SPARK too.<h3 dir="ltr">Can you tell us about the Static Analysis Unit, your current projects and its plans for the future?</h3>Claire: The Static Analysis Unit is made up of several subteams - the Libadalang team, the GNAT Static Analysis team, and the SPARK team:<ul><li dir="ltr">The Libadalang team is creating a frontend to analyse source code in Ada which is used by our internal IDE and GNATcheck teams to check conformance and compliance, for instance. Our Libadalang engineers are working on a way to reformat Ada code automatically and add “quick fixes” to tool messages to correct elements in the code.</li><li dir="ltr">The GNAT Static Analysis team is working to improve static analysis with a focus on security, for example detecting CWEs (Common Weakness Enumerations). They are also working on integrating static analysis tools developed at AdaCore in a single analysis suite. This year, they are integrating gnatmetric, which is a tool for computing various program metrics.</li><li dir="ltr">We are always working to improve SPARK's usability. This includes increasing the subset of language features it supports and adding brand-new features. We integrate support for our customers’ features within SPARK. Finally, we create new materials and resources to help programmers learn SPARK on&nbsp;<a href="http://learn.adacore.com/">learn.adacore.com</a> and to make it easier for them to annotate their code.</li></ul><h3>Can you tell us about the Toolchain Unit, your current projects and its plans for the future?</h3>Tonu: The toolchain unit provides Adacore's core technologies: compilers, debuggers, various helper tools and libraries. The unit consists of 9 teams and over 45 teammates.<ul><li dir="ltr">Our bread and butter is the Ada compiler and its ports for specific processors.</li><li dir="ltr">We’re always working on new developments for the Ada language, defining its scope and future roadmap.</li><li dir="ltr">We also provide dedicated ports for other languages – C/C++, Rust and tools for interfacing those languages with Ada.</li><li dir="ltr">Rust has been a new addition to our product offering within the last few years. It’s exciting to see how this new product is evolving and taking off.</li></ul>Personally, what motivates me at work is ensuring team members work on tasks they know best and keep processes effective. I find it really fulfilling to work on new developments in our technology and deliver the final product to our customers.<h3 dir="ltr">How do you collaborate with teams based in different locations at AdaCore?</h3>Claire: Across the Static Analysis Unit, we have representatives in many different locations. Several can be found in our offices in Paris, Grenoble, or Toulouse where I am based. But others are very dispersed including members based across vastly different timezones such as Korea and the USA.Though we try to remain connected to Slack throughout our working days to make it easier to chat and come up with technical solutions together when we need to, we also find it important to prioritize having a few regular meetings for the team. We have a weekly standup for regular updates on what everyone is working on, a monthly call for general alignment on technical goals and around 2 - 4 other meetings to share knowledge on specific topics or insights gathered from research conferences. These updates are really important to help the team work well together.Tonu: In the Toolchain Unit, we have team members from all over the world across multiple time zones, including Estonia, France, the UK, and both the West coast and East coast of the US.We organize meetings so that everyone can attend as close as possible to their normal working hours. The ten-hour time difference between the farthest time zones makes finding a reasonable time difficult, so we stick to one full team meeting per week. Most of the time we rely on Google Meetings in smaller groups, email, Gitlab messages, and Slack to collaborate. It’s not easy to organize face-to-face meetings, but we aim to get the whole team together at least once a year.<h3 dir="ltr">What would you say to someone interested in joining AdaCore?</h3>Claire: We are doing interesting work in technology and research at AdaCore. There are always technical challenges to solve to improve our products, and there is the opportunity to interact with really smart people. Collaboration is really important here — everyone wants to see the team succeed, and we all get on well together. I would say that the team and the technology we work on are the two main attractions for me of working at AdaCore.Tonu: Even if we are not a big company, we have expertise in many different fields. We have a mix of top language experts - some of whom come from the original teams who developed the Ada language - as well as experts in compiler technology, formal analysis, and processor architectures.Here, people are always willing to share their knowledge and you can speak to anyone directly, regardless of seniority. It is rewarding to hear what people are doing and, from a cultural viewpoint, I enjoy working with people from different countries.<h3 dir="ltr">What do you value most about working at AdaCore?</h3>Claire: My colleagues' expertise and the quality of work here are really high. This is important to me, and it motivates many people to work at AdaCore.Another thing worth mentioning is that while working at AdaCore, I have never felt singled out for being a woman - it has never been a topic of conversation.Career development and the freedom to create your own path are valued more here than at other companies. You never feel replaceable like you might at another company, and that’s a good thing. Each person is valued for what they can achieve, and not everybody is the same.Tonu: The first thing that struck me when I started working with AdaCore was the openness. I enjoyed seeing how the mindset of sharing knowledge simplifies working processes. Being able to book the President’s office as a meeting room in Paris shows how little emphasis there is on hierarchy here.I came from a very small company before, where it often happened that only one person had knowledge on a problem at hand. Since joining AdaCore, I have never had another occasion where I was stuck on such a specific problem and there was no one to ask for help. Here, you can always depend on somebody to ask who can give you some pointers.

To celebrate Global Engineering Day, we're looking at what it's like to work as a truly global engineer, collaborating with international colleagues from all over the world to advance software development.

Building the Future: My Path from Software Research to Leadership

<a href="https://www.adacore.com/gnatpro/assurance" target="_blank" rel="noreferrer noopener">GNAT Pro Assurance</a> customers have access to a special variant of GNATcheck called GNATkp (GNAT Known Problems detector). This tool is packaged with rules designed to detect Ada constructs affected by known problems in compiler releases. Note that GNATkp is an addition to and not a replacement for GNATcheck.Replacing error-prone manual code inspection with an automatic and systematic verification relevant to specific GNAT Pro versions and targets, GNATkp ensures that your code remains robust and free from potential bugs introduced by known problems. It integrates seamlessly into existing workflows, offering a targeted approach to safeguarding software quality,Let’s consider one example.Here is the definition of a data structure that triggers an invalid code generation on GNAT 17 for powerpc targets only:<pre><code>A record component whose type is a record type with an Unchecked_Union and a representation clause specifying a size that is not a power of two for some of the fields.</code></pre>As you can see, the triggering condition is very precise, and not easy to spot during code review, while weakening it is liable to introduce many false positives.Here is a piece of code that matches:<pre><code>type A (Kind : Boolean := True) is record
 case Kind is
 when True =&gt;
 A1 : Integer;
 when False =&gt;
 A2 : Boolean;
 end case;
 end record
 with Unchecked_Union;
    
 for A use record
 A1 at 0 range 0 .. 31;
 A2 at 0 range 0 .. 12; -- Note the size is not a power of 2
 end record;

 type B is record
 AF : A;
 end record;</code></pre>Now let’s see how we can use GNATkp to spot the problem.There are two important switches for GNATkp:<ul><li dir="ltr">--kp-version: Specify the compiler version used</li><li dir="ltr">--target: Specify the target architecture</li></ul><pre><code>$ gnatkp --kp-version=17.1 --target=powerpc -P simple.gpr
info: kp_s124_035 enabled
info: kp_s814_034 enabled
info: kp_u727_033 disabled, target does not match
info: kp_v120_015 enabled
main.adb:19:08: possible occurrence of KP V120-015 on powerpc targets</code></pre>GNATkp lists all the known problems for the given GNAT version. Problems specific to a target architecture are either disabled or enabled depending on the --target switch. Then, for each enabled problem, a rule is checked against the project source code.Infringing pieces of code will result in a message like this one:<pre><code>main.adb:19:08: possible occurrence of KP V120-015 on powerpc targets</code></pre>Under the hood, GNATkp rules, like GNATcheck rules, are written using the&nbsp;<a href="https://docs.adacore.com/live/wave/lkql/html/gnatcheck_rm/gnatcheck_rm/lkql_language_reference.html">LKQL</a> (short for LangKit Query Language). This means you can implement your own rules to detect other forbidden constructs, e.g. related to hardware malfunctions.GNATkp can be integrated into developers’ workflows, continuous integration systems, or certification processes. In summary, it empowers teams to proactively manage known compiler-related issues. By integrating GNATkp into your development process, you can significantly reduce the chances of encountering costly or hazardous errors in deployed systems.

GNAT Pro Assurance customers have access to a special variant of GNATcheck called GNATkp (GNAT Known Problems detector). This tool is packaged with rules designed to detect Ada constructs affected by known problems in compiler releases.

How GNATkp Safeguards Against Known Compiler Issues

<h2>Choosing Ada: Safety, Reliability, and Qualification</h2>Headquartered in Reims, France, Latitude’s mission is to launch small satellites (up to 100 kilograms in Low Earth Orbit) for the European space market. To fulfill this mission the company is developing from the ground up a new launcher called Zephyr. Software is a vital element in this endeavor and the company’s core project involves developing and verifying the launcher flight code. The company was founded in 2019 with an engineering approach that combines a rich industrial heritage with advanced aerospace ingenuity. Their core project revolves around the flight software for the launchers, and a key decision – affecting the effort required in developing, verifying, and maintaining the code - was the choice of programming language, its supporting tools, and the tool vendor.&nbsp;<blockquote>We write everything in Ada, from our own device drivers to the bare-metal programming of our business logic on microcontrollers.- Clément Rousseau, embedded software engineer, Latitude</blockquote>Among the various language technologies that Latitude investigated, Ada stood out as offering the best balance for the company’s needs. Perceived benefits included improved code quality, better safety support, and reasonable qualification cost. “We were drawn to Ada for its potential to simplify certification, even though it wasn’t a strict requirement when we began,” said Remo Smadja, Embedded software engineer at Latitude. “We expect our software to undergo certification in the future, most probably with some of the ECSS (European Cooperation for Space Standardization) standards.”&nbsp;Ada and SPARK have been instrumental in helping Latitude meet its goals. “Ada’s high-level features combined with its systems programming support have been incredibly beneficial,” said Mr. Smadja. “We’ve made significant use of records and representation clauses, which allow us to capture the low-level register representation of microcontrollers. This flexibility is remarkable.” Latitude’s decision to write its entire software in Ada reflects its trust in the language’s safety, reliability, and efficiency. “We write everything in Ada, from our own device drivers to the bare-metal programming of our business logic on microcontrollers,” said Clément Rousseau, embedded software engineer at Latitude. Latitude’s current software strategy prioritizes simplicity and efficiency, and leverages GNAT Pro’s included real-time tasking run-time for safe concurrency. The team found particular benefits in using the Ravenscar profile, a subset of Ada’s concurrency features supported by the certifiable light-tasking runtime profile. “The Ravenscar profile fits our needs perfectly at this point,” said Mr. Rousseau. “Our strategy is to keep everything as straightforward as possible.” By eliminating the need for a complex operating system, Ravenscar has streamlined task analysis and boosted the team’s confidence in mitigating concurrencyrelated issues.&nbsp;AdaCore’s GNAT Pro and GNAT Studio form the core of Latitude’s development environment, additionally, the SPARK language and the SPARK Pro tool suite are used for critical code sections.&nbsp;<img src="https://s3-us-west-1.amazonaws.com/wevolver-project-images/froala%2F1750246746900-asasasassa.png" style="width: 100%px;" class="fr-fic fr-dib"><h2>AdaCore’s Support: Navigating the Transition to Ada</h2>Latitude’s software developers, although experienced in C, C++, and Java, were not formally trained to Ada at the outset of the project. Understanding Ada’s rich set of features and knowing how to use them effectively were therefore critical skills that the team needed to acquire. To meet this goal, Latitude decided in late 2021 to invest in the training and mentoring services that AdaCore offers. AdaCore conducted classes that included hands-on workshops, which provided customized guidance on how to best use Ada’s safe coding practices. After rapidly becoming proficient in Ada, the team readily made the transition to SPARK for critical code sections.&nbsp;The mentorship was instrumental during Latitude’s software development. Initiated while the code architecture was still being designed, AdaCore’s consultation helped the team employ Ada’s best practices in refining the code structure. Mentorship discussions covered topics ranging from design patterns to code analysis techniques such as stack checks. Latitude found the GNAT Pro compiler especially useful; it performs many checks that would have required the use of separate analysis tools in the case of deploying other languages.&nbsp;<h2>Future Outlook: Conquering the “New Space Industry”&nbsp;</h2>Looking ahead, Latitude remains keenly focused on the development of Zephyr’s flight software. In addition, the company plans to continue leveraging Ada and SPARK for future projects. In the rapidly changing landscape of European space startups, companies are always looking to stand out from the crowd. For software, that means implementing innovative functionality through code that is safe, secure, reliable, efficient, and easily maintainable as requirements evolve. Latitude believes in modern programming language technology, backed by AdaCore’s effective professional support, to help them meet their goals.

Ada and SPARK

ORGANIZATIONS.

SHAPING THE INDUSTRY.

Latest Posts

Building the Future: My Path from Software Research to Leadership

How GNATkp Safeguards Against Known Compiler Issues

Latitude Adopts Ada and SPARK for Light Launcher Software in New Space Industry