Mohammed Samrose’s Post

Leaving Node.js behind: Building a raw HTTP server in Go. After spending the week locking down my PostgreSQL database, it is finally time to build the API server. But moving from Node.js to Go requires a complete mental reset. In Node, you reach for Express.js immediately. You write app.get("/", (req, res) => {}) and you're good to go. In Go? There is no Express by default. You build it raw using the standard library (net/http). This simple block of code completely flips the script on how you handle data. package main import (   "log"   "net/http" ) // The mental shift happens HERE: (w, r) func handler(w http.ResponseWriter, r *http.Request) {   w.Write([]byte("hello world")) } func main() {   http.HandleFunc("/", handler)   if err := http.ListenAndServe(":8080", nil); err != nil {     log.Fatal(err)   } } In Node, it’s always (req, res) - Request first, Response second. In Go, the handler looks like this: (w http.ResponseWriter, r *http.Request). Response first, Request second. Why? Because Go treats the ResponseWriter (w) as a literal tool you are handed to execute your job. The server effectively says: "Here is your pen (w). Now look at the paperwork (r) and write your response back immediately." I'm officially writing my first route to start the Auth sequence. It’s raw, it’s fast, and there’s no framework magic hiding the fundamentals from me. We move! 💪🏾 To the devs who made the switch from JavaScript/Node.js to Go: What was the hardest habit you had to break? Let’s gist in the comments 👇🏾 #Golang #NodeJS #BackendEngineering #API #SoftwareDevelopment #TechBro #TechInNigeria #WeMove

Node.js vs. Go HTTP Server 🌐 Leaving Node.js behind: Building a raw HTTP server in Go 🚀💻 After spending the week locking down my PostgreSQL database, it is finally time to build the API server. But moving from Node.js to Go requires a complete mental reset. In Node, you reach for Express.js immediately. You write app.get("/", (req, res) => {}) and you're good to go. In Go? There is no Express. You build it raw using the standard library (net/http). And Go completely flips the script on how you handle data. In Node, it’s always (req, res) — Request first, Response second. In Go, the handler looks like this: func handler(w http.ResponseWriter, r *http.Request) Response first, Request second. Why? Because Go treats the ResponseWriter as a literal tool you are handed to execute your job. The server says: "Here is your pen (w). Now look at the paperwork (r) and write your response back immediately." I'm officially writing my first route to start the Auth sequence (Signup/Login). It’s raw, it’s fast, and there’s no framework magic hiding the fundamentals from me. We move! 💪🏾 To my devs who made the switch from JavaScript/Node.js to Go: What was the hardest habit you had to break? Let’s gist in the comments 👇🏾 #Golang #NodeJS #BackendEngineering #API #SoftwareDevelopment #TechBro #TechInNigeria #WeMove

I just shipped a CLI tool that saves developers hours of setup time. It's called better-ts-stack. Run one command. Answer a few prompts. Get a production-ready TypeScript project — fully wired. Here's what it scaffolds for you: → Backend API with Express + TypeScript → Full-stack app with Next.js 16 + React 19 → Database: PostgreSQL or MongoDB → ORM: Prisma or Drizzle or Mongoose → Auth: JWT (backend) or Better Auth (full-stack) → Docker setup, ESLint, Prettier, .env — all included No more copy-pasting boilerplate from old projects. No more spending the first 2 hours of a new project just "setting things up." Just run: npx better-ts-stack And you're building within minutes. NestJS support is coming next. Would you use a CLI like this in your workflow? 👇 Live link : https://lnkd.in/ddfFKZ_R Github : https://lnkd.in/d4c9ZetQ #BuildInPublic #TypeScript #NextJS #FullStackDeveloper #OpenSource

I just published my first npm package — dotenv-audit Ever had your app crash in production because someone forgot to set an environment variable? I built a tool that solves this. It scans your actual codebase, finds every process.env usage, and tells you exactly what's missing — with file paths and line numbers. No schema to write. No config needed. Just run: npx dotenv-audit --ask What it does: Scans .js, .ts, .jsx, .tsx, .vue, .svelte files automatically Detects all patterns — dot access, bracket access, destructuring, Vite env Generates .env files with smart placeholder values Auto-detects your database (MongoDB, PostgreSQL, MySQL) from package.json Supports monorepos — creates separate .env per service Filters out framework built-ins (Vite's DEV, MODE, etc.) Zero dependencies. 15KB package size. Interactive mode asks you step by step: Want an ENV_SETUP.md with all missing variables? ✓ Want a .env file generated with smart defaults? ✓ Check it out: https://lnkd.in/gqRAPjGN Would love to hear your feedback! #nodejs #npm #javascript #typescript #opensource #webdevelopment #developer #dotenv

🚀 𝐏𝐑𝐎𝐉𝐄𝐂𝐓 #𝟒: 𝐂𝐥𝐨𝐜𝐤𝐢𝐧𝐠 - 𝐓𝐢𝐦𝐞 𝐒𝐞𝐬𝐬𝐢𝐨𝐧 𝐋𝐨𝐠𝐠𝐢𝐧𝐠 (𝐏𝐄𝐑𝐍) For this project, I built Clocking. The inspiration came from a concept we’re all familiar with: The 10,000-Hour Rule. To truly master skills like coding, writing, or trading, we need to put in the hours. In the past, I used standard stopwatches to track my progress, but it was a mess—I had to take screenshots and manually organize them into folders just to know how much time I’d actually spent. I built Clocking to solve this: a dedicated tool to track deep work sessions and visualize progress without the manual clutter. On the backend, I built a robust API using Node.js and Express to persist session data into a PostgreSQL database, allowing users to keep a permanent, organized record of their journey toward mastery. 𝐓𝐡𝐞 𝐕𝐢𝐬𝐢𝐨𝐧 𝐟𝐨𝐫 𝐅𝐮𝐭𝐮𝐫𝐞 𝐈𝐭𝐞𝐫𝐚𝐭𝐢𝐨𝐧𝐬: I see a lot of potential to take this further—specifically by integrating Computer Vision to verify that a session is actually being worked on. Imagine a dedicated verification system where users can "prove" their deep work through visual check-ins. It would function like Strava, but for skill-building; a platform where people can share their journey with genuine, verified proof of the work they’ve put in. 🛠️ Tech Stack (PERN): PostgreSQL, Express.js, React.js, Node.js, CSS (Modules), and Git for version control. ⚠️ Important Note: This app is currently hosted on Render’s free tier. If it hasn’t been accessed in a while, the server may take 1 to 5 minutes to "wake up" and load the data on your first visit. 🌐 Check out the Live Demo: https://lnkd.in/g5Sae2Cp 📄 GitHub Docs: https://lnkd.in/gykYsXv6 💻 GitHub Profile: https://github.com/Rahelxv #100FullStackProjectsChallenge #WebDevelopment #BuildInPublic #PERNStack #ReactJS #PostgreSQL #FullStackDeveloper #10000HoursRule #Productivity

𝗖𝗹𝗶𝗰𝗸𝗶𝗻𝗴 "𝗖𝗼𝗻𝗻𝗲𝗰𝘁" 𝘁𝗮𝗸𝗲𝘀 𝗼𝗻𝗲 𝘀𝗲𝗰𝗼𝗻𝗱. 𝗕𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘁𝗵𝗲 𝗹𝗼𝗴𝗶𝗰 𝗯𝗲𝗵𝗶𝗻𝗱 𝗶𝘁? 𝗧𝗵𝗮𝘁'𝘀 𝗮 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝘁 𝘀𝘁𝗼𝗿𝘆. - I’m currently building a developer networking platform, and I just wrapped up the core feature: the User Connection system. As users, we expect a seamless experience when we visit someone's profile. But as a backend developer, orchestrating that single "Connect" button was an amazing dive into dynamic state calculation and bidirectional database queries. To make the UI feel intuitive, my API doesn't just return profile data—it acts as a dynamic state machine. When User A visits User B's profile, the backend instantly calculates: 🔹 𝗜𝗱𝗲𝗻𝘁𝗶𝘁𝘆 𝗖𝗵𝗲𝗰𝗸: Are they viewing their own profile? ➔ Render "Edit Profile". 🔹 𝗕𝗶𝗱𝗶𝗿𝗲𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝗗𝗕 𝗖𝗵𝗲𝗰𝗸: Did A send a request to B, or did B send one to A?  🔹 𝗦𝘁𝗮𝘁𝘂𝘀 𝗜𝗻𝗷𝗲𝗰𝘁𝗶𝗼𝗻: Injecting real-time states (`connect`, `pending_sent`, `pending_received`, or `connected`) directly into the payload before it even reaches the frontend React app. It’s incredibly satisfying to take a complex database relationship and distill it down to a single, snappy UI button for the end-user. The hardest features to build are usually the ones that look the simplest on the screen! Have you ever built a feature that looked deceptively simple? Let me know below! #SoftwareEngineering #BackendDevelopment #NodeJS #PostgreSQL #ReactJS #WebDevelopment #BuildInPublic

📨 HTTP Headers Cheat Sheet HTTP headers tell you about the status of the request/response, and controls how data is transferred, formatted, and processed. In this guide, we offer a quick reference for: 📦 Request headers 📤 Response headers 🔒 Security headers 🗄️ Caching headers 🌍 CORS headers 🧩 Custom/debug headers Save & share with your team! Download Our Free Full-Stack Developer Starter Kit ➡️ https://buff.ly/JbI0Qof --- If you found this guide helpful, follow TheDevSpace | Dev Roadmap, w3schools.com, and JavaScript Mastery for more tips, tutorials, and cheat sheets on web development. Let's stay connected! 🚀 #Caching #Performance #CDN #Redis

📨 HTTP Headers Cheat Sheet HTTP headers tell you about the status of the request/response, and controls how data is transferred, formatted, and processed. In this guide, we offer a quick reference for: 📦 Request headers 📤 Response headers 🔒 Security headers 🗄️ Caching headers 🌍 CORS headers 🧩 Custom/debug headers Save & share with your team! Download Our Free Full-Stack Developer Starter Kit ➡️ https://buff.ly/JbI0Qof --- If you found this guide helpful, follow TheDevSpace | Dev Roadmap, w3schools.com, and JavaScript Mastery for more tips, tutorials, and cheat sheets on web development. Let's stay connected! 🚀 #Caching #Performance #CDN #Redis

🚀 Built something small… but useful. Introducing @bhaskardey772/captcha ❓What is it? A lightweight, Canvas-based CAPTCHA generator for Node.js that works without sessions, databases, or external storage. 🤔 Why did I build this? Most CAPTCHA solutions I tried had at least one of these problems: Required session storage or Redis Used SVG tricks or browser dependencies Or were just too heavy for simple use cases I wanted something: → Simple → Stateless → Easy to drop into any backend So I built one from scratch. ⚙️ How does it work? Instead of storing answers anywhere: 1. It generates a CAPTCHA image using Canvas (server-side) 2. Signs the correct answer using HMAC-SHA256 3. Sends back a token 4. Verifies everything statelessly 🔍 What makes it interesting? 🎨 Pure Canvas rendering No SVG. No browser. Just clean PNG generation. 🔐 Stateless verification No Redis. No DB. No sessions. 🤖 Anti-OCR distortion (3 layers) • Character rotation, skew, jitter • Ghost layers (turbulence effect) • Noise (lines, ellipses, dots) ✅ Strict validation Case-sensitive. No shortcuts. ⚡ API is intentionally minimal const { dataUrl, token } = captcha.create(); const { valid, reason } = captcha.verify(token, userAnswer); Works with Express, Fastify, or plain Node.js. (Also added a small React example in the docs.) 📦 npm: https://lnkd.in/gk4EMbRt 💻 GitHub: https://lnkd.in/g_6-WS5h If you try it out, I’d genuinely love your feedback, even if it’s “this could be better” 🙂 #nodejs #typescript #opensource #websecurity #npm #backenddevelopment

Shoutout to Chris Barber for shipping rocksdb-js. A ground-up Node.js binding for RocksDB, open sourced under Apache 2.0. The Node.js ecosystem has had some options for a while, but none that expose the full engine. Wrappers built on old LevelDB abstractions. Abandoned forks. Bindings without real transaction support or TypeScript. If you wanted to use RocksDB seriously from JavaScript, you were writing glue code or compromising on what the engine could actually do. rocksdb-js closes that gap. Full transaction support with optimistic and pessimistic isolation. Lazy range iteration. A native C++ binding on modern Node-API. Prebuilt binaries across macOS, Linux (glibc and musl), and Windows. A built-in transaction log system that powers replication in Harper Pro (The enterprise extension of Harper 5.0) and is ready for event sourcing, change tracking, or whatever the community builds next. Huge thanks to Chris for the craft and care he continues to pour into this library. Open source matters more now than ever. AI is compressing the distance between an idea and a working system, and the ecosystem moves fastest when the foundations are shared. Read the walkthrough: https://lnkd.in/gR4Zq4bR #NodeJS #OpenSource #RocksDB #DeveloperTools