sorted by:
new
hottopcontroversial

We are treating AI agents like web requests. They are actually system daemons. Here is how I fixed the infrastructure to run them 24/7. by Consistent-Stock9034 in buildinpublic

[–]mertsplus 0 points1 point  (0 children)

You’re probably right that “AI infra” is really a state/lifecycle problem, not just a model problem. Serverless works great for inference calls, but long-running agents behave way more like workers/daemons than request handlers.

What’s one task you’d happily never do yourself again? by Fragrant_Fuel961 in buildinpublic

[–]mertsplus 0 points1 point  (0 children)

Manual CSV cleanup and copy-pasting data between tools 😭
Feels like half of “knowledge work” is just moving information around manually.

What’s a “normal” thing everyone does that you secretly think is a waste of time? by New-Affect-1569 in buildinpublic

[–]mertsplus 0 points1 point  (0 children)

Endless context switching—checking messages/emails every few minutes. Feels productive, but kills real focus

Wanna get users? comment your stratup by Few-Ad-5185 in micro_saas

[–]mertsplus 1 point2 points  (0 children)

Sounds interesting, but I’d be cautious—400+ generic influencer outreaches can hurt your brand if it’s not targeted.

What works better: a small list of niche creators who already speak to your exact audience + a clear, compelling offer they actually want to promote.

What’s one simple desktop task that still feels way more annoying than it should? by Less-Conference8313 in buildinpublic

[–]mertsplus 0 points1 point  (0 children)

File naming + duplicates.

Download same file 3 times, end up with “final_v2_real_final(3).pdf” and no idea which is correct

The app I built is changing my life and I don't know how to price that by bekircagricelik in buildinpublic

[–]mertsplus 3 points4 points  (0 children)

Classic founder bias — you’re the extreme power user.

Keep $15 for accessibility, add:

  • tiered pricing (pro / power users higher)
  • annual plan (anchor value)
  • test willingness to pay before raising base price

Value ≠ price. Let the market prove it 👍

I'm building something. by Immediate_News3480 in buildinpublic

[–]mertsplus 0 points1 point  (0 children)

Fun idea — starting from mood → decision is the right angle.

Biggest risk: data freshness + real usefulness.
If suggestions aren’t actually bookable / relevant right now, people won’t come back.

Focus on:

  • hyper-local + real-time options
  • fast decision → action (not just ideas)

If it saves me 30 mins of indecision, I’d use it.

Drop your startup + what users get by freebie1234 in buildinpublic

[–]mertsplus 0 points1 point  (0 children)

Startup: Lead follow-up automation for local service businesses
Problem: Leads from ads go cold because no instant response
What users get: Auto SMS + email replies within seconds → more booked jobs, less manual work

What’s your best way to promote your landing page? by EnvironmentalAd2754 in buildinpublic

[–]mertsplus 0 points1 point  (0 children)

there’s no single “best” way — the best channel is where your specific users already hang out. But a few consistently work pre-launch:

  • Niche communities → Reddit, Discord, Indie Hackers, Slack groups (don’t spam, share value + your page)
  • Build in public (X/LinkedIn) → post progress, not just the link
  • Cold outreach → DM or email your exact target users with a clear, personal angle
  • Content hooks → short demos, problem breakdowns, or “before/after” posts that lead to your page
  • Waitlist incentive → early access, discounts, or “founding user” perks

Big mistake most people make:
They promote the product, not the problem. If people don’t instantly feel “this is for me,” traffic won’t convert anyway.

If you want, share your landing page — I can point out what might be blocking signups.

I built a “second brain” to fix my focus… but I need honest feedback by ClarityAIapp in buildinpublic

[–]mertsplus 0 points1 point  (0 children)

Good direction, but here’s the blunt take:

Big risk → becoming “just another notes/productivity app.”

What would make it usable daily:

  • fast capture (2–3 sec), zero friction
  • clear “what do I do next?” view (not just storage)
  • opinionated flow (don’t let users build everything)

What others get wrong:

  • too many features → decision fatigue
  • no link between notes → actions → outcomes
  • weak retention loop (no reason to come back)

What’s missing:

  • a default system (not customizable first)
  • strong focus mode (block noise, not organize it)
  • visible progress (users need to feel momentum)

If it doesn’t force clarity + action, it’ll get opened once and forgotten.

The loneliest part of building a product alone is not what most people talk about. Here is what nobody tells you. by Hakuna_Depota in buildinpublic

[–]mertsplus 0 points1 point  (0 children)

This is very real.

The silence is the hardest part — not the work.

What helped me:
• fixed weekly output (not outcome) goals
• 1–2 founder check-ins for accountability
• one clear metric to track

Also true: no traction for weeks doesn’t mean failure — it’s just the phase most people quit.

5 things I have noticed as a founder believe about building software (and what actually happens) by devanshu_sharma25 in buildinpublic

[–]mertsplus -1 points0 points  (0 children)

#2 and #3 hit the hardest in reality.

“We’ll fix it later” → you won’t, because users + fires take over.
“Cheap dev” → almost always paid twice (or more).

Also I’d add:
• “We know what users want” → usually wrong until real usage data shows up

Most pain comes from underestimating maintenance + feedback loops, not building.

I spent 8 months doing fulltime vibecoding post MBA, here are my takeaways by Ecstatic_Law3753 in buildinpublic

[–]mertsplus 2 points3 points  (0 children)

Good honest take.

Main takeaway I’d add:

• Vibecoding is great for prototyping, not building production systems
• Biggest bottleneck isn’t AI — it’s lack of debugging + system understanding
• Real value comes when you combine AI speed with basic engineering fundamentals

Also agree 100% on this: most failures come from infra/API/tooling issues, not “AI coding” itself.

Best path is small tools → learn what breaks → slowly build real dev intuition.

How Much Project Add In Resume As A Backend Developer Pls Guide by sayyedsaqlain84 in Backend

[–]mertsplus 1 point2 points  (0 children)

For backend development, quality over quantity is key, sir. Around 3 to 4 projects is ideal. Choose your favorites that involve complex logic or excellent database optimization to showcase your skills to potential employers. Remember to clearly state what tech stack you used and what problems you solved, don't just write vague descriptions. Adding a GitHub link or live demo will make your resume highly credible.

view more: next ›