Skip to main content

Bref je fais du support

Mon métier aujourd'hui est de fournir un service de support aux utilisateurs qui ont choisi la solution logicielle que vend ma société. En pratique, l'utilisateur rencontre un problème avec le produit et je dois l'aider à résoudre le problème en question. Il peut aussi poser des questions, mais les questions rentrent aussi dans le champ des équipes avant vente et de service. 

Dans les faits, la surface des produits que nous commercialisons est assez énorme et j'apprends tous les jours. C'est compliqué parfois, juste de suivre le rythme des sorties, des bugs et des nouvelles fonctionnalités – mais cela fait partie du jeu. Nous avons des boites à outils pour potentiellement analyser les problèmes des produits, et pour reproduire une bonne partie des conditions des clients. Il sera toujours difficile de reproduire de la masse (quelques milliers de clients qui se connecte à une BDD par exemple). Nous travaillons en équipe, jamais seul. C'est super pour apprendre, prendre du recul et des fois comprendre les questions des clients. Mon travail ressemble à du sysadmin, sauf que des fois, je n'ai pas accès aux machines et j'ai un intermédiaire plus ou moins compétent pour la faire à ma place. C'est assez amusant parfois de trouble shooté dans le noir.

J'avais jusqu'à présent toujours refusé les postes contenant le mot support. Dans les faits, le fait de faire du support logiciel me permet de n'interagir qu'avec des informaticiens qui maitrisent plus ou moins bien le produit. Je ne crois pas que j'aurai la même patience, approche si je devais faire du support à l'utilisateur final. Je 'pense' que je m'en tire plutôt pas mal, car au début de ma carrière, j'étais de l'autre côté, c'est moi qui ouvrais des incidents/ ticket su support. J'ai donc une petite idée de ce que la personne veut lire, entendre.

Comments

Popular posts from this blog

Firefox OS's story from a mozilla insider not working on the project

  I clearly remember, but can't date it. I was working for Mozilla messaging at the time ( momo ), being the QA lead for Thunderbird. It was at the end of one of the Mozilla All-hands, maybe in 2011 or 2012. At one of the ending keynotes, we were introduced to Boot 2 Gecko. A hack that would let US - Mozilla own the platform to run a mobile browser on. At the time, the iPhone was going strong and Google was trying to catch up with Android. MeeGo had been in development at Nokia for a while but was going nowhere even when Intel tried to help. Blackberry was slowly starting to die. In the Silicon Valley everything was about mobile, mobile, mobile and the emerging South Easter Asian market, where people would skip computers and use smartphones to join the internet revolution. We were struggling with Chrome and the massive investment by Google to take market share. Our Firefox port on Android was having loads of issues. We were denied by Apple's policies to be present on iPhones....

Key signing party at fosdem 2024

I'm organizing a GnuPG key signing party in order to bolster our web of trust , since there is no official ksp this year. I have organized a few in the past using tools like biglumber (website is gone, if someone know of a replacement or where the source code of site is, I might end up running one again) and others tools . I've also run once the KSP at FOSDEM and helped running it a few other times.    === Details below === When, Where   We'll meet in front of the infodesk stand in building K around 12:00 Sunday Feb 4th 2024. I'll have a sing of some sort with KSP and or Key Signing Party . Once enough participants show up we will move outside to proceed with the party. What to Bring Warm cloths as the party will happen outside this year, like in the good old days. I hope it won't rain, but it might. Piece of papers with your fingerprint written on them. Each piece should look like below:  $ gpg --fingerprint 34246C61F792FBCC1F23BFF296BD1F38FEA32B4D pub ...

Are mozilla's fork any good?

To answer that question, we first need to understand how complex, writing or maintaining a web browser is.  A "modern" web browser is : a network stack, and html+[1] parser,  and image+[2] decoder, a javascript[3] interpreter compiler, a User's interface, integration with the underlying OS[4], And all the other things I'm currently forgetting.   Of course, all the above point are interacting with one another in different ways. In order for "the web" to work, standards are developed and then implemented in the different browsers, rendering engines. In order to "make" the browser, you need engineers to write and maintain the code, which is probably around 30 Million lines of code[5] for Firefox. Once the code is written, it needs to be compiled [6] and tested [6]. This requires machines that run the operating system the browser ships to (As of this day, mozilla officially ships on Linux, Microslop Windows and MacOS X - community builds for *BSD do ex...