<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Geoffroy Streit</title>
    <description>The latest articles on DEV Community by Geoffroy Streit (@hylst).</description>
    <link>https://dev.to/hylst</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4252537%2F672286e3-45aa-4681-80f2-b76ddc4418fe.webp</url>
      <title>DEV Community: Geoffroy Streit</title>
      <link>https://dev.to/hylst</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/hylst"/>
    <language>en</language>
    <item>
      <title>I audited 40 side projects. What I removed mattered more than what I built.</title>
      <dc:creator>Geoffroy Streit</dc:creator>
      <pubDate>Thu, 19 Nov 2026 21:12:44 +0000</pubDate>
      <link>https://dev.to/hylst/i-audited-40-side-projects-what-i-removed-mattered-more-than-what-i-built-1gp6</link>
      <guid>https://dev.to/hylst/i-audited-40-side-projects-what-i-removed-mattered-more-than-what-i-built-1gp6</guid>
      <description>&lt;h1&gt;
  
  
  I audited 40 side projects. What I removed mattered more than what I built.
&lt;/h1&gt;

&lt;p&gt;In November 2026 I stopped building for a couple of weeks and went through every app on hylst.fr, one by one. I expected bugs. I found promises my code wasn't keeping.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why I did this
&lt;/h2&gt;

&lt;p&gt;I have around 40 apps and websites. They grew out of curiosity over several years, not out of a plan. That's a nice way to build and a terrible way to maintain. By mid-November I had enough small interruptions to know I needed a full pass.&lt;/p&gt;

&lt;p&gt;I'll be honest: I'm not a security expert. I'm a self-taught developer with a thing for making tools that stay out of your way. What I did was simple, almost boring: open each app, read the text on the screen, then read the code behind it, and compare the two.&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Dependencies: no critical findings, but that's not luck
&lt;/h2&gt;

&lt;p&gt;On 16 November, zero critical, high or moderate vulnerabilities in production across the menu (Guide Maths, À votre service, HylstDevToolBox, DataLab, Next.js 16.4.6...).&lt;/p&gt;

&lt;p&gt;That number only means something with the work behind it: going through libraries app by app, updating what needed updating, removing what nobody used. It's not a badge. It's hygiene.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Secrets that shouldn't survive a tab close
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;DataLab: remote API keys no longer survive closing the tab.&lt;/li&gt;
&lt;li&gt;HylstDevToolBox: clipboard history is gone on close.&lt;/li&gt;
&lt;li&gt;À votre service: generated passwords no longer sit in plain text in the browser.&lt;/li&gt;
&lt;li&gt;Guide Maths: the notepad now stores a PBKDF2 hash, 210,000 iterations.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;None of this is clever. It's just the difference between "we don't store your data" and actually not storing it.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Cutting the external calls
&lt;/h2&gt;

&lt;p&gt;No more Google Fonts or Unsplash calls. In Brevet, a student's nickname no longer leaves the browser to generate an avatar; it's drawn locally. CSP policies per section, legal notices everywhere.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. The honesty pass (this was the hard one)
&lt;/h2&gt;

&lt;p&gt;In À votre service I removed 27 mentions of encryption or cloud sync that the code wasn't doing yet. All 87 tools were checked one by one.&lt;/p&gt;

&lt;p&gt;On Bulle Sensorielle I deleted every "therapeutic" claim. It's a relaxation tool, not a medical device. Let's call a cat a cat.&lt;/p&gt;

&lt;p&gt;I wrote those words. Nobody forced me to. They were optimistic descriptions of things I intended to build. That's not a small thing when someone types a password into your tool.&lt;/p&gt;

&lt;h2&gt;
  
  
  5. The funny bits
&lt;/h2&gt;

&lt;p&gt;An audit always turns up something ridiculous:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Brevet's profile save had been silent since June because of a circular import nobody saw.&lt;/li&gt;
&lt;li&gt;The React quiz had got into the habit of quietly overwriting the Java quiz's progress. Territory war in the browser.&lt;/li&gt;
&lt;li&gt;3D Creator's service worker thought reloading the page mid-use was a good idea.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;All back in order.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I'd tell someone doing the same
&lt;/h2&gt;

&lt;p&gt;Every deploy is now rebuilt from a clean clone and checked with browser scenarios across 49 sections. That's the real fix: not the one-time cleanup, the thing that stops the dust coming back.&lt;/p&gt;

&lt;p&gt;Three rules I'd keep:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Check the text against the code, not the other way around.&lt;/li&gt;
&lt;li&gt;Delete a promise before you implement it, not after.&lt;/li&gt;
&lt;li&gt;If it can stay in the browser, keep it in the browser.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Nothing magical here. Just rigour and digital hygiene so these tools stay reliable, sober and respectful of the people using them.&lt;/p&gt;

&lt;p&gt;What's the most surprising thing you found during your own cleanup?&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>privacy</category>
      <category>opensource</category>
      <category>localfirst</category>
    </item>
  </channel>
</rss>
