Mert

I’ll work for free to fix this issue. Send me location.

You are one of the biggest companies in the world, and it takes more than one week to complete the ID verification process in the world we live in, every week counts for startups. Other companies do this instantly. I’ll never understand this. @stripe @stripesupport @patrickc

@pierreeliottlal 20k

We're on track to hit $4M ARR in under a year. 🚀 Getting from $0 to $20k MRR was by far the hardest part. So we documented everything that got us there: • Every traffic channel we used • Our daily growth playbook • The exact outreach scripts and messages • The systems we repeated every single day No fluff. Just the playbook that got us our first $20k MRR. Want it? Repost ♻️ so more founders can see it. Comment "20k" and I'll DM it to you.

I was just doing couple migrations bruh

I'm reading many comments comparing Prisma and Drizzle. While there are valid points about DX, it's less relevant now since most people don't write low-level SQL queries anymore. What truly matters is the agent experience (AX). I want tools that help agents make fewer mistakes.

@16vchq lexfill.app

drop your startup link get some traffic

@nia_thinks namecheap because its cheap

Founders, which is the best place to buy a domain? - GoDaddy - Porkbun - Hostinger - Cloudflare - Namecheap - Others

@bcherny Product and engineering should be the same role. Now that agents write most of the code, "good at coding" isn't the moat anymore. Knowing what to build is.

As engineering, product, design, DS, etc. melt into a new kind of role, I was reflecting on what roles might look like in the future. For example, when I look at the Claude Code team I see what I think is five archetypes: 1. Prototyper: comes up with brand new ideas; churns out many ideas, most of which don't ship 2. Builder: quickly turns a prototype/idea into production-grade product/infra 3. Sweeper: cleans up the UI, simplifies the code and system, unships, optimizes performance 4. Grower: takes a product that has been built and iterates on it to improve Product-Market Fit 5. Maintainer: owns a mature system to make it secure, reliable, fast, and efficient as it scales Many people span across 2 roles, and sometimes 3 roles. I also notice that these roles are not really tied to job function -- eg. across Anthropic, some designers match category 1, some 2, some 3; same for engineers, PM, DS. A healthy team needs a mix of these, depending on the product: - A product that is new and pre-PMF needs people that are strong at 1+2+3 - A product that is growing and has found PMF needs 2+3+4 and some 5 - A product that has strong PMF needs 3+4+5 and some 2 Maybe product roles of the future will look more like this, and less like the domain-specific roles of today?

Claude should clean up after itself during long sessions. If it gets stuck, debugs the issue, finds a fix, and that debugging trail is no longer useful, it should delete that reasoning from context instead of carrying it forward.

@james84_ hello 🤣

my first attempt to loop engineering. claude doesn't follow my orders