Why 'Works on My Machine' Happens in JavaScript Dev

Most production bugs I’ve seen around environment variables aren’t caused by missing values. They’re caused by misunderstanding what environment variables actually are. A few things that have burned teams I know: - Environment variables are an OS primitive. Every process gets a flat key-value copy of its parent’s environment. A copy, not a reference. What your child process changes, your parent never sees. - Your .env file does nothing on its own. Something has to read it. And most tools, including dotenv, will NOT overwrite a variable that already exists. So if your shell profile already exports DATABASE_URL, your .env is silently ignored. This is probably the most common “works on my machine” culprit. - Docker starts with a clean slate. It does not inherit your shell environment. If you’re not explicitly passing variables with -e or –env-file, the container doesn’t know they exist. - React’s process.env is not real runtime config. The bundler replaces every reference with a literal string at build time. That value is now hardcoded in the JavaScript your users download. If you put a secret in REACT_APP_anything or NEXT_PUBLIC_anything, it is not a secret anymore. - Build time and runtime are fundamentally different. A frontend bundle bakes values in at build time. An Express server reads the actual process environment when it starts. You can change a backend variable and restart. You cannot do that with a bundled frontend without rebuilding. Deleted a committed secret in the next commit? The key is still in git history. git show will find it. The only fix is to rotate the credential. The mental model that fixes most of this: secrets always runtime, never build time, never committed to source code. #SoftwareEngineering #DevOps #WebDevelopment #BackendDevelopment #JavaScript #Docker #NodeJS #EngineeringLeadership

TypeScript doesn’t make your code safe. It makes it safer. There’s a difference. Here’s why 👇 TypeScript checks: ✔ Compile-time types But runtime: ❌ Anything can happen Example: → API returns unexpected data → Type says “string” → Runtime gives null Result: → Crash What works: ✔ Validate data at runtime ✔ Don’t blindly trust types ✔ Use proper guards Key insight: TypeScript is not a runtime safety tool. It’s a development aid. #TypeScript #JavaScript #Frontend #Backend #SoftwareEngineering #Engineering #Programming #Tech #CleanCode

Stop writing TypeScript interfaces by hand. 🛑 Paste your JSON → pick your output style → get clean, production-ready TypeScript in seconds. Modular or single-block. Interface or type syntax. Zero server, 100% private. ⚡ Built this tool for developers who have better things to do than manually type out API response shapes. Try it free 👉 https://lnkd.in/dn76zm9R Read the full breakdown at hamidrazadev.com 🔗 #TypeScript #WebDev #DevTools #JavaScript #FrontendDev #ReactJS #NextJS #OpenSource #Programming #100DaysOfCode

Day 4 of 30 Days of TypeScript 🚀 Today’s topic: any vs unknown A lot of developers use any thinking it gives flexibility… But in reality, it removes the biggest advantage of TypeScript — type safety. Here’s the truth: 🔴 any Disables type checking Allows anything (even wrong code) Can lead to runtime bugs 🟢 unknown Forces you to validate data Keeps your code safe Encourages better patterns Example 👇 let data: unknown = "hello"; if (typeof data === "string") { console.log(data.toUpperCase()); // ✅ safe } 👉 Rule of thumb: If you don’t know the type yet, use unknown — not any. Because good developers don’t just make code work… They make it reliable. #TypeScript #WebDevelopment #JavaScript #Frontend #CleanCode #100DaysOfCode

TypeScript devs explaining why you should rewrite everything in TypeScript: "Type safety!" "Catches bugs at compile time!" "Better autocomplete!" "Refactoring is so much easier!" Cool. How long did you spend defining interfaces for a function that returns a string? "...2 hours." Meanwhile JavaScript devs wrote the entire feature, shipped it, got user feedback, and iterated twice. Does TypeScript catch bugs? Yes. Does your 500-line type definition file prevent runtime errors? No. Will TypeScript devs care? Absolutely not. Both languages are incredible. But treating every project like it's a banking system is how you end up debugging generic constraints at 2 AM for a landing page. Use the right tool. Not the safest one. #TypeScript #JavaScript #Programming #DevLife #TechTwitter

🚀 Stop installing 'tsx' or 'ts-node' for your simple scripts! Node.js 22 just changed the game for TypeScript developers. With the introduction of the --experimental-strip-types flag, Node.js can now execute TypeScript files directly. No more complex build steps or heavy transpilers just to run a quick automation script or a microservice. How it works: ✅ Node.js uses the Amaro (swc-based) library to strip type annotations. ✅ No type checking is performed (keeping it lightning fast). ✅ It supports modern syntax including interfaces, enums, and namespaces. This is a massive boost for Developer Experience (DX). It reduces the barrier between development and execution, making Node.js feel more modern and integrated than ever. Are you still using a build step for every small TS project, or are you moving to native execution? #NodeJS #TypeScript #WebDevelopment #Backend #JavaScript #SoftwareEngineering #Coding #Programming #FullStack #SoftwareArchitecture #CleanCode #WebDev #TechUpdates #DeveloperExperience #OpenSource #DevOps #SoftwareDevelopment #NodeJS22

Unpopular opinion: most Full-stack TypeScript with tRPC — end-to-end type safety tutorials are teaching you the wrong thing. They teach syntax. They should teach systems thinking. The difference between a junior and senior developer isn't knowing more APIs. It's knowing which problems are worth solving and which to delegate — to a teammate, a library, or an AI. What's the most valuable lesson you've learned that no tutorial ever taught you? #WebDevelopment #TypeScript #Frontend #JavaScript

Unpopular opinion: most Full-stack TypeScript with tRPC — end-to-end type safety tutorials are teaching you the wrong thing. They teach syntax. They should teach systems thinking. The difference between a junior and senior developer isn't knowing more APIs. It's knowing which problems are worth solving and which to delegate — to a teammate, a library, or an AI. What's the most valuable lesson you've learned that no tutorial ever taught you? #WebDevelopment #TypeScript #Frontend #JavaScript

Built a clean API. Tested in Postman. Everything works perfectly ✅ Frontend integration starts… Suddenly: ❌ Undefined errors ❌ Unexpected responses ❌ “It was working before” Developer life 😄 But honestly, this is where real debugging skills grow — understanding the full flow (frontend ↔ backend ↔ database) matters more than just writing code. #developerlife #backenddeveloper #debugging #restapi #webdevelopment #programming

Day 7: Top 5 Beginner Mistakes in TypeScript 🚨 When starting with TypeScript, most devs don’t struggle with syntax… they struggle with how to think in types. Here are 5 mistakes I see all the time 👇 1. Overusing any 😬 It disables TypeScript completely. You’re basically back to JavaScript. 2. Ignoring unknown 🤷♂️ unknown forces safety checks. Use it when you don’t know the type yet. 3. Not defining types early 🧩 Relying only on inference can make large apps messy. 4. Misusing interfaces & types 🔁 They’re similar, but not interchangeable in all cases. 5. Skipping strict mode ⚠️ This is where TypeScript actually shines. 💡 TypeScript isn’t just about adding types. It’s about writing predictable, maintainable code. Follow along for more in my TypeScript series 🚀 #TypeScript #JavaScript #WebDevelopment #Frontend #Coding #Developers