Developers who earn stable MRR through coding are not those who learn quickly within a year.
Want to make a breakthrough in income? First adjust your expectations—unless you're particularly talented or the product itself is solid, you're likely to face rejection in the early stages.
Last year, I built 5 fully functional prototypes. Sounds good? But none of them reached MVP. The problem isn't code quality; it's execution. Often, the technical aspect isn't the issue—it's the speed of decision-making, persistence, and direction adjustment.
This is the reality.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
22 Likes
Reward
22
9
Repost
Share
Comment
0/400
FundingMartyr
· 01-09 00:35
Really, not a single one of the 5 prototypes worked out—I believe that statement. Execution capability is indeed the biggest pitfall.
View OriginalReply0
ruggedSoBadLMAO
· 01-08 21:31
The one whose five prototypes all turned yellow has something to say, haha
View OriginalReply0
APY追逐者
· 01-08 14:28
It sounds like you're talking about me... None of the 5 prototypes have passed the MVP stage, that must be really exhausting.
View OriginalReply0
CountdownToBroke
· 01-06 01:59
Really, none of the 5 prototypes have an MVP, and that's the most heartbreaking part. No matter how beautiful the code is, what's the use? To be honest, it's still a matter of execution capability.
View OriginalReply0
SnapshotLaborer
· 01-06 01:59
Really, writing code is just the basics; the hardest part is actually creating something and surviving.
View OriginalReply0
LiquidationSurvivor
· 01-06 01:56
These five unfinished prototypes... aren't they just my copy from last year? Haha
View OriginalReply0
MysteryBoxBuster
· 01-06 01:54
Yeah, that hits close to home. I'm the kind of person who has all 5 prototypes die at the MVP stage. Looking back, it was really a waste of time.
View OriginalReply0
GasGuzzler
· 01-06 01:48
Really, the fact that none of the 5 prototypes passed the MVP really hit me. Me too, technical issues are not the problem; they are even more frustrating because you can't blame the code...
View OriginalReply0
ShibaSunglasses
· 01-06 01:35
Really, none of the 5 prototypes worked, that's the most heartbreaking part. Even if the code is awesome, it's useless.
Developers who earn stable MRR through coding are not those who learn quickly within a year.
Want to make a breakthrough in income? First adjust your expectations—unless you're particularly talented or the product itself is solid, you're likely to face rejection in the early stages.
Last year, I built 5 fully functional prototypes. Sounds good? But none of them reached MVP. The problem isn't code quality; it's execution. Often, the technical aspect isn't the issue—it's the speed of decision-making, persistence, and direction adjustment.
This is the reality.