Amanda Silmon

Amanda Silmon

Growth Marketer
#9506445123 followers14 following
#6,923Last month
1 KP
>10,000All time
534 KP

About

I work as a Growth Marketer, focusing on driving customer acquisition and business growth through data-driven strategies. I design and execute campaigns across digital channels to increase engagement and conversions. I analyze performance metrics to identify opportunities and optimize results. I collaborate with product, sales, and marketing teams to improve the customer journey. My goal is sustainable growth through experimentation, creativity, and continuous improvement.

Badges

Top 5 Launch
Top 5 Launch
Tastemaker
Tastemaker
Gone streaking
Gone streaking
Gone streaking 5
Gone streaking 5

Maker History

  • Agent 37
    Agent 37Your own OpenClaw instance for $3.99/mo
    Mar 2026
    • 🎉
    Joined Product HuntMarch 2nd, 2026

Forums

Aperturep/aperture-7•

24d ago

Aperture's checks now work outside the editor: any agent, and every PR

Since launch, your bots and agents can check a change before they apply it.

Aperture is now an MCP server. Grok Bot, Claude Code, Cursor or any MCP client can call check_change before it applies a change. It checks that the files parse, the imports resolve, and the TypeScript compiler finds no new errors, including in files the agent never opened. It also flags a change that skips or cuts short the tests. Nothing the agent sends is run or kept. Setup takes three steps at https://aperturesais.grok.me/agents

Aperture Agent Check runs the same checks on every pull request, as a CLI or a GitHub Action. Red lines get annotations right on the diff. If a failure was already there in the base branch, it shows as amber, not blamed on the PR. Your code never leaves the runner. Aperture's own PRs go through it.

Honest numbers: in the benchmark, the editor catches 27 of 33 bad edits, with 1 false alarm in 15 good ones. check_change stops 20 of the 33 without running anything. The other 7 only show up when tests run, so keep running them. Every miss is listed at https://aperturesais.grok.me/ben...

LapuAIp/lapuai•

2mo ago

Desktop AI for ops is still subsidized. What happens when users pay the bill?

I'd like to share an opinion on the current situation in AI ops, not the coding/tech side.

Right now the market has a pretty clear pattern. Big labs like OpenAI, Anthropic and xAI are building their own desktop AI and computer-use apps. The trick is they still treat this segment as Growth. Maturity is far away. So the biggest players burn money acquiring customers and giving them huge subsidies on tokens vs real cost.

Today the world is getting a huge AI bill, mostly paid by investors. We're running on debt. If there is no real breakthrough, math doesn't lie, there will have to be a cost-effective compromise. Using heavy models for coding is justified. Using them for the simplest things in operations is not, economically.

•

2mo ago

Vibe coding is fun until the AI becomes dumb all of a sudden.

I used a few different tools to vibe code my saas. I used lovable, chatgpt, gemini to code my saas. The thing is, there is a huge problem of these AI's of forgetting when you chat for a longer time.

This has happened to me a lot of times. One solution I found is that you can start a new chat to overcome this problem. But, here the problem arises to explain the AI all the context which you had in the previous conversation.

Curious, has anyone else ever ran into this problem? How did you manage to overcome this?

View more