Live data from Hacker News

Will low and no code tools ever truly disrupt tech development?

stackoverflow.blog

131–140 of 208 posts

Re: Will low and no code tools ever truly disrupt tech development?

#132
post #32

My main issue with low-code/no-code is that it attempts to solve the complexity problem, without understanding what "complexity" is. Code is perceived to be complex, but when you look deeply into what people mean when they say that, it's almost entirely a social perception. They see these weird characters and it looks like gibberish and they assume that the people who understand this gibberish are somehow on another…

The classic Mythical Man Month makes a crucial distinction between "accidental" and "essential" complexity. Accidental complexity is stuff that it is in your solution, but is not necessary. For example, you added a layer of abstraction that ultimately isn't necessary and doesn't have benefits outweighing the costs. Essential complexity is intrinsic to the problem itself. For example, if you write software to help you…

I venture the opinion that the overwhelming majority of the complexity on most current software is accidental. It's the kind of share that you measure in 9s, not on raw percentage.

Some stack that avoids all that complexity would be technically "low-code". But the format of the low-code stacks people push around today is incompatible with general development, and doesn't actually make most of the complexity go away.

Re: Will low and no code tools ever truly disrupt tech development?

#133

My main issue with low-code/no-code is that it attempts to solve the complexity problem, without understanding what "complexity" is. Code is perceived to be complex, but when you look deeply into what people mean when they say that, it's almost entirely a social perception. They see these weird characters and it looks like gibberish and they assume that the people who understand this gibberish are somehow on another…

it just comes down to abstraction and associated tradeoffs. Low-code/no-code fundamentally isn't all that different from the difference between using Python vs a lower level language.

Re: Will low and no code tools ever truly disrupt tech development?

#134

I use them to great advantage as an engineering manager. If you have programming skills, you can use these tools to whip stuff up significantly faster than people without programming skills. It’s an organizational super power. I just replaced an internal web app used for planning with a data visualization tool dashboard that can spit out a spreadsheet for further analysis. Took a week to build something that solves t…

I’m increasingly of the opinion that if it doesn’t face customers it should be done using something like Retool. Especially considering that you can just plug it into your internal APIs so if you need to do anything particularly hairy you can still use your backend.

Re: Will low and no code tools ever truly disrupt tech development?

#135
post #46

My main issue with low-code/no-code is that it attempts to solve the complexity problem, without understanding what "complexity" is. Code is perceived to be complex, but when you look deeply into what people mean when they say that, it's almost entirely a social perception. They see these weird characters and it looks like gibberish and they assume that the people who understand this gibberish are somehow on another…

I think any discussion about no-code/low-code and if it's effective has to take into account Unreal Blueprints. Game development is full of inherently complex problems, but some people are able to pull it off with Blueprints. What's important about that though, is that Blueprints live inside a complex codebase focused on game development, so the graphical/node based toolbox you have is extremely powerful because deve…

Low-/no-code environments are really great for exposing domain-specific landscapes to non-coders, but that significantly reduces the hype value of the lingo, which aims to convince buyers that they can replace those pesky non-specific domain problem spaces and coders with capex and a smidge of opex. The value proposition of these products is the same as before because this is a repackaging of fourth-generation languages, and the economics have not changed.

The more narrow the domain, the easier it gets to figure out a low-/no-code environment that will work for the users. But the smaller the base of purchases. And distilling the complexity to just the right level still takes some really bright domain experts with extremely good intuition of where the most profitable use cases lay (the hardest role to fill) and highly empathetic coders (also hard to fill) who work well together (extremely rare), or a single person who embodies both (unicorn).

If energy and money were no object, low-/no-code is absolutely A Thing. I believe there is some kind of emergent Shannon–Hartley theorem behavior here, where complexity down a communications network with certain noise/bandwidth/etc. properties has some suspected hard physics-as-we-know-it limits.

Re: Will low and no code tools ever truly disrupt tech development?

#136

As someone who got their start in tech with a low-code environment (ServiceNow reporting) I have found the true value of low code is the ability for business/ops teams to create tools that serve their needs without waiting on a team of "real" developers to make time for them. One of the biggest benefits is the sense of excitement this creates for these users as they are able to add the logic of programming into a pro…

I 100% agree on the savings of real developer time when end users can self service. At the same time, I've also seen users do incredibly crazy things because either they didn't know any better or just didn't bother to "read the code". Good example of this is people just keep creating Statuses in JIRA until you end up with "Which of these 264 'Completed' statuses is the one I want?". It's similar to the Ops person "He…

> At the same time, I've also seen users do incredibly crazy things because either they didn't know any better or just didn't bother to "read the code". Good example of this is people just keep creating Statuses in JIRA until you end up with "Which of these 264 'Completed' statuses is the one I want?".

Why is this a problem? Programs are a means to an end. The 264 Jira statuses are messy and could be done away with, but would a clean solution actually change anything for the better? In a significant, "it was worth spending the money on a real developer" way?

Re: Will low and no code tools ever truly disrupt tech development?

#137
post #12

I do a fair amount of pre-seed and angel investing and I've seen a _massive_ increase in the number of very early businesses that have a "product" that they've been able to build with no/low code tools. It gives non-tech founders a set of options they've never had before, in my experience. That obviously isn't viable for all early businesses and even the ones it is viable for eventually need to hire engineering teams…

I am a non-tech founder building a app on building, basically very CRM/Data centric for a specific industry vertical I work in professionally.

I am pushing Bubble to its limits where I have access to approx 150m records with all sorts of other database relationships to many millions of records.

To build this app in a custom software solution, I have been quoted $100k to $500k depending on the backend architecture.

Instead, I am spending around $20-30k in development costs to get my app off the ground to be able to pick up the first paying users... at least that's the goal and I'm a few weeks away from launch.

I would also say that my "MVP" is not like Airbnb's MVP... my hope (and it seems) that it may be functional enough to nearly (70%) replace my existing CRM that I use day to day. Of course, I am planning to transition to a custom software solution once I validate, so I don't see bubble as a long term solution.

I've self taught myself a bit of python and tried teaching myself JS as well off and on, so I am able to generally talk through with software developers what I'm trying to achieve and generally understand the technical things that might be discussed. So I'm not entirely a total non-technical noob.

But the issue with Bubble is there is still a high barrier to actually learning how to use the platform for the average non tech person. It's a black box of sorts and they don't have the best education (unlike webflow). I mean come on, you have to pay $800 to take a bubble sponsored course? Lame. Nonetheless, you learn programming concepts by learning how to build on bubble.

I'll end by replying to the top comment about code being perceived as complex.

Spanish isn't complex. Nor is French. Maybe we can consider Japanese to be more complex. But even then, millions of people speak it just fine. Conjugations in Spanish are complex for a 40 year old English speaker new to Spanish but not complex for a 8 year old native speaker.

But after a certain age, life takes hold, you begin working, and you lose the time and opportunity to spend 100's or 1,000's of hours learning another language. Trying to learn how to code is like this. I sometimes need to carve out 3-6 hours of a day to context-switch away from my busy (non-technical) professional & social life to get back into programming mode.

Low code tools abstract away hours of that complexity you would have to learn, which allows you to start building something functional quicker than you otherwise would have. I know software devs look at low code and say "what's the matter with this crap, I can just spin up a X to do Y in 1 week, this is worthless!". But you are the native Spanish speaker in my metaphor, not the folks learning Spanish way past the days they had time to learn Spanish in college, trying to build the next greatest Spanish hit song to tell their story (i.e. software app!)

Re: Will low and no code tools ever truly disrupt tech development?

#138
Did ever Visual Basic back in the 90's disrupt tech? Not that much. It certainly back then allowed a lot of people with low skill/experience in dev to jump in development. Was an inclusive tool but not revolutionary.

Tools like github copilot gives us a glimpse of how will be the tool that will revolutionize tech dev on day in the future IMHO.

Re: Will low and no code tools ever truly disrupt tech development?

#139
post #64

My main issue with low-code/no-code is that it attempts to solve the complexity problem, without understanding what "complexity" is. Code is perceived to be complex, but when you look deeply into what people mean when they say that, it's almost entirely a social perception. They see these weird characters and it looks like gibberish and they assume that the people who understand this gibberish are somehow on another…

Low code allows "less" sunken cost when the inevitable misalignment of requirements happen. It's same reason why design starts on napkins, then wireframes, and then low def, high def and eventually a fully interactive prototype. In software we dive into code way to eagerly and way too early in the product process. Equating no/low code tools to full on dev is impossible. Just as you wouldn't/shouldn't equate a design…

> In software we dive into code way to eagerly and way too early in the product process.

Low code doesn't help at all? It's still code.

> Low code allows "less" sunken cost when the inevitable misalignment of requirements happen.

Sunken cost is about investment already incurred that can't be recovered. It's very likely that low code increases software sunk cost problems.

If you use low code as a prototype thing to throw away, that's almost a complete waste of investment.

Wrong low code often is much harder to programmatically test for correctness and debug, so you often need a larger investment to fix it.

Re: Will low and no code tools ever truly disrupt tech development?

#140
Maybe this is inexperience on my part, but the LCNC tools I've used are very clunky, with UIs that are plain at best, and performance that is cumbersome. While there is certainly a place for them in the business world, I can't see them replacing a really snappy, custom product with beautiful and intuitive UX/UI.
Post reply on HN