Location: Toulon, France
Remote: Yes (around CET TZ)
Willing to relocate: No
Technologies: Rust, C++, Python, Terraform, Docker, Linux, CI/CD, Unreal Engine
Résumé/CV: https://cv.thibault.jochem.fr
Email: jobhunt2025@jochem.fr
Hi, I'm Thibault, Senior Software Engineer with 18+ years of experience across game development, embedded systems, backend infrastructure, and deep-tech startups.
Recently Director of Engineering at MetaGravity, where I led teams building cloud-scale multiplayer and simulation infrastructure (Rust, Terraform, AWS/GCP/Azure).
I’m looking for a hands-on engineering position — ideally Rust-heavy — where I can contribute to performant systems, tooling, or low-level backend work.
Also open to short-term contracting through my own company.
The end of the first part. Although it's optional. In the start of part two they make you do it if you skipped it in part one.
I did it in javascript. I didn't really miss typing. Although when things went wrong a lot of debugging was needed. But I think these were logic errors iirc. I'm not sure if typing would have helped.
In part two you build a stack-based virtual machine and then javaesq programming language, that is built on top of the assembler you built in part one.
You can make gates out of more than just electronics (mechanical, electromechanical, pneumatic, hydraulic computers all exist), hence the suggestion to start there --- the abstraction doesn't really leak.
More seriously, it is possible to fit quite a lot of this stuff into an undergrad program - my Cambridge degree included logic gates (including drawing silicon layout with coloured pens), computer architecture (ARM assembler), a lab on FPGAs, Java, Standard ML (for type inference and lambda calculus), and had plenty of time left over for higher level topics.
The market segment of web hosted Git repositories was a relatively new and small market segment when GitHub got started back in 2008.
GitLab didn't appear until 2011, and at the time it didn't feel to me like a direct competitor. So GitHub had quite a bit of extra time to establish its presence and capture a large share of a growing market.
For a large chunk of GitHub's users, GitHub fulfills their needs well enough that they don't feel much motivation to make a change. Even if GitLab is better than GitHub for a person or company, it has to be better enough to be worth the pain of switching.
And I think for most users, that just isn't the case. Speaking anecdotally, there are some things about GitLab I like more than GitHub. And if I were starting out, I'd likely pick GitLab. But all of my code is on GitHub, and although I pay a monthly fee for private repos, it's small enough that it doesn't bother me.
What GitHub has that GitLab didn't offer in my experience last year is a snappy website. Apart from that I'm a huge fan of GitLab, it is superior.
I believe that GitHub is more popular mainly because it was first, gained traction and became synonymous for some people with git itself, and open source.
Location: France
Remote: yes
Willing to relocate: no
Technologies: C++, Qt, QML, C, node.js, Android, Java, C#
Résumé/CV: http://bit.ly/2qY9KkH
Email: look at my resume ;)
I'm a software engineer with 10+ years of professional XP. I mainly work with C++/Qt, but I also used C (low level), javascript/typescript(node.js), Java (Android), C#(Windows Phone) in the past. I'm a quick learner so I can easily adapt to new technologies/stacks/frameworks (but I prefer to stay away from html/frontend).
I worked in several domains : videogames, digital television, social networks, robotics and defense. I'd be happy to discover more, especially VR or blockchain related topics.
Recently Director of Engineering at MetaGravity, where I led teams building cloud-scale multiplayer and simulation infrastructure (Rust, Terraform, AWS/GCP/Azure).
I’m looking for a hands-on engineering position — ideally Rust-heavy — where I can contribute to performant systems, tooling, or low-level backend work.
Also open to short-term contracting through my own company.