<?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: Michel Jee</title>
    <description>The latest articles on DEV Community by Michel Jee (@micheljee).</description>
    <link>https://dev.to/micheljee</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3941384%2Fceb027db-ce96-4191-81cc-579bbe0bfa96.png</url>
      <title>DEV Community: Michel Jee</title>
      <link>https://dev.to/micheljee</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/micheljee"/>
    <language>en</language>
    <item>
      <title>How do you handle environment-specific configuration in your Node.js projects?</title>
      <dc:creator>Michel Jee</dc:creator>
      <pubDate>Sat, 30 May 2026 07:41:56 +0000</pubDate>
      <link>https://dev.to/micheljee/how-do-you-handle-environment-specific-configuration-in-your-nodejs-projects-4lj1</link>
      <guid>https://dev.to/micheljee/how-do-you-handle-environment-specific-configuration-in-your-nodejs-projects-4lj1</guid>
      <description>&lt;p&gt;I've been using dotenv for years, but recently started experimenting with a more structured approach using JSON config files with environment overrides. Here's what I came up with:&lt;/p&gt;

&lt;p&gt;javascript&lt;br&gt;
const config = {&lt;br&gt;
  development: {&lt;br&gt;
    apiUrl: '&lt;a href="http://localhost:3000" rel="noopener noreferrer"&gt;http://localhost:3000&lt;/a&gt;',&lt;br&gt;
    debug: true&lt;br&gt;
  },&lt;br&gt;
  production: {&lt;br&gt;
    apiUrl: '&lt;a href="https://api.example.com" rel="noopener noreferrer"&gt;https://api.example.com&lt;/a&gt;',&lt;br&gt;
    debug: false&lt;br&gt;
  }&lt;br&gt;
};&lt;/p&gt;

&lt;p&gt;const env = process.env.NODE_ENV || 'development';&lt;br&gt;
const envConfig = config[env];&lt;/p&gt;

&lt;p&gt;// Allow environment variables to override&lt;br&gt;
for (const key in envConfig) {&lt;br&gt;
  if (process.env[key.toUpperCase()]) {&lt;br&gt;
    envConfig[key] = process.env[key.toUpperCase()];&lt;br&gt;
  }&lt;br&gt;
}&lt;/p&gt;

&lt;p&gt;export default envConfig;&lt;/p&gt;

&lt;p&gt;This gives me a clean default config with the flexibility to override via env vars. I've been using a small library called EnvManager that adds validation and schema support. What's your preferred config management strategy?&lt;/p&gt;

</description>
      <category>ai</category>
      <category>programming</category>
      <category>productivity</category>
      <category>beginners</category>
    </item>
    <item>
      <title>How to Filter Bot Traffic in GA4 for Accurate SEO Analytics Using Python</title>
      <dc:creator>Michel Jee</dc:creator>
      <pubDate>Mon, 25 May 2026 05:14:07 +0000</pubDate>
      <link>https://dev.to/micheljee/how-to-filter-bot-traffic-in-ga4-for-accurate-seo-analytics-using-python-3kk4</link>
      <guid>https://dev.to/micheljee/how-to-filter-bot-traffic-in-ga4-for-accurate-seo-analytics-using-python-3kk4</guid>
      <description>&lt;p&gt;Ever had your analytics show a sudden spike in traffic, only to realize it's all bots? I recently discovered a way to filter out bot traffic using a simple Python script that checks user-agent strings and request patterns. It's not perfect, but it helped me clean up my data significantly. If you're dealing with similar issues, check out how I did it.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fju77q222ympku73wlwd1.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Farticles%2Fju77q222ympku73wlwd1.png" alt=" " width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
      <category>programming</category>
      <category>beginners</category>
      <category>python</category>
      <category>performance</category>
    </item>
  </channel>
</rss>
