Tim David's profile on Product Hunt

About

I help businesses build digital brands that people actually trust. Most companies treat their website as a brochure. We build it as their best salesperson — one that works 24/7, converts visitors into customers and reflects a brand worth believing in. At Housman Digital, I lead creative and technical direction across B2B projects — bringing together brand strategy, creative design, social media, UX and full-stack development (Next.js, JavaScript, PHP) so nothing gets lost in translation between vision and delivery. I've worked with SMEs and multimillion pound enterprises across the UK.

Badges

Tastemaker

Gone streaking

Forums

•

1d ago

Are AI coding agents good at working with existing codebases?

Generating a new project feels relatively straightforward, but modifying an older codebase with existing conventions is a different challenge. I m curious how well coding agents handle unfamiliar folder structures, shared components, and legacy code. What has your experience been with this?

•

1d ago

Bought a 25-day-old domain, but it shows 1.1k historical backlinks - normal?

Hey everyone,

I recently purchased the domain curetotal.com through GoDaddy - it's only about 25 days old under my ownership. But when I checked backlink data:

- Ahrefs shows ~1.1k backlinks

- Ubersuggest shows ~27 backlinks

•

3d ago

Fifteen blue buttons and the layer that never sees a selector

We asked a coding agent fifteen times to make one button blue on a page built to tempt it: Add to Cart and Checkout shared a class, a badge and the nav link shared the accent variable. Every run added an id-scoped rule. Checkout stayed green. Appending "Do not change anything else" changed one thing: the five runs with it wrote the hex inline where nine of the other ten had added two CSS variables. A path rule fencing off every file but the stylesheet never fired.

Real repositories look different. One benchmark pre-applied the fix to 200 issues and reopened them for five recent models in their vendors' harnesses. The right patch is empty; 35 to 65% of instances got an edit to executable code anyway, and in the authors' analysis of one model's failed traces, 87.1% had modified code unrelated to the issue. Task wording moved that figure a long way in both directions. Telling the agent to "edit the codebase" dragged one model's correct-abstention rate to 36.5%; reproduce first, then fix or abstain if nothing was wrong, lifted it to 88.5%. Their explanation: the agent acts on whatever it believes success means.

The harness side: switch on auto-accepted edits in both CLIs whose docs we read and the grant is the whole working directory. A path rule brings that down to files; one vendor's docs state that it applies to the built-in edit tools and recognized shell commands, and that a script opening a file itself is outside it. A selector inside a permitted file sits below every layer's resolution. Whether the blue landed on one button or on every primary button is decided by the sentence you typed and by whoever reads the diff.

When your agent overshoots, where does the boundary live in your setup today: the prompt, a rule file, a path rule, a sandbox, or the person reading the diff? Which of those has caught a change for you inside a file the agent was allowed to edit?