Javascript / Angular JS / Dataviz
I have 4 years experience as a JS engineer. I consider this language, despite its flaws, to be the next standard for connected apps, I dug deep into it.1987 ~ 1998 |
1999 ~ 2001 |
2002 |
2004 |
2005 |
2006 |
2007 |
2008 |
2009 |
2010 |
2011 |
2012 |
2013 |
2014 |
2015 |
2016 |
2017 |
2018 |
2019 |
2020 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| First steps (homebrew games mostly) | Diploma in Computer science Engineering (DESS) - Toulouse University. (Links in French) | ||||||||||||||||||
| Worked professionally for the now defunct Neurosys (subsidiary of the also defunct Sumotori Networks) | |||||||||||||||||||
| Work for Berger-Levrault ... | Work for Inetum (ex-GFI) ... | ||||||||||||||||||
| Fullstack Software Developer | Senior fullstack engineer | Senior Research And Development Software Engineer | Senior Fullstack Developer | Technical architect / manager | |||||||||||||||
| Teacher (University of Montpellier) | |||||||||||||||||||
Attitudes
Perceiving function
Judging function
Dominant/Auxiliary Function
You'll find here the explanation of how I wanted to code this résumé, as well as some hightlights about its functionalities.
All the source of this résumé has been hand coded : the "how" I wanted to implement is the use of plain HTML and CSS, with no external library, to show that a fair amount of functionalities can be accessed without needing additional scripts. Also, I tried to ensure that semantics and presentation were separated : this provided me the possibility of conceiving different presentations for different format factors and medias. Just try to resize your window when viewing this résumé to see what I mean.
In this résumé, I included some technical points I wanted to detail for those interested :
This implementation could be improved, there a some of the ideas that could be coded :
In fact, a résumé is a subject that can lead to experiments without end, including many technologies.
First of all, the main reason that motivated me in making this web résumé is the fact that, during the five years I was committed to engineer recruitment, all of the résumés I received were more or less the same. This document is meant to display factual data to let the recruiter know better about a candidate. And because a résumé is not associated with an unique formal presentation, this document can be used to demonstrate a certain creativity, details that will make the candidate stand out of the crowd. Thinking about this, I realized that a software developer - specifically with web skills - should develop its résumé.That's why I began writing the code that ended as the résumé you are reading :)