Removed experiences pages (privacy reasons)
This commit is contained in:
parent
9236eee9cc
commit
76ce6c40b5
@ -33,7 +33,6 @@
|
||||
<a href="/">Home</a>
|
||||
<a href="/skills">Skills</a>
|
||||
<a href="/projects">Projects</a>
|
||||
<a href="/experiences">Experiences</a>
|
||||
<a href="/hobbies">Hobbies</a>
|
||||
|
||||
<a href="https://git.tcharles.fr" class="external">Gitea</a>
|
||||
|
@ -1,137 +0,0 @@
|
||||
<article id="ifremer">
|
||||
<h1 id="ifremer2018">Ifremer</h1>
|
||||
|
||||
Between 2018 and 2019 I worked in Ifremer Brest, on a distributed data processing platform for scientific data.
|
||||
|
||||
## Project
|
||||
|
||||
The original code-base had a lot of un-necessary complexity caused by a long history of feature added without doing any proper code architecture change (the project started around 2004). The platform was strongly tied to the enterprise environment, with dependencies on specific software versions, environment variables and NFS shares.
|
||||
|
||||
My **main missions** were:
|
||||
|
||||
- **Decoupling the platform from the production environment**, for easier testing during development. The applications were very dependent on NFS shares and specific environment files.
|
||||
- **Removing unused features** and reworking others while **keeping the compatibility** when possible. The platform shares a lot of similarities with continuous integration platforms, and Gitlab CI was a good inspiration for improving / replacing existing features.
|
||||
- **Migrating from Python 2.4 to Python 3**, and **upgrading libraries**.
|
||||
- Setting up better deployment tools, mainly with Anaconda environments and Docker containers.
|
||||
- Making the software **interoperable with current services**: sending logs to Elasticsearch and RabbitMQ, replacing SQLite with PostgreSQL, sending processing jobs to PBS Pro, ...
|
||||
|
||||
## Skills
|
||||
|
||||
- Python 2 to 3 migration
|
||||
- Unearthing, understanding and upgrading legacy code :)
|
||||
- Code refactoring, quality improvements, bug fixes, ... and adding new features
|
||||
</article>
|
||||
|
||||
|
||||
<article>
|
||||
<h1 id="ifremer2016">Ifremer</h1>
|
||||
|
||||
Between 2016 and 2017 I worked in Ifremer Brest, on marine observatory stations. During this period I improved the developer environment, installing a lot of automation tools for building, checking and deploying/flashing the software on a testing environment.
|
||||
|
||||
I also worked on understanding / reverse engineering an acoustic MODEM protocol.
|
||||
|
||||
## Skills
|
||||
|
||||
- Bare metal C development
|
||||
+ ARM EFM32 board
|
||||
- Gitlab / CI / Chat server setup
|
||||
+ Gitlab instance
|
||||
+ Mattermost instance, linked to Gitlab
|
||||
+ GitlabCI (`gitlab-ci-runner`) to run automated tests
|
||||
+ Automated updates of both the server OS (CoreOS) and services (mostly Docker containers)
|
||||
+ Automated CoreOS setup changes through GitlabCI
|
||||
|
||||
</article>
|
||||
|
||||
<article>
|
||||
# Thales Airborne Systems
|
||||
|
||||
<div class="cinema">
|
||||
<a
|
||||
data-lightbox="thales"
|
||||
href="img/thales-1.jpg"
|
||||
title="Company logo">
|
||||
![](/img/thales-1.jpg)</a>
|
||||
</div>
|
||||
|
||||
Between 2014 and 2015, I worked in sandwich courses at Thales Airbourne Systems.
|
||||
|
||||
My mission was to __evaluate Yocto__ for building embedded Linux distributions, tuned to __match__ as much as possible the __system capabilities__.
|
||||
|
||||
Yocto is a __recent__ project based on OpenEmbedded Bitbake, similar to Buildroot. It __automates__ the task of building, installing and configuring softwares to __assemble__ a __complete Linux distribution__.
|
||||
|
||||
Yocto comes also with a lot of tools, that allows the user to execute unit tests on an emulated system, serve packages and provide updates, check that licenses are respected, ...
|
||||
|
||||
## Skills
|
||||
- Yocto toolchain
|
||||
- Linux ecosystem
|
||||
- Linux Kernel
|
||||
- Build automation
|
||||
|
||||
## More
|
||||
- [Documentation](https://git.tcharles.fr/tcharles/yocto-public) (may be incomplete)
|
||||
- [School presentation slides (fr)](https://tcharles.fr/slides/yocto-isen-slides)
|
||||
|
||||
</article>
|
||||
|
||||
|
||||
<article>
|
||||
# Thales Underwater Systems
|
||||
|
||||
<div class="cinema">
|
||||
<a
|
||||
data-lightbox="thales"
|
||||
href="img/thales-1.jpg"
|
||||
title="Company logo">
|
||||
![](/img/thales-1.jpg)</a>
|
||||
</div>
|
||||
|
||||
Between 2012 and 2013, I worked in sandwich courses at Thales Underwater Systems, on the __portage__ of the graphic part of the __Android SDK__ on RHEL5, and on the creation of a __custom window manager__ based on XLib.
|
||||
|
||||
|
||||
## Skills
|
||||
- Java, C/C++ dev.
|
||||
- Building Android SDK
|
||||
- Desktop Environment & Window Manager
|
||||
- X11 Server
|
||||
|
||||
## More
|
||||
- [Slides (fr)](/res/Memoire_obf.pdf)
|
||||
|
||||
</article>
|
||||
|
||||
|
||||
|
||||
|
||||
<article>
|
||||
# Genesys internship
|
||||
|
||||
<div class="cinema">
|
||||
<a
|
||||
data-lightbox="genesys"
|
||||
href="img/genesys-1.jpg"
|
||||
title="Company logo">
|
||||
![](/img/genesys-1.jpg)</a>
|
||||
</div>
|
||||
|
||||
In 2012, I did a 7 week internship in Genesys, an affiliate of Alcatel Lucent.
|
||||
|
||||
I worked on debugging the VBS Scripts for __automated regression tests__, started by another student the preceding year.
|
||||
|
||||
</article>
|
||||
|
||||
|
||||
|
||||
<article>
|
||||
# Electronics Club
|
||||
|
||||
Since 2011, I am an active member of the Electronics Club of ISEN Brest, a __student-driven club__ specialized in __electronics__, __computer sciences__ and __robotics__, hosted by my engineer school.
|
||||
|
||||
|
||||
## Skills
|
||||
- Team managing
|
||||
- Meetings organization
|
||||
- Event poster designs
|
||||
- Repair/configuration of PC running Windows/Linux, and electronic hardware
|
||||
- Electronic and programming projects
|
||||
</article>
|
Loading…
Reference in New Issue
Block a user