My Curriculum Vitae is available for download as a PDF file.

In the follow you can find a list of “keywords: what I have done with this”. This will hopefully tell you something more about my technical skills.

SCRUM Framework: PSM I and PSPO I certifications

search engines: I have experience with Google Cloud Search and ElasticSearch

product owner: that’s my title today. My team has realized the Google Cloud Search integration at LumApps (aka Melania), and the Native Search Rework (aka Brigitte)

perl: frozen-bubble PTP (peer-to-peer and network exchange support for a famous coin-up)

python: (prevents code quality indicators regressions), (gone – xml graphic tools, tests engines, automation of repetitive testing tasks), web crawler to extract metadata about medias

C/C++: L4Ka:Pistachio (microkernel->implemented communicating processes), jidVolo (flight simulator using Massachusetts maps)

C#: No public or open-source project with this language. The NDA I signed with my past employers was too strict to contribute.

java: MSTest Jenkins plugin, MM-DOSE (a branch of the H-DOSE semantic search engine, used to index multimedia contents), Converter (an applet calling the conversion services exported by a webservice)

html, xhtml, xml, xpath: used for sites, for softwares, for thesis (ontologies)

tests: functional testing (Sytel Reply, 06-2006->12-2006; Esker SA, 01-2007->01/2011); unit testing was used for developed softwares; automated testing was used for some web applications and format converters, as well as for printer drivers; load tests and stress tests were performed on sensitive components of my employer’s production architecture; security tests were performed on DMZ components of the production environment.

linux: worked on since 1996. Ubuntu, Gentoo, Debian and RedHat are a subset of the distributions I’ve experience with.

windows: used for everyday work from 2007 to 2016 (development, functional testing, 2003, 2008, up to 2016 and 10)

docker, containers, kube: experience as developer; I have used Windows containers on Windows 2016 and I use docker and kube today for python and golang based microservices.

vmware: used for everyday work, a long long time ago (workstation, esxi, player)

exchange 2003/2007 server: used for functional testing (integration with a 3rd party gateway)

LDAP, Active Directory: used for functional testing (the gateway saves its information in the Active Directory database)

SAP: used for functional testing (sales orders and accounts payable integration with a web application, it required also the knowledge of BAPI, privileges managements, system management). I worked with the SAP R/3 versions: 4.6C, 4.7, 5.0, 6.0 (aka ECC6).

DNS, NFS, SMTP, POP, SSH, SSL, FTP, R*, LPR protocols: functional testing on server/client applications

TCP/IP: well, they’re the underlying layers for all the protocols listed above.. I must know them in order to analyze any kind of network transmission

IPv4 and IPv6: the small and the big one. two addressing spaces for IP addresses. I’m experiencing the transition from one to another in the applications I test. Developers are not yet ready to the big one. 🙂

organization: in the past, chief of the youth section of a local blood donors group. today, responsible for my own projects and for a team of 6 people, as well for the products we realize together.

collaboration: worked as team member for about 10 years; today manager of a team of 6 people.

web applications: I have tested and built them over the last 12 years! 🙂 With technologies ranging from .net (C# 3.0 to 7.0), WCF and EntityFramework to python (2.7 and 3.x) on AppEngine (Standard and Flex) to golang on Kubernetes. SaaS has been a leitmotif of my work experience 🙂

SQL: the products I test use a relational database to store the information. so, SQL is a necessary knowledge in order to analyze the behavior of the application. SQL Server, PostgreSQL, SQLite.

NoSQL: experience with Google Datastore (a lot) and Redis (a little)

GNOME and KDE: two desktop enviroments for Linux. I’m used to use them (and debug them, in case of problems).

  1. No comments yet.
  1. No trackbacks yet.

Leave a Reply

Please log in using one of these methods to post your comment: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: