Earlier quoted context omitted.
I think the abstraction layers are important, they should not be leaky. You shouldn't have to go up/down the stack. If you can't build what you want with one tool, then choose another tool.
Couldn't disagree more. Unless your job is unbelievably trivial, you should use a range of tools and use the best one available for the task at hand.
The “No Code” Delusion
331–334 of 334 posts
Re: The “No Code” Delusion
#332Earlier quoted context omitted.
Couldn't disagree more. Unless your job is unbelievably trivial, you should use a range of tools and use the best one available for the task at hand.
Lets say you call for pizza, but you need to know how to bake in order to use their self help service, then that's a leaky abstraction. As high levels of abstractions it's OK to only know the name of the different pizzas. And the baker doesn't need a master in chemistry or engineering to operate the oven. We humans are very good at abstracting things and take most abstraction layers for granted, even though the world…
If I order a pizza, I’m using a communication channel (phone, internet) to place an order; one tool.
I deeply hope the pizza place is using chefs and an oven to make the pizza; completely different tools.
If I demanded the pizza chef make the dough, slice the ingredients, and bake the pizza with just a stand mixer... that’s just dumb.
Use the appropriate tool for the job and use the right level of abstraction at each step.
Re: The “No Code” Delusion
#333Earlier quoted context omitted.
All you've said is 100% true, but in addition I'd argue that a big part of reason why no-code tools don't get more traction is also just the simple power of habit and the lack of motivation to invest time into learning it. We already know how to build things the traditional way, and all these no-code solutions require learning a lot of new, proprietary interfaces and stuff, playing with it and figuring it out, learni…
I don’t have enough experience with no-code tools either, but I don’t agree it’s motivation that prevents it from taking off. No-code is used mostly by non-technical founders who do seem quite motivated (enough to do it themselves). Engineers are more likely to build it themselves (realistically, over-engineer).