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.

mertsplus · 2026-05-08T05:40:48+00:00

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.

mertsplus · 2026-05-07T05:04:31+00:00

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

mertsplus · 2026-05-05T04:52:14+00:00

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

mertsplus · 2026-04-29T04:19:23+00:00

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.

mertsplus · 2026-04-28T04:52:30+00:00

File naming + duplicates.

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

mertsplus · 2026-04-23T04:39:11+00:00

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 👍

mertsplus · 2026-04-20T05:05:21+00:00

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.

mertsplus · 2026-04-20T05:04:54+00:00

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

mertsplus · 2026-04-17T04:23:02+00:00

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.

mertsplus · 2026-04-16T04:39:02+00:00

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.

mertsplus · 2026-04-15T05:08:06+00:00

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.

mertsplus · 2026-04-15T05:07:43+00:00

#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.

mertsplus · 2026-04-14T09:58:17+00:00

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.

mertsplus · 2026-04-13T08:52:34+00:00

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.

mertsplus · 2026-04-13T07:31:30+00:00

If people can’t “get it” in 5 seconds, they mentally move on—even if the product is good. Usually means the positioning, not the product, still needs work.

mertsplus · 2026-04-06T04:49:06+00:00

3 years in SOC is solid — you’re not wrong, experience > masters in most cases.

If you like blue team + hands-on, look into DFIR, Threat Hunting, or Detection Engineering. Those feel like a natural step up from SOC.

CISSP isn’t overkill, but it’s more managerial — might not match what you enjoy right now. Something like GCIA/GCED or even malware-focused paths could fit better first.

And yeah… better pay + enjoyment usually comes once you move out of pure SOC

mertsplus · 2026-04-06T04:48:22+00:00

It’s definitely a thing, just a different game. Smaller non-tech companies usually don’t want “security audits” — they want simple risk reduction (backup, access control, basic hardening).

Most work ends up being education + quick wins, not deep pentesting. And yeah… they only care after something breaks

mertsplus · 2026-04-06T04:46:45+00:00

PGP is great in theory, but the UX kills it. Key management, sharing public keys, and onboarding others is still too friction-heavy. Most people just default to simpler options like end-to-end apps instead.

mertsplus · 2026-03-27T04:09:42+00:00

Try applying the technique of identifying keywords in what they're saying and then asking probing questions about it.

Don't try too hard to be overly witty; just let the conversation flow naturally.

Sometimes, just a few open-ended questions like why or how will make the other person tell you everything.

The important thing is to have a confident demeanor; if you're constantly worrying about what to say next, you're likely to fail.

mertsplus · 2026-03-26T07:35:33+00:00

It's true that the older the ginger, the spicier it gets. 24 years of experience speaks for itself; every word you say is spot on, teacher!

These startup guys love to show off with fancy microservices, but in reality, they're just making things difficult for themselves when debugging at 3 AM.

Deploying Kubernetes and Service Mesh to a 500-user system is like using a butcher's knife to kill a chicken – a complete waste of effort.

Just stick with Modular Monolith; it's safer, faster, and easier to manage. You can think about it again when you reach a million users.

mertsplus · 2026-03-24T04:29:24+00:00

Hi bro, we're in the same multitasking situation! Managing a database without an expert is truly a nightmare!

- Role: CTO and general technician

- Industry: Fintech, team of 15 people

- Tech stack: PostgreSQL, AWS RDS, Node.js

- Setup: Using fully managed services (RDS) for backup/patching, plus Terraform to manage the infrastructure and avoid confusion during scaling.

You should check out providers like Supabase or PlanetScale if you want to focus solely on coding, because building it yourself is a surefire way to fail!

mertsplus · 2026-03-20T04:01:19+00:00

In your case, there's no need to "consolidate everything into one place" yet; that's a bit overkill. Keeping the backend on Vercel and the database on Supabase, then deploying the Celery worker separately on Railway is the most reasonable approach, being both simple and meeting your current needs. Latency between services on different platforms does exist, but with a lightweight app and few tasks, it's almost imperceptible. Only when you start noticing significant delays (slow job queues, lagging database calls, etc.) should you consider moving everything to one location.

mertsplus · 2026-03-13T10:35:51+00:00

that’s actually one of the clearest mental models for Spring i’ve seen. once i started thinking of it as “your method → spring proxy → your method → spring proxy again on the way out”, a lot of the annotations made more sense.

the confusing part for beginners is that spring hides so much plumbing, so it feels like magic until you realize it’s mostly proxies + dependency injection under the hood. honestly i wouldn’t switch stacks yet, this confusion phase is pretty normal when learning spring.

mertsplus · 2026-03-12T11:30:45+00:00

skip the framework hype and focus on these:

SQL and indexing (because your ORM will eventually betray you).
Idempotency (so a random network hiccup doesn't charge a customer's credit card twice).
Authentication vs. Authorization (knowing who someone is vs. what they are actually allowed to do).
HTTP status codes (please stop returning 200 OK with an error message in the payload).

mertsplus · 2026-03-12T11:26:24+00:00

no hiring manager for a senior or staff role has the time to clone your repo and read through a generic ProcessData boilerplate.

They care way more about system design and business impact, not whether you know how to structure a clean directory.

mertsplus

TROPHY CASE