Priyam Sekra

With AI writing the majority of first drafts now, I've noticed something shifting in how engineering teams work, the bottleneck isn't writing code anymore, it's reviewing it.

A few things I've been thinking about:

• Most devs I know got good at coding by writing a lot of it. But we never really trained to read it the same way.

• Code review culture is getting worse, not better, as AI output volume increases. People are rubber-stamping PRs they don't fully understand.

• The bugs that make it to production aren't from bad writers, they're from missed reads.

Curious if others are feeling this. Do you actively practice reading code, or is it just something you pick up passively? Has AI changed how carefully you review code before merging?

A lot of digital security products focus on detecting threats after something suspicious has already happened.

But many problems begin earlier: approving the wrong permission, downloading from an unofficial source, trusting a familiar-looking page, or accepting a prompt without enough context.

This makes me wonder whether the real issue is a lack of security tools, or a lack of clear information at the moment a user is making a decision.

My view is that most people do not want more alerts or technical dashboards. They want to understand:

Hey Product Hunt Tony and Steven here from ClawTeams.

Three days ago we launched ClawTeams, the first goal-driven, proactive AI team for e-commerce. We hoped for a warm welcome. What caught us off guard was how much the comments themselves would end up teaching us. We landed at #1 Day Rank, crossed 800+ points, and picked up over a thousand followers but honestly, the questions in the thread have shaped our roadmap more than any planning doc we wrote before launch. So I wanted to write down what we heard, what it changed, and where we're headed.