Loading video...

Video Failed to Load

Go Home

Explaining a product change often takes longer than making it. This AI can now build the change for your engineers to review. Small product fixes often have to wait because only engineers can make changes to the code: → A typo in the copy → An empty screen with...

40,165 views • 9 days ago •via X (Twitter)

27 Comments

Kevin Box's profile picture
Kevin Box9 days ago

Giving non-engineers a way to prepare changes for review could help teams move faster without removing engineering oversight.

Andrew Bolis's profile picture
Andrew Bolis9 days ago

That balance is what makes this approach worth trying.

Businessaholic's profile picture
Businessaholic9 days ago

The preview step makes this especially practical.

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Good point, a live preview takes the guessing out.

EntrepBuilder's profile picture
EntrepBuilder9 days ago

Helpful workflow for teams dealing with constant small changes.

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Agreed, this takes a lot of pressure off busy teams.

The Ant Philosophy's profile picture
The Ant Philosophy9 days ago

The browser-based workflow makes this feel very accessible.

Andrew Bolis's profile picture
Andrew Bolis9 days ago

No local setup means anyone can jump in quickly.

AntonioAI's profile picture
AntonioAI9 days ago

Turning small product fixes into reviewable code could remove a huge amount of friction from the product development loop

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Less friction on tiny fixes keeps the whole loop moving.

EyeingAI's profile picture
EyeingAI9 days ago

Tiny fixes should be this simple.

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Honestly, the best part is nothing skips the review.

Business Corner | Showcasing Entrepreneur's profile picture
Business Corner | Showcasing Entrepreneur9 days ago

Nice approach to keeping engineers involved without bottlenecks.

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Good point, the pull request keeps everyone in the loop.

PreneursCircle's profile picture
PreneursCircle9 days ago

This could make small product fixes much faster.

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Yeah, small changes should not need a whole meeting.

Minds That Build's profile picture
Minds That Build9 days ago

Engineers keeping final control is an important detail.

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Speed means little if engineers lose the last word.

Nyx's profile picture
Nyx9 days ago

Great share

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Thanks!

Jyoti's profile picture
Jyoti9 days ago

Love the idea of letting anyone turn product feedback into real code changes while keeping engineers in control. This could make small but important fixes much faster.

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Good point, important little fixes shouldn't sit around for weeks.

Nelly;'s profile picture
Nelly;9 days ago

I’ve written embarrassingly detailed tickets for changes that were basically three words

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Ticket longer than the fix itself is so relatable.

Amit's profile picture
Amit9 days ago

this could save teams a ton of back and forth

Andrew Bolis's profile picture
Andrew Bolis9 days ago

Agreed, describing the change directly cuts out the middleman.

Andrea Z's profile picture
Andrea Z9 days ago

the bottleneck just moves to review. anyone can open 10 small PRs a day now, and each still needs someone to check it didn't break something two files away. i build an AI PR reviewer and that second step is the part that matters.

Related Videos