r/lowcode • u/Cloudy_Day912 • 6d ago
Is low-code actually saving time, or just moving the problems around?
The more I read about low-code, the more I wonder how much time it really saves once a project starts getting bigger.
Building something basic seems pretty straightforward. But then you need one custom feature, an integration doesn't work the way you expected, or you end up spending hours trying to get around some limitation. I was going through a few development discussions, and geekyants came up along the way. It got me thinking about whether it's better to deal with those limitations or just build things from scratch at some point.
I'm curious how others handle this. Do you stick with low-code as long as possible, or is there a point where you just feel like it's not worth the hassle anymore?
2
u/Tern8762 6d ago
A hybrid approach works well, with low-code for the data layer and simple workflows, and a custom service for the rest. Of course this doesn't work if the low-code tool lacks an API.
2
u/seatable_io 6d ago
It's definitely worth it, but as with all tools the main question is what you need. If it's flexibility and the ability to build and expand your customized tool without waiting for an engineer or integrator, no-code or low-code really should be the way to go.
In my experience, the time saved depends less on project size than on who owns the system. When the people who use the process can adjust it themselves, changes take hours instead of a sprint queue. That's where low-code pays off long after the first prototype.
What I'd check before committing: How do rate limits and permissions behave once more teams use it? Can you test the integration you need in a trial, not just see it listed? And what does migrating out look like, e.g. via a full export?
2
u/BringBackManaPots 6d ago
The benefit is that you can have people work in areas where they aren't experts. The downside is that you now employ people that aren't experts. Do with that what you will.
1
u/SirMcFish 6d ago edited 6d ago
We've had a new director come in, he insists it's the way to go... A project that we C# Devs would've finished by now, and be training out, is now looking like being ready in 2028, and will be massively over budget... I'd have loved to be given the kind of deadlines he's getting away with.
1
u/rando1-6180 6d ago
Way back I used airtable and consumed updates via API. We moved away from it, but a bunch of other low code offers appeared afterwards. I didn't follow up though.
Today, would a new director with an actual Dev team not use agentic AI tooling? You seem to have a front row seat and I'm curious what the thinking might be. Is it SLA concerns? His prior experience with successful low code implementations? Short term budget constraints? Was this an agreement in his hiring?
1
u/SirMcFish 5d ago
He's just an arse who thinks his ideas are the only ones worth merit.
We're a small in house Dev team, 5 Devs, the specs we usually get fit on one A4 sheet if that, we've always over delivered and always done that on time in my 6 years here. The rest of the business knew they could get us to do pretty much anything.
In he comes, we get stopped from developing anything new, because it's all going to be done in Dynamics from now on... 9 months in, nothing delivered, deadlines extended ridiculously. Contractors bought in, 3rd party dynamics company hired... And still naff all delivered, but it's the future it's better... Now they get another year...
In the 9 months of their non,-delivery I've integrated 2 completely new 3rd party complex systems and extended current system capabilities, and that's just me, the other Devs have also delivered other stuff too, but, yeah no/low is still better...
1
u/rando1-6180 5d ago
That's just really sad. Not leveraging a proven and already hired team is a bad production approach and negative for building a team culture. Whatever happened to measure twice, cut once?
I always find it ironic that people who don't have their hands on the work end up making decisions about how the work is done. The thinking might be specialization of labor, but there needs to be enough of an overlap to keep policy and the nuts and bolts of the work in alignment. As I recall, low code was sold as a way to reduce your dependency on high cost development work. I'm not sure how much of that still applies with agentic AI in the hands of devs with institutional knowledge.
All of this makes me wonder who put him in place and how much homework they did. You don't always have to promote from within, but not checking in with your own people seems really short-sighted.
1
u/SirMcFish 5d ago
Oh well got a whole new load of directors who are just faceless bureaucrats now. They gave him a job because people they know had done similar stuff and they just believe all the bull he spouts.
Most of us are just going for as long as we can until, hopefully, they pay us off... A couple have got out. It's a shame because it was a special place before, now it's corporate bollockville. Oh hum.
1
u/rando1-6180 5d ago
Sad, but not unique. It sounds like the inmates are running the asylum now. This might be called enshitification at the company level.
I hope they take care of you and you get to do what you makes sense to you.
1
u/SirMcFish 5d ago
Aye that's the only hope. Too old to easily move, too young to retire... Feel trapped, but I still get paid and as long as that keeps happening I'll take it 🤣🤣
1
u/JakubErler 6d ago
Depends completely on platform and can not be generalized to "low-code" because the differences are huge.
1
u/WastedYouth39 6d ago
Isn’t that same for any software.. a lot of companies outgrow their initial licence with their first supplier they build up a load of historic data so when they move to a more enterprise level solution its an absolute pain. There is no perfect solution
1
u/rando1-6180 6d ago
It's a form of lock in. It only gets worse the more you struggle like those finger traps. Imagine porting all those integrations and retraining staff you accumulated over the years.
1
u/tcpukl 6d ago
What is low code? Appeared in my feed.
1
u/Available_Safe1818 6d ago
Building a website with Wix, I think is one example. Something that sets up parts of your system without you having to code much of them.
1
u/Zealousideal_Art1720 18h ago
I think low-code genuinely saves time when you're building something with predictable workflows, internal dashboards, or MVPs. The problems usually start when the application needs complex business logic, custom integrations, or more control over performance.
My approach would be to use low-code for the parts it handles well and keep custom code for the parts it doesn't. I wouldn't rebuild everything from scratch just because one feature becomes complicated. The real deciding factor is whether maintaining workarounds is taking more time than implementing the feature properly.
2
u/Square_Technician983 6d ago
I would say both: It saves a lot of time up front and moves the problems to a later stage. Low-code works best when tehe core of your app is data and simple workflows. But it gets painful when you need complex logic, integrations or fine-grained performance tuning. API, webhooks, scripting or custom code blocks and an easy data export are essentials when building something with a low-code tool.
But to give you a straight answer to your question: With low-code tools you have much more flexibility to build the system you actually need and I would stick with it as long as workarounds are the exception. When the workaround becomes the rule it's time to part.