Jyotirmoy Barman

launching entitlements on @dodopayments. when your customer buys a product, dodo now automatically delivers access to whatever they purchased. and when they cancel, we revoke it. you don't do anything. seven entitlement types supported today: license keys. digital files. discord roles. github repo access. telegram invites. framer remixes. notion templates. attach them to any product. we handle delivery, revocation, and the entire lifecycle from there. no zapier. no manual steps. no "i forgot to remove them."

Why do most programmers use dark theme when writing code ? Because light attracts bugs 🐞 Sorry for this bad joke 😆

@ayushagarwal @dodopayments Lets go

will make a big announcement from @dodopayments this week! let's gooo

@Simon_Ingari it just delete the reference to the files, when you store new files it overwrite the old deleted files.

Format a 16 GB USB drive. Open it. All files deleted. Take it to IT guy All 16 GB of files are restored. Where were they stored?

A Rust dev just killed Headless Chrome. It's called Obscura. The open-source headless browser purpose-built for AI agents and scrapers at scale. Chrome vs Obscura: - Memory: 200MB+ → 30MB - Binary: 300MB+ → 70MB - Page load: 500ms → 85ms - Startup: 2s → Instant - Anti-detect: None → Built-in Single binary. No Node, no Chrome, no dependencies. Stealth mode is brutal: → Per-session fingerprint randomization (GPU, canvas, audio, battery) → 3,520 tracker domains blocked by default → navigator.webdriver masked to match real Chrome → Native function masking so detectors can't sniff it out Drop-in replacement for Puppeteer and Playwright over CDP. Zero code changes. If you run agents or serious scraping at scale, this repo prints money. 100% Opensource.

We’ve identified a security incident that involved unauthorized access to certain internal Vercel systems, impacting a limited subset of customers. Please see our security bulletin: vercel.com/kb/bulletin/ve…

Our @golang load balancer at @render handles more than 150 billion HTTP requests a month across millions of services. The number of times we've wanted to rewrite it in Rust: zero. Go is the most underrated language in infrastructure. "Boring" is the ultimate feature.

@hiddnest Border edges

if you notice the differences, you're the top 1% designer

@garysheng @awsdevelopers Yes super excited to use my project

📂 Hey Developers ┗ 📂 Amazon S3 ┣ 📂 can now ┣ 📂 have a ┣ 📂 file system ┗ 📂 get started go.aws/4dB1GfZ

Announcing Amazon S3 Files. The first and only cloud object store with fully-featured, high-performance file system access. Learn more here. go.aws/4tw17Zg

A transaction in Go (using GORM) ensures multiple database operations succeed or fail together. If any step fails, all changes are rolled back, keeping data consistent and preventing partial updates.

189. Rotate Array LeetCode: leetcode.com/problems/rotat…

Claude limit reached before lunch. It's not even half day. Ape sad. Ape confused. Ape understand nothing. Ape consider touching grass. Ape stay inside.

Hot take: Vibe coding only works well if you already know how to code.

Introducing render-json The Generative JSON framework. 1. Point it at anything 2. It generates JSON 3. That's it Apps, games, and more. If it exists, it can be converted into a JSON spec. 𝚗𝚙𝚖 𝚒 @𝚓𝚜𝚘𝚗-𝚛𝚎𝚗𝚍𝚎𝚛/𝚛𝚎𝚗𝚍𝚎𝚛-𝚓𝚜𝚘𝚗

Build production-grade AI agents with @golang. ADK for Go 1.0 is here ⭐ Check out the new capabilities for building robust and debuggable agentic systems: 🔎 Native OpenTelemetry integration 🧩 Plugin system for extensibility 🛡️ HITL confirmation for enhanced security ⚙️ YAML-based agent configuration 🔗 Refined A2A protocol

Fix: cache Go modules and build files using volumes (/go/pkg/mod and /root/.cache/go-build). First run downloads, next runs are fast. So you can stop containers daily and still get quick startup.

Stopping Docker containers doesn’t delete everything. Containers are temporary, but volumes stay. If your Go modules reinstall every time, you’re not using caching properly. ↓ continue

Tooling + workflow: separate Dockerfiles/compose, isolate with -p dev/prod, add Makefile (make dev|prod). Fix real issues (versions, module paths, cache), add DB retry. Run one env at a time. Result: clean, scalable Go + Docker setup.

Go modules: imports must match module in go.mod; run from root. Use env-based DSN (localhost vs db). In Docker, use service DNS (host=db), not localhost. Keep DB private in prod (no port mapping). ↓ continue

Built a production-ready Go backend with Docker. Key: split dev vs prod early. Dev = fast feedback (Air + volumes). Prod = reproducible builds (multi-stage). Avoid “works on my machine”, make onboarding trivial. ↓ continue