Been thinking a lot about how fast original content disappears. It seems news footage, eyewitness video, documentary clips and other original video gets buried under noise within a week. Something goes viral on Monday and by Friday the original is gone, replaced by reposts, edited versions, and debates on what actually happened until it's just... not findable anymore.

Curious if anyone has tackled this problem, what approach you took, and what you think about the tension between platform distribution (reach) and platform dependency (your content disappearing under noise). Specifically interested in eyewitness footage, journalism, and documentary work but any category where permanence matters.

What approach works? What doesn't?

A few years ago, shipping constantly was almost a marketing strategy. Pieter Levels, Jennifer Dewalt, Marc Lou building fast gave people a reason to follow the journey. Every launch created another story and more momentum.

But AI changed the equation. Now anyone can ship an app every week, and a lot of them are buggy, generic, and make $0. Shipping itself is no longer impressive.

Everyone s been talking about AI Agents over the past year.

But the real leverage doesn t come from the agent itself. It comes from the context you provide:

One thing I ve found hard while building a SaaS is knowing when slow progress is normal and when it s actually a sign that something needs to change.

Some weeks you ship things, fix bugs, improve the product but the numbers barely move.

It s easy to look at that and think, "maybe this isn t working."

But sometimes you just need more time. Other times, you probably need to change something.

Curious how other devs handle this: missing env vars, wrong Node version, lockfile mismatch the same CI errors that keep coming back across repos.

I've been thinking about whether pattern matching (not AI) could just auto-fix these. Same error same fix open a PR automatically.

Questions:

• How much time do you actually lose to CI debugging per week?

• Would you trust an automated fix PR from a bot?

• What's the most annoying CI error you keep seeing?

If you've tried registering a domain anytime recently, you know how rare this is. Usually every decent idea is either parked for thousands or forces you into compromises. Finding a clean, 6-letter .com sitting right there felt like winning a tiny lottery.
It got me thinking about how much energy goes into naming in the early stages.
Question for the founders and creators here: How do you usually go about finding domains or experimenting with names?
Do you use AI tools, churn through registry searches, look for expired domains, or just stick to standard TLDs like .com or .ai no matter what?

I used to save everything.

I'd see an interesting article and immediately save it because obviously I was going to read it later.

Except "later" apparently never came.

I've mostly gone back to bookmarks and open tabs now, which isn't exactly a great system either.

I've gone back and forth between these two more times than I should probably admit.

Coda always pulls me in because I can make tables, buttons, little automations, etc. It's fun until I've somehow turned a simple notes system into a project of its own.

Then I go back to Notion because I just want to write things down and find them later.

And then, inevitably, I miss something Coda did better.