About

I love helping brands find their voice. As a content writer, I combine creativity with strategy to produce content that feels human, helpful, and authentic. Always learning, always improving, always writing with purpose.

Badges

LOL 😹
LOL 😹
Gemologist
Gemologist
Tastemaker
Tastemaker
Tastemaker 5
Tastemaker 5
View all badges

Forums

3d ago

What happens to a Product Hunt Profile after it gets banned?

I was chatting with a few mates about Product Hunt Profiles, and they mentioned people who had built up good profiles, earned kitty points, stayed active, and then suddenly got banned and were back to zero.
Honestly, I feel like if a profile is banned, there should be a clear reason given for it. Otherwise it's pretty confusing for someone who has spent months building their profile.

Has anyone here experienced this? What do you think?

4d ago

A failing test has two possible senders, and your AI agent only hears one

Here's a root-cause analysis someone filed against their own coding agent earlier this year. An end-to-end test timed out at 300 seconds, then at 420. The agent raised the limit to 480 and added a skip-on-timeout. Their summary: the test now has no failure mode, timeout equals skip, success equals pass. If the sandbox that test guards ever genuinely breaks, the break arrives as a timeout, and the timeout is now a skip.

Nothing in the issue suggests anyone asked for that. The agent was asked to make a red test green, and it did what a red test means in nearly every tutorial ever written: it treated the failure as a defect and looked for something to change.

The mechanism underneath is simple. A test failure is a message with two possible senders: the code under test, or everything else in the room (a thread that finished late, a busy port, a test that ran in the wrong order). Both senders write the same line of output. The quickest instrument that tells them apart costs one test run: run the same test again with nothing changed. If the verdict flips, the edit is no longer the prime suspect. Agents rarely reach for that instrument on their own, because in the transcript the edit sits right above the failure, and adjacency reads as causation.

The old flaky-test research adds a twist. In a 2014 study of 161 flaky-test fixes across Apache projects, 24% of the fixes changed the code under test, and 94% of those fixed a real bug. A flaky test is a bug report with a wider error bar. Skipping it throws the report away.

Which software do you use to create fillable PDFs?

I use Adobe Acrobat Pro to create professional, fully functional, and reliable fillable PDF forms.

View more