Live data from Hacker News

Is Low Code The Future? How I built and shipped my revenue-ready MVP in 4 hours

bethanvincent.com

11–20 of 53 posts

Re: Is Low Code The Future? How I built and shipped my revenue-ready MVP in 4 hours

#11
Low code is definitely the future. Look at all the things you can do by calling the right APIs and/or all the scaffolding available. The clear trend changed after RoR and managed cloud services like Heroku popped up. Now the big players offer cloud services that would take months to code but if you pay up you have access (everything as a service). The lesson for developers is work on tools consumed by other developers and if this is not the case probably someone else is working on automating bits of pieces of your work.

Re: Is Low Code The Future? How I built and shipped my revenue-ready MVP in 4 hours

#12
"I literally built a business in an afternoon and so can you."

Are you charging money and have customers actually paying you? If not, it's not a business yet. It's a website.

This barely functions as a website and looks like a few components thrown together using a bootstrap template.

Re: Is Low Code The Future? How I built and shipped my revenue-ready MVP in 4 hours

#13

For 4 hour experiments, it sounds like a reasonable strategy; but what happens are your requirements become increasingly complex? Is "Low Code" going to work, for example, if you want to implement A/B tests? Possibly one day.

For what should be a prototyping solution: Definately, a resounding Yes!

Re: Is Low Code The Future? How I built and shipped my revenue-ready MVP in 4 hours

#15
I vehemently disagree. To me, this is a classic case of people who believe in YAGNI versus people who plan (sometimes too much) for the future. I've been burned too many times to be able to adhere to the YAGNI protocol. Sure, these low/no-code solutions may work fine for a while but eventually, they'll hit an impassable roadblock and then they're stuck until they either decide that roadblock isn't worth overcoming or put in the time and effort that could have been accounted for at the beginning.

Re: Is Low Code The Future? How I built and shipped my revenue-ready MVP in 4 hours

#16

"I literally built a business in an afternoon and so can you." Are you charging money and have customers actually paying you? If not, it's not a business yet. It's a website. This barely functions as a website and looks like a few components thrown together using a bootstrap template.

If they were charging for it, they would have called it "revenue-earning" instead of "revenue-ready".

What does "revenue-ready" even mean? They're willing to accept money for it? Really high bar to clear /s

Re: Is Low Code The Future? How I built and shipped my revenue-ready MVP in 4 hours

#17
The criticism -- almost all the other comments at this point -- focuses on one aspect of the low-code app:

It has to be re-written once it grows. *

While this is true, I don't think Bethan or any other low code advocate would dispute that. The question is: can you get test an idea with low code.

The answer to that might be a trivial yes, but if you had asked me what that means, I would guess a team of 3 people could prototype an idea in about a week.

I did not expect a single person to be able to test an idea in 4 hours. That is the real insight here.

* Not all the criticism. One person points out that calling it a business is overblown till someone pays for it.

Re: Is Low Code The Future? How I built and shipped my revenue-ready MVP in 4 hours

#18
As a programmer, I kinda don't want it to be, but I acknowledge that as short-sighted.

In general, "low code" should be the future: because efficiency, and maturity of available libs/components. What i'm saying is that this should be seen as a win.

Post reply on HN