u/bluetech333

I’m curious about something I keep hearing from business owners who make videos/content as part of their marketing.

Creating the main piece of content doesn't seem to be the hardest part.

The annoying part seems to come afterward:

You record a video → then somehow you need to turn it into clips, thumbnails, graphics, posts, etc.

I'm trying to understand what this actually looks like in real life, rather than what people think they do.

So if you create content for your business:

What do you do with a video after you record it?

Do you repurpose it into other formats?

Which part takes the most time?

Do you do it yourself, have an employee/editor do it, or outsource it?

What part of the process do you absolutely hate?

Are there things you know you should be creating from each video but usually don't because it's too much work?

I'm especially interested in hearing from people where content isn't their actual job — you're a realtor, financial advisor, coach, consultant, etc., and content is something you do to bring in business.

Not looking to sell anything. I genuinely want to understand how people are handling this today.

If this is your workflow, I'd love to hear what yours looks like.

I bought an investment for a real reason, then sold it during the panic phase, and then I realized the original reason hadn't changed what I think while buying. The market just scared me. I'm guessing I'm not the only one here who's done that.

So I built this tool to test one question that if you saw exactly what you wrote about why you bought that investment in your own words right when you're thinking about selling it, would that words actually change your mind what is your thesis while your buying?

A 3 minute test:

1. Write a quick note about a real (or made-up) investment why you bought it, what would actually make you reconsider.

2. You're shown a scenario where it's dropped 18%, and asked how likely you are to sell.

3. It shows your own note back to you, and asks if your answer changed.

That's the whole thing. No sign-up, no bank or broker connection, nothing to install.

Being honest: this is an early, rough test, not a complete product. I'm not selling anything. I genuinely don't know yet if this works that's why I'm asking.

Your experiment answers will saved so we can look for patterns across the people . Nothing beyond that.

The most useful thing you can give me isn't just clicking through it. It's telling us what you were actually thinking while you test it. There's a spot at the end to write that down, or just reply here.

Experimentlink: https://lock-intent.vercel.app

Brutal honest feedback genuinely welcome, including "this did nothing for me" that's useful for us.

​

Hey, I'm a developer building something real but very small for investors, and I'd genuinely love honest feedback from this community, either good or bad.

The idea: I bought an investment for a real reason, then sold it during the panic phase, and then I realized the original reason hadn't changed what I think while buying. The market just scared me. I'm guessing I'm not the only one here who's done that.

So I built this tool to test one question that if you saw exactly what you wrote about why you bought that investment in your own words right when you're thinking about selling it, would that words actually change your mind what is your thesis while your buying?

A 3 minute test:

1. Write a quick note about a real (or made-up) investment why you bought it, what would actually make you reconsider.

2. You're shown a scenario where it's dropped 18%, and asked how likely you are to sell.

3. It shows your own note back to you, and asks if your answer changed.

That's the whole thing. No sign-up, no bank or broker connection, nothing to install.

Being honest: this is an early, rough test, not a complete product. I'm not selling anything. I genuinely don't know yet if this works that's why I'm asking.

Your experiment answers will saved so we can look for patterns across the people . Nothing beyond that.

The most useful thing you can give me isn't just clicking through it. It's telling us what you were actually thinking while you test it. There's a spot at the end to write that down, or just reply here.

Experimentlink: https://lock-intent.vercel.app

Brutal honest feedback genuinely welcome, including "this did nothing for me" that's useful for us.

​

I have done this, and I'm curious how common it is.

You buy something because you believe X.

Then it drops 18%.

Suddenly you're looking at the red number every few minutes, reading every negative comment, and thinking:

"Maybe I should just get out."

But sometimes, when you look back later, you realize the thing that originally made you buy hasn't actually changed. The price changed. Your emotions changed. The thesis didn't.

That made me wonder:

Would seeing your own original reasoning at the exact moment you're considering selling actually help?

I built a tiny 3-minute experiment to test that.

You write down:

- why you bought an investment

- what would actually make you reconsider

Then you're given an 18% drop scenario and asked how likely you are to sell.

After that, you're shown your own original note and asked whether your answer changes.

I'm not trying to tell anyone whether they should hold or sell anything. I'm trying to test whether reminding people of their own pre-existing reasoning changes the decision they're making under pressure.

No signup, brokerage connection, or installation.

Experiment: https://lock-intent.vercel.app

It's very early, and I honestly don't know if the idea works.

If you try it, I especially want like to know:

Would seeing your own reasoning actually make you less likely to panic-sell, or would you just find a way to rationalize holding?

And if you've experienced this in real life, I'd be interested in hearing what happened.

I'm interested in a very simple behavioral question:

When someone makes a decision with a particular rationale, does reminding them of that rationale reduce the chance that they reverse the decision when they later experience a strong negative outcome?

I'm testing this using investing because it's an easy scenario to understand.

The basic experiment:

1. A person writes down why they bought an investment and what would cause them to reconsider.

2. They're presented with a hypothetical 18% decline.

3. They rate how likely they are to sell.

4. They're shown their original reasoning in their own words.

5. They rate their likelihood of selling again.

The hypothesis is that seeing their own prior reasoning might act as a kind of pre-commitment/decision anchor and make them less likely to react purely to the negative outcome.

But I'm very aware that this may be testing something much weaker than that.

For example, maybe I'm just measuring:

priming,

consistency effects,

demand characteristics,

confirmation bias,

or simply the effect of making someone pause before answering.

That's actually what I'd like feedback on.

Does this experiment meaningfully test the hypothesis, or am I fooling myself about what the result would mean?

I made a very rough 3-minute version here if anyone wants to experience it:

https://lock-intent.vercel.app

No signup or brokerage connection. It's an early experiment, not a product I'm selling.

I'd especially appreciate criticism of the experimental design. If you think the 18% scenario, question wording, order of steps, or "show them their own reasoning" intervention creates a confound, please tell me.

I'm much more interested in finding the flaws than getting people to tell me it's a good idea.

Teams deploy AI agents for things like refunds, purchase orders, CRM updates, and support resolutions. The agents often report “done” and the API call returns 200, but later someone discovers:

The refund amount was wrong

The customer wasn’t actually eligible

A duplicate order went through

The ERP never updated

Policy was quietly violated

So the technical action succeeded, but the business outcome was wrong.

I’m trying to understand how common this actually is in production.

If you’re running agents (or automated workflows) that take real actions:

Do you (or someone on your team) still manually check a meaningful percentage of them?

Have you had cases where the agent reported success but the actual result was incorrect or incomplete?

How do you currently catch these? Manual reconciliation? Spot checks? Alerts from finance/ops?

What’s the real cost when one slips through (time, money, customer impact)?

Not looking for theoretical answers or “AI needs more guardrails.” Just real operational experience from people who’ve dealt with this.

Curious how painful this actually is right now versus something teams just accept as the cost of automation.

Thanks.

Has anyone here had AI generate code and tests that all passed, only to discover later that the tests weren't actually catching the bug?

I'm trying to understand whether this is a real pain or just something that sounds interesting in theory.

How often does this happen?

How do you catch weak AI-generated tests today?

If a tool could tell you, "these tests look good, but they probably wouldn't catch a real bug," would that actually be useful, or is this not a problem worth solving?

Im not building anything yet I just want to hear honest experiences from people who use AI for coding every day.

​

Has anyone here had AI generate code and tests that all passed, only to discover later that the tests weren't actually catching the bug?

I'm trying to understand whether this is a real pain or just something that sounds interesting in theory.

How often does this happen?

How do you catch weak AI-generated tests today?

If a tool could tell you, "these tests look good, but they probably wouldn't catch a real bug," would that actually be useful, or is this not a problem worth solving?

I'm not building anything yet—I just want to hear honest experiences from people who use AI for coding every day.

I want honest answers before that colors anything.

I've been using Cursor/Claude Code daily for a while now, and there's a pattern I can't tell if I'm imagining. I ask it to fix one small thing — a button style, a validation check, whatever — and when I actually read the full diff, it's touched two or three other things I didn't ask about. Sometimes it's a legit related fix. Sometimes it's just... extra. And I catch myself skimming those diffs faster than I should, because the agent is fast and I don't want to be the bottleneck slowing myself down.

Here's the thing — I don't have a single real story where this actually burned me. That's exactly what's making me unsure if this is a real problem or a vague unease I've talked myself into after staring at it too long.

So, genuinely, I want to know:

Do you read every line of every agent diff, every time, or do you skim once you trust the tool?

Has an agent ever changed something outside what you asked for that actually mattered — not "annoying," but "would've been bad if it shipped"?

If yes — how did you catch it? Code review, tests, CI, pure luck?

If you're on a team — does anyone specifically worry about this for the scary parts of the codebase (auth, billing, payments, permissions)? Or is that worry just not real once you have normal review process anyway?

The thing I've been sketching, if it turns out this is real: not a permission system, not something that blocks or gates anything. Just at the moment the agent finishes, or even while it's still working — show you everything downstream a change could actually touch, using the real call graph, not a guess based on which folder the file is in. Less "you're not allowed to touch this." More "here's everything this could ripple into, before you hit approve." No setup, nothing to declare in advance, just visibility you didn't have to go dig for yourself.

But I've talked myself into and out of three different versions of this in the last few weeks, so I genuinely don't trust my own read anymore. If this isn't real for you, tell me. I'd rather hear it now.

I'm trying to understand something I've noticed while building products myself.

We spend weeks or months building a product, but once it's finished, there's another challenge:

How do you let a new visitor actually experience the value of your product?

I'm curious how other builders handle this.

Do you let people use the real product immediately?

Do you create demo accounts, fake data, or sample projects?

Do you rely on videos, screenshots, or product tours instead?

If your product requires login, how do you help people understand its value before asking them to sign up?

What's the most frustrating part of this whole process?

I'm especially interested in answers from people who've actually shipped products.

I'm not looking for theoretical advice. I'd love to hear what you actually do today, what works, what doesn't, and what you wish was easier.

I've spent months building an AI developer tool, but before I spend months more, I want honest feedback from people who actually use AI for coding.

I don't want validation. I don't want encouragement.

I want to know if I'm chasing a problem that isn't painful enough.

My assumption is this:

As AI coding agents become more capable, developers spend less time writing code and more time trying to understand, review, and trust what the AI actually changed.

I believe problems like these become more common:

AI edits files you didn't expect.

Large AI-generated PRs are mentally exhausting to review.

You don't fully understand why the AI made certain changes.

I believe problems like these become more common:

AI edits files you didn't expect.

Large AI-generated PRs are mentally exhausting to review.

You don't fully understand why the AI made certain changes.

You end up reading hundreds of lines just to feel safe merging.

That's what I've been building around.

Here's what I want to know:

Am I solving a problem that isn't actually painful?

When using Cursor, Claude Code, Codex, Windsurf, Gemini CLI, etc., what is the single biggest frustration you repeatedly experience?

Have you ever thought, "I wish there were a tool that solved this," or do you just review the code and move on?

If my assumption is wrong, where exactly is it wrong?

Please don't worry about hurting my feelings.

If you think this is a niche problem, tell me.

If you think developers will never install another tool for this, tell me.

If you think there's a much bigger problem in AI-assisted software development that everyone is ignoring,

I'd rather hear that now than after another six months of building.

I'm genuinely looking for reasons not to continue if I'm solving the wrong problem.

​

I'm an independent developer from India.

For the last several months, I've been building an open-source developer tool called Ripple.

Ripple helps developers keep AI coding agents focused on their intended task by checking whether AI-generated code changes stay within the scope they were supposed to modify. My goal is to make AI-assisted software development safer and easier to trust.

I've built the project almost entirely on my own. It has taken months of work, and I've reached the point where I can't realistically continue at the same pace because I simply can't afford the AI tools and API usage that modern development now depends on.

I'm not asking anyone to believe in an idea—I already have a working project. I'm asking for help to keep improving it.

If anyone can help with any of these, I would be deeply grateful:

Unused AI API credits (OpenRouter or similar)

Sponsoring a Claude, Codex, or other AI coding subscription

Information about grants or startup programs for open-source developers

Technical feedback or code contributions

Introductions to people or teams who might find Ripple useful

If you can't help financially, even trying the project, sharing feedback, or pointing me toward useful resources would mean a lot.

I've put everything I have into building Ripple because I genuinely believe it can help developers work more safely with AI.

Thank you for taking the time to read this. Any advice or support is sincerely appreciated.

I've been thinking about how AI coding agents are changing software development.

AI can now generate and refactor code much faster than humans can fully absorb it. That got me wondering about a deeper question.

When a project evolves over months or years, code is preserved through Git, but the reasoning behind important changes often disappears.

I'm not talking about comments or documentation.

I'm talking about things like:

Why was this architectural decision made

What assumption changed?

What trade-off was accepted

What business constraint drove this implementation?

Why was one approach rejected over another?

So I have a question for experienced engineers:

After looking back at projects you've worked on for years, what is the single most valuable piece of knowledge you wish had been captured at the moment a significant change was merged?

I'm not looking for tool recommendations.

I'm trying to understand what kind of knowledge actually gets lost over time and becomes painful later.

I'd really appreciate hearing from people who've maintained large or long-lived systems.

After reading the discussions on my previous post, I think many developers agree on one thing:

AI is making it much faster to build software, but keeping an accurate mental model of a rapidly evolving codebase is becoming harder.

Some people suggested:

Better documentation

Smaller AI-generated commits

More code reviews

Asking AI to explain its changes

These all help, but I'm wondering if they solve the root problem.

Imagine coming back to a project after two weeks. AI agents have made dozens of changes.

What would you actually want?

Would it be:

A better README?

Better architecture docs?

A timeline of architectural decisions?

A "project memory" that remembers why important decisions were made?

Something else entirely?

I'm not asking how you work around the problem today.

I'm asking:

If you could design the ideal solution from scratch, what would it look like?

I've noticed something while using AI coding agents, and I'm curious if other developers feel in the same way.

AI can now build complex features incredibly fast. In a single session it can modify dozens of files, introduce new abstractions, refactor existing code, and everything still works.

The problem is that I often don't have a clear mental model of what actually changed.

I own the code, but I couldn't confidently explain:

How the architecture evolved.

Why certain design decisions were made.

Which modules now depend on each other.

What assumptions were introduced.

I've seen many projects add files like README md, ARCHITECTURE md ,AGENTS md , or ,CLAUDE md but those can quickly become outdated as AI keeps changing the code.

I'm wondering if we're entering a new kind of engineering problem:

AI can generate software faster than humans can build an accurate understanding of it.

Do you experience this too, or is it just me?

If you've run into this, how do you keep an up-to-date mental model of an AI-generated codebase?

​

My workflow usually looks like this:

I spend a few hours working with one AI.

Then I switch to another because it's better at a different task.A

nd suddenly... I have to explain everything again.

end up rewriting the same context over and over:

What the project is

How it's architected

What I've already built

Why I made certain decisions

What I've already tried

What's currently broken

What I want the AI to do next

What it absolutely shouldn't touch

After doing this enough times, I started wondering:

Is this actually a common pain for developers, or is it just the way I work?

I'd love to hear from people who regularly use AI for coding.

Do you switch between multiple AI coding assistants?

How do you hand off project context when you switch?

Do you keep a living document, rewrite prompts every time, or have another system

What's the most frustrating part of changing from one AI to another?

One idea I've been thinking about is a tool that continuously understands your project and automatically generates a concise "AI handoff" so any coding assistant can immediately understand the current state of the project.

Would something like that genuinely save you time, or is this solving a problem that isn't really there?

I'm not building or selling anything right now. I'm just trying to validate whether this is a real pain point before I spend months working on it.

I'd really appreciate honest feedback—even if your answer is, "No, this isn't a problem for me."

One thing I've noticed is that AI has made it much easier for a solo developer to build software. But building a successful product still feels like a one-person battle.

As a solo founder, you're often responsible for:

Product planning

Development

UI/UX

Testing and QA

Documentation

Marketing

Community building

Customer support

Launching

Iterating based on feedback

Each of these requires different skills, and switching between them constantly can slow progress and become mentally exhausting.

I'm wondering whether there's a better way.

Imagine a platform where a founder could post an idea or project and break it into specific needs, such as:

Looking for beta testers

Need a security review

Need UI/UX feedback

Need documentation help

Need marketing support for launch

Need developers for a particular feature

Need users to validate assumptions

Instead of searching across dozens of Discord servers, Reddit communities, LinkedIn, X, and Slack groups, everything would happen in one place where contributors could join based on their expertise and interest.

The goal wouldn't be to replace co-founders or traditional hiring. It would be to help solo builders turn ideas into real products faster by making collaboration more structured and accessible.

I'm curious:

Have you ever wished a platform like this existed?

If something similar already exists, what is it?

What do existing communities do well, and where do they fall short?

As a solo founder, what has been your biggest bottleneck outside of writing code?

Would you actually use a platform like this, or is there a reason you think it wouldn't work?

I'm not trying to promote anything—I genuinely want to understand whether this solves a real problem or whether I'm overlooking something obvious.

I'd really appreciate your honest and brutal thoughts, whether positive or critical.

​

I'm an independent developer from India building Ripple, an open-source tool that helps engineering teams keep AI coding agents within their intended scope. It analyzes code changes and helps prevent unintended edits before they reach production.

Over the past several months I've built:

A TypeScript CLI

GitHub integration

Cloud backend

Published npm packages

Cryptographic audit trail for AI-generated changes

The project has reached a stage where further development is becoming difficult because I can't currently afford AI development tools like Claude, Codex, or similar paid plans that would significantly speed up development and testing.

I'm not asking for donations with nothing in return.

If you believe this project could become useful to the developer community, I'd really appreciate any of the following:

Advice on grants, startup programs, or open-source funding.

Free credits or programs for open-source maintainers.

Sponsorship of an AI coding subscription. Introductions to companies or engineers interested in trying Ripple.

Honest technical feedback or contributions.

Everything I've built so far has been developed as an open-source project, and my goal is to keep improving it for the developer community.

If you'd like to see the project or have suggestions, I'd be grateful for any guidance.

Thank you for reading.

​

One thing I've noticed is that AI has made it much easier for a solo developer to build software. But building a successful product still feels like a one-person battle.

As a solo founder, you're often responsible for:

Product planning

Development

UI/UX

Testing and QA

Documentation

Marketing

Community building

Customer support

Launching

Iterating based on feedback

Each of these requires different skills, and switching between them constantly can slow progress and become mentally exhausting.

I'm wondering whether there's a better way.

Imagine a platform where a founder could post an idea or project and break it into specific needs, such as:

Looking for beta testers

Need a security review

Need UI/UX feedback

Need documentation help

Need marketing support for launch

Need developers for a particular feature

Need users to validate assumptions

Instead of searching across dozens of Discord servers, Reddit communities, LinkedIn, X, and Slack groups, everything would happen in one place where contributors could join based on their expertise and interest.

The goal wouldn't be to replace co-founders or traditional hiring. It would be to help solo builders turn ideas into real products faster by making collaboration more structured and accessible.

I'm curious:

Have you ever wished a platform like this existed?

If something similar already exists, what is it?

What do existing communities do well, and where do they fall short?

As a solo founder, what has been your biggest bottleneck outside of writing code?

Would you actually use a platform like this, or is there a reason you think it wouldn't work?

I'm not trying to promote anything—I genuinely want to understand whether this solves a real problem or whether I'm overlooking something obvious.

I'd really appreciate your honest and brutal thoughts, whether positive or critical.

One thing I've noticed is that AI has made it much easier for a solo developer to build software. But building a successful product still feels like a one-person battle.

As a solo founder, you're often responsible for:

Product planning

Development

UI/UX

Testing and QA

Documentation

Marketing

Community building

Customer support

Launching

Iterating based on feedback

Each of these requires different skills, and switching between them constantly can slow progress and become mentally exhausting.

I'm wondering whether there's a better way.

Imagine a platform where a founder could post an idea or project and break it into specific needs, such as:

Looking for beta testers

Need a security review

Need UI/UX feedback

Need documentation help

Need marketing support for launch

Need developers for a particular feature

Need users to validate assumptions

Instead of searching across dozens of Discord servers, Reddit communities, LinkedIn, X, and Slack groups, everything would happen in one place where contributors could join based on their expertise and interest.

The goal wouldn't be to replace co-founders or traditional hiring. It would be to help solo builders turn ideas into real products faster by making collaboration more structured and accessible.

I'm curious:

- Have you ever wished a platform like this existed?

- If something similar already exists, what is it?

- What do existing communities do well, and where do they fall short?

- As a solo founder, what has been your biggest bottleneck outside of writing code?

- Would you actually use a platform like this, or is there a reason you think it wouldn't work?

I'm not trying to promote anything—I genuinely want to understand whether this solves a real problem or whether I'm overlooking something obvious.

I'd really appreciate your honest and brutal thoughts, whether positive or critical.