Engineering manager at @PayFit @PayFitEng

Joined November 2011
26 Photos and videos
Jérémy Prioux retweeted
I'm Boris and I created Claude Code. Lots of people have asked how I use Claude Code, so I wanted to show off my setup a bit. My setup might be surprisingly vanilla! Claude Code works great out of the box, so I personally don't customize it much. There is no one correct way to use Claude Code: we intentionally build it in a way that you can use it, customize it, and hack it however you like. Each person on the Claude Code team uses it very differently. So, here goes.
1,319
7,017
54,538
8,178,218
Jérémy Prioux retweeted
A few months ago, I built a custom URL shortener. Quick refresher: a URL shortener does two things: 1. Creates short URLs that map to long URLs 2. Redirects short URL requests to those long URLs. Designing this was a fantastic engineering challenge. Here’s a look at my design process! A thread 🧵 - 1/N
1
2
28
3,644
Jérémy Prioux retweeted
How did I not know these work in GitHub😍
75
588
6,105
451,493
Jérémy Prioux retweeted
Let's go for the @Breizhcamp 2024 conference in Rennes, starting today and featuring 3 speakers from @PayFit : Caroline Becker @Horgix talking about @MongoDB & how to get away from a monolithic hell, and @MartinBahier talking about @OBSProject ! May the force be with them 🚀
3
3
324
Jérémy Prioux retweeted
In a week from now, on Tuesday 4th June, @PayFit will have the pleasure to host the MongoDB Paris meetup! Incl. a talk sharing our own experience and plans with MongoDB at PayFit, by @Horgix and Laurentiu Capatina 🎉 See meetup.com/paris-mongodb-use… for more and to signup for it!
4
4
607
Jérémy Prioux retweeted
This demo is insane. A student shares their iPad screen with the new ChatGPT GPT-4o, and the AI speaks with them and helps them learn in *realtime*. Imagine giving this to every student in the world. The future is so, so bright.
1,414
7,958
43,813
10,927,828
Jérémy Prioux retweeted
libyear - A simple measure of software dependency freshness // Adding it to our CIs right now! libyear.com/
1
4
689
Jérémy Prioux retweeted
Google Cloud accidentally deleted a company's entire cloud environment (Unisuper, an investment company, which manages $80B). The company had backups in another region, but GCP deleted those too. Luckily, they had yet more backups on another provider. theguardian.com/australia-ne…
477
3,489
17,457
5,964,141
Jérémy Prioux retweeted
Rôle intéressant sur un projet : DRI (Directly Responsible Individual) ou Personne Directement Responsable. Cela marche sur un projet, une initiative ou une activité. handbook.gitlab.com/handbook…
1
3
10
1,959
Jérémy Prioux retweeted
8 Feb 2024
Ravi de revenir 6 ans plus tard à @tourainetech et cette fois-ci, je parlerai de l’IA 🤖 et l’impact sur ma façon de coder 🧑‍💻 #tnt24 Rdv à 12h10 en Bio
2
4
11
1,019
Eating playlist ? 🤷 @Spotify 😅
4
75
Jérémy Prioux retweeted
7 principles 9 ways I've learned to improve how you ship software First the 7 principles: 1. Speed When it comes to deploys speed is safety, and small is speed. The speed of shipping has massive compounding effects. If your deploy takes hours, you’re going to want to make damn sure there are no bugs, because if you find a critical bug right after a deploy goes live, then you have to wait another couple hours for your fix to go live.
2
7
32
5,702
Jérémy Prioux retweeted
7 Jan 2024
Started using Nitro.js this weekend in a new app, it's been awesome. best of what I love about both @nextjs & @UseExpressJS - File based routing - Zero config setup w/ TypeScript out of the box - Hot module replacement out of the box - Small < 1MB nitro.unjs.io/
20
21
293
33,296
Jérémy Prioux retweeted
L’épisode annuel est sorti, j’espère qu’il vous plaira
3 Jan 2024
Aujourd'hui, j'ai eu la chance de recevoir @waxzce, le CEO de Clever Cloud pour faire le bilan tech de 2023. Il faut entendre ce qu'il a à dire à propos de l'IA. Des bouts de scotch tiennent le navire ensemble ! À écouter sans attendre : ifttd.io/episodes/bilan-2023
3
5
19
4,483
Jérémy Prioux retweeted
This is one big difference between the three cloud providers: When AWS or Azure has an outage: their parent companies (Amazon and Microsoft) will lose money/churn customers etc. When GCP has an outage: it's business as usual for Google. Which is more incentive for reliability?
Google doesn't build anything meaningful on top of GCP, and so Google doesn't feel the impact of these outages. This is distinctively different from eg AWS (Amazon is built on it) and Azure (tons of Microsoft products built on it). You wonder what happened if they did!
30
93
1,004
358,958
Venez voir Julien et Josian dans les bureaux de @PayFit ! @PayFitEng
This tweet is unavailable
1
7
563
Jérémy Prioux retweeted
[🚨🚨[FRANCE]CyberAlert - 🇫🇷 Les données du CHU de Rennes publiées] Le groupe de cybercriminels #bianlian commence à mettre en ligne 300Go de données... On y retrouve des données sensibles comme : - des données personnelles - des documents financiers - des données du personnel de santé de l'hôpital - ... À date, même si rien ne permet d'affirmer qu'il y ait un rapport entre la #cyberattaque avortée que le #ChuDeRennes subissait il y a quelques semaines et cette publication, la prudence est de mise. Jusqu'ici, le groupe de #ransomware #bianlian n'avait pas revendiqué la cyberattaque contre le CHU de Rennes. Affaire à suivre dans les heures à venir... D'ici là, si vous êtes passé par le CHU de Rennes dans les 3 dernières années, soyez extrêmement PRUDENTS ! La période est propice pour différentes arnaques. Sensibilisez vos proches et les personnes plus fragiles. Cybèrement vôtre, SaxX #hopital #cybersécurité #cyberalert cc @SamuelNohra @Julien_J0ly @OuestFrance @LeTelegramme
16
309
452
117,522
Jérémy Prioux retweeted
29 Jul 2023
As the first AWS service, I almost forgot SQS is still stuck in XML land until I saw this announcement just now. aws.amazon.com/about-aws/wha… If you're using an official AWS SDK, there is no code change required on your part. Just upgrade the SDK to the specified version and it'll start making requests to SQS in JSON. 23% reduction of end-to-end response time and lower client-side CPU and memory use. It's the best kind of performance improvement because we don't really have to do anything 😎 (besides upgrading the SDK)
9
35
236
58,010