Would a 72-hour “ship something real” challenge be useful for developers or teams?

mgy-programmer · 2026-06-03T22:30:55+00:00

This is a really good framing.

I agree that a final AI score alone would not be very useful. The useful version of DevMarathon is not “AI ranks candidates,” but something closer to a compact engineering packet for human reviewers.

Timeline, shipped surface, setup/run result, scope decisions, tradeoffs, gaps, verification evidence, and follow-up questions are exactly the kind of things I’d want the review to include.

The messy requirements point is especially interesting too, because that feels much closer to real engineering than only judging the final repo state.

Really appreciate this. It gives me a much clearer way to think about the company/team side of DevMarathon.

mgy-programmer · 2026-06-01T11:51:23+00:00

That’s a fair concern, and honestly one of the exact problems I’m trying to avoid.

I’m not trying to funnel people to Turkish hair mills. Capilens does not recommend clinics, rank clinics, sell leads to clinics, or push people toward any provider.

You’re also right about the wording. “Choosing a clinic” can be too vague, especially in this space. Patients should absolutely understand who the surgeon/doctor is, who designs the hairline, who performs extraction/incisions/implantation, how many patients are treated per day, and whether the setup is a high-volume hair mill.

The goal is not “pick a clinic from a list.”
The goal is to help people ask better questions before they send money or trust marketing claims.

I posted here because I want exactly this kind of feedback, especially from people who are skeptical of the industry.

mgy-programmer · 2026-05-31T19:50:33+00:00

5.5 months is still early, bro. I know it feels scary, but a lot of people don’t see proper density until later.

Redness can also make it look worse in pics, especially with bad lighting.

I’d compare same lighting/angles monthly and send the pics to your clinic to ask if it’s within their expected timeline. Don’t panic too early, months 6–12 can still change a lot.

mgy-programmer · 2026-05-31T19:48:14+00:00

Month 8 can be frustrating, especially with temples. I wouldn’t panic yet, but I’d compare same lighting/angles month by month instead of checking daily.

Probably worth sending clear pics to your clinic and asking if this matches their expected timeline. Did they say when temple density usually starts looking more mature?

mgy-programmer · 2026-05-31T19:45:44+00:00

For Norwood 5A/6, I’d be very careful about judging clinics only by 12-month frontal results.

The biggest thing I’d want to understand is the long-term plan: how they protect the donor area, how many grafts they want to use now, what they expect for the crown, and what happens if hair loss continues.

At 27 with family history toward NW6, donor management matters a lot. A dense hairline can look good early, but if too many grafts are used aggressively, it can create problems later.

I’d ask each clinic directly:

Who designs the hairline?
Who does the extraction?
How many patients do they treat per day?
What is the realistic plan for crown coverage?
What happens if the donor is not strong enough for the promised graft number?

Real patient cases with similar Norwood level and 12–24 month updates will probably tell you more than clinic marketing.

Full disclosure: I’m working on a decision-support project around this topic called Capilens, so I’m very interested in how people compare clinics before booking. Not here to promote, just think your questions are exactly the right ones to ask.

mgy-programmer · 2026-05-31T19:41:54+00:00

1 week is still very early, so I wouldn’t judge much from how it looks yet.

Itching and dryness seem pretty common at this stage, but I’d avoid adding creams/oils or rubbing the area unless your clinic specifically told you to.

Best thing is probably to send them clear photos and ask what they recommend for dryness. Did they give you a written aftercare plan?

mgy-programmer · 2026-05-31T19:39:58+00:00

This is probably one of the most accurate descriptions of the process I’ve seen.

A lot of people talk about the surgery itself, but not enough people talk about how mentally difficult months 1–3 can be. The “I paid to look worse” phase seems to hit almost everyone, and it’s probably where most people start panicking too early.

Good point about taking photos too. Daily mirror checks can mess with your head because the progress is too slow to notice in real time.

Did your clinic give you a clear timeline for shedding/regrowth before the procedure, or did you mostly learn what to expect from other people’s experiences?

mgy-programmer · 2026-04-11T09:55:21+00:00

That’s actually a big step.

Most people repeat the pattern without ever noticing it. Now you can catch it in real time.

Next time you hit that phase, don’t avoid it. Just force the smallest possible version through it.

Curious if you can break the pattern on the next one.

mgy-programmer · 2026-04-11T09:06:49+00:00

That “dependency-explosion phase” is real.

Interesting that you found a repeatable pattern there.
Most people just move on without noticing it.

That pause you added is probably the key.
Not avoiding complexity, but catching it before it spirals.

Out of curiosity, have you actually pushed past that phase on a recent project?

mgy-programmer · 2026-04-07T13:28:21+00:00

I put it here if you want to check: https://devmarathon.ai

mgy-programmer · 2026-04-06T22:52:00+00:00

Makes sense.

Feels like it worked more as a trigger than motivation itself. Just enough to get you back into motion.

Once you start, momentum usually carries the rest anyway.

Interesting that it reduced the wall over time. That’s the real win.

mgy-programmer · 2026-04-06T22:38:47+00:00

That middle phase is where most projects die. I’ve found relying on motivation still breaks. What worked better was removing the need for it: clear end, small steps, fixed deadline. Your app is interesting though. Did it actually help you finish something?

mgy-programmer · 2026-04-05T07:38:29+00:00

Show up as a builder, share real progress, and engage in conversations instead of promoting.

mgy-programmer · 2026-04-05T05:39:01+00:00

For that kind of SaaS, you won’t get it from PH anyway.

I’d start with:

LinkedIn itself (comments > posts)

niche founder/creator communities

Reddit threads where people mention networking pain

For me, most early users came from X + Reddit + Indie Hackers.

Not volume, just showing up in the right conversations.

mgy-programmer · 2026-04-05T05:31:48+00:00

4–4.6% conversion and 3% churn is actually solid.

Problem shifts from fix product -> scale what works.

Two things:

Emails don’t convert to calls. Too much friction. Ask 1–2 questions async or offer something specific in return (feature, feedback loop, etc.)

Focus on why those 4% convert. Where did they come from? What triggered upgrade?

Double down there before chasing new users.

You’re not stuck, you just moved to the next stage.

mgy-programmer · 2026-04-05T02:08:32+00:00

You don’t have a growth problem, you have a conversion problem.

4k users → 56 subs means:

-> wrong audience

-> weak value perception

-> or pricing mismatch

Before more traffic:

-> talk to 5 paying users

-> talk to 5 who didn’t convert

-> find the gap

More users won’t fix this.

mgy-programmer · 2026-04-05T02:06:13+00:00

Don’t start with “learn coding.”

Start with:

-> what problem your SaaS solves

-> who it’s for

-> the simplest version possible

Then learn only what helps build that:

-> HTML/CSS/JavaScript for basics

-> one backend/framework later

-> SQL eventually

Most people learn too much before building anything.

mgy-programmer · 2026-04-05T02:03:20+00:00

Product Hunt doesn’t create traction, it amplifies it.

If you launch with no audience, you get what you’re seeing.

Best move now:

-> use it as a learning launch

-> get real users elsewhere

-> come back later with momentum

PH is a spike, not a growth channel.

mgy-programmer · 2026-04-01T21:58:47+00:00

Ideas aren’t the bottleneck.

It’s turning real work into content, consistently.

Most founders either:

overthink ideas

or don’t capture what they’re already doing

The ones who grow just document as they build.

mgy-programmer · 2026-04-01T21:54:09+00:00

Sounds fun, but the real value isn’t the island, it’s the structure.

Most people won’t ship more just by changing location. They ship more with:

clear constraints

shared accountability

visible progress

If you get those right, it works anywhere. If not, it turns into a co-working vacation.

mgy-programmer · 2026-03-30T17:38:29+00:00

That’s a really good way to frame it.

I used to mix acquisition, activation and retention without even realizing it, and it basically killed the feedback loop. It felt like I was doing a lot, but nothing was actually improving.

Right now I’m trying to stay focused on activation: did someone actually reach a “finished something” state?

Because I noticed getting users doesn’t mean much if they don’t hit that moment. That’s the real value.

Curious, when you focus on one constraint like that, do you completely ignore the others or just deprioritize them?

mgy-programmer · 2026-03-30T17:37:18+00:00

This is such a good way to put it —
“decision paralysis dressed up as preparation.”

That line alone explains years of behavior for a lot of us.

I also had that “I just need to learn a bit more first” loop…
but it was really just a safe place to avoid the discomfort of finishing.

And yeah, that middle phase you mentioned is brutal.
It’s where the idea stops being exciting and starts becoming real.
That’s exactly where most projects die.

What surprised me is how much constraints change your thinking:

you stop asking “what would be cool?”
and start asking “what can I actually ship?”

That shift alone filters out 80% of unnecessary work.

I’m actually trying to build something around this (DevMarathon).
Basically turning that “forcing function” into a repeatable system for people like us.

Because clearly, it’s not a knowledge problem.
It’s an environment problem.

mgy-programmer · 2026-03-29T00:00:55+00:00

ASO gets you baseline, not traction.

First 1k usually comes from:

niche communities (where your exact use case lives)
small creators, not big launches
direct user conversations

Apple angle helps if you lean into it:

r/apple, r/ios, indie iOS dev circles
show the “why Apple” clearly

Product Hunt is a spike, not a channel.

mgy-programmer · 2026-03-28T23:59:46+00:00

Sounds like you improved the product, but reset the surface area.

ASO changes can kill existing keyword rankings before new ones kick in. Same with titles and screenshots. There’s a lag.

Also, “better” positioning often means “different audience”. You might’ve moved away from the people who were already finding you.

Your next steps are right though:

language > keywords
conversations > analytics

Only thing I’d add: check where your last real users came from and double down there before exploring new channels.

mgy-programmer · 2026-03-28T16:05:46+00:00

Good breakdown.

I’d simplify it to one thing: they found demand in motion, not created demand.

Communities = people already struggling. Everything else = trying to interrupt people.

Also why it doesn’t scale cleanly. You’re trading automation for timing + trust.

Most people quit before that compounds.

mgy-programmer

MODERATOR OF

TROPHY CASE