These abstractions are great but are contributing to brutal de-skilling.
What do you mean?
Javascript YAML warriors not understanding what a computer actually is.
Also https://noyaml.com/
Show HN: I built a backend so simple that it fits in a YAML file
11–20 of 80 posts
Re: Show HN: I built a backend so simple that it fits in a YAML file
#12These abstractions are great but are contributing to brutal de-skilling.
Maybe, but they're selling a backend-as-a-service - it's like arguing that taxis are contributing to de-skilling because using them doesn't teach you how to change a brake pad.
Re: Show HN: I built a backend so simple that it fits in a YAML file
#13> However, their no-code approach generates awful code difficult to follow, making apps less reliable. Moreover, using a UI is slower than coding, especially now that AI assistants are here to help you.
I don't get this one, the sentence "their no-code approach generates awful code". If it's no-code, why do you care about code ?
Also, in what way are you relying on "coding" ? No information on this on the front page, to me it seems just like a config file only. Are you saying that the config only generates the boilerplate that the user will modify afterwards ? If that's the case, it's really not obvious.
Re: Show HN: I built a backend so simple that it fits in a YAML file
#14These abstractions are great but are contributing to brutal de-skilling.
Seems like a weird take. To me it's just another abstraction level, could be useful for quick PoC or hobby website, could be unusable for a backend that wants larger features. Either way, where do you draw the line between useful abstraction and "de-skilling" ? Like, should I craft by hand all my docker containers, and is the quick config file "deskilling" me ?
Re: Show HN: I built a backend so simple that it fits in a YAML file
#15Any plan to plug this into an LLM and generate a backend in virtually any stack/platform?
The idea seems cool, provided it supports more features like authentication type, generic middlewares, rate limiting, etc.
Re: Show HN: I built a backend so simple that it fits in a YAML file
#16These abstractions are great but are contributing to brutal de-skilling.
Said the assembly programmer to the C programmer.
Re: Show HN: I built a backend so simple that it fits in a YAML file
#17I can’t think of a single time where my backend was literally just a crud api over entities. These toys fall apart beyond a hello world app.
No validation, no authorization, no authentication, no property level permission, no events, no auditing… the list of what is actually needed for a real application goes on.
Re: Show HN: I built a backend so simple that it fits in a YAML file
#18Developer discovers he can type emojis on his PC
Re: Show HN: I built a backend so simple that it fits in a YAML file
#19Earlier quoted context omitted.
What do you mean?
Javascript YAML warriors not understanding what a computer actually is. Also https://noyaml.com/
Out of spite and because I could, I deleted all the text in the noyaml site and then clicked "save". Sorry if you were too slow to read it. Might find it in the waybackmachine?
Re: Show HN: I built a backend so simple that it fits in a YAML file
#20> However, their no-code approach generates awful code difficult to follow, making apps less reliable. Moreover, using a UI is slower than coding, especially now that AI assistants are here to help you. I don't get this one, the sentence "their no-code approach generates awful code". If it's no-code, why do you care about code ? Also, in what way are you relying on "coding" ? No information on this on the front page,…
Hi there ! Dev here, thanks for the feedback. Yes the example in the homepage (https://manifest.build/) generates the DB, Admin panel and REST API, we will adapt if it is not clear.
You asked an interesting question: "should you care about code quality if you use no-code tools?": As a developer, I would say definitely say yes because not understanding your own code (or your team's code) will soon or late lead to issues. If you work on a team with PR validations or similar, how can you validate your teammates' code if the code is unreadable ?