Rails is better low code than low code
radanskoric.com
Rails is better low code than low code
1–10 of 249 posts
Re: Rails is better low code than low code
#2[deleted]
Re: Rails is better low code than low code
#3The low code space has been well explored. Excel is the flagship product in that space.
You tell me if you want to be involved with a long lived and non trivial collection of spreadsheets.
Re: Rails is better low code than low code
#4So low-code is faster to get started with little programming knowledge but isn’t expandable. OTOH, a language and framework that you’ve taken the time and effort to learn takes a little longer to get started but is ultimately more suited to more complex tasks.
I think the takeaway from the narrative here is knowing when to switch from the low code platform and call it a PoC. I’d have cut that off around the point that the custom lambda came into play. That way you’ve used the low code environment for what it’s good at, creating something “they” can react to and easily explore basic functionality. While at the same time you’re taking those learnings and building the more robust solution.
Re: Rails is better low code than low code
#5So low-code is faster to get started with little programming knowledge but isn’t expandable. OTOH, a language and framework that you’ve taken the time and effort to learn takes a little longer to get started but is ultimately more suited to more complex tasks. I think the takeaway from the narrative here is knowing when to switch from the low code platform and call it a PoC. I’d have cut that off around the point tha…
I agree that the main takeaway is knowing when to switch. Having a mental model for this makes many future discussions and decisions much easier, because this seems to be a conundrum that comes up frequently (even for me inside of a large tech organization!).
Based on my experience, I'd suggest the pivot point occurs before even starting: it should pivot around who is building and maintaining the system. If you have the experience needed to quickly develop a solution in code, do it in code. If not, because this is a non-technical team without technical resources, do it in low code. Simple as that.
Re: Rails is better low code than low code
#6I don’t want to build in a language without types, but low code is even less types than Rails. I’ve just never worked on a public app that was simple enough for Rails to feel good - Airbnb was rails but by the time I got there it was very much not simple. Internal tools in rails though, that is okay.
Re: Rails is better low code than low code
#7I don’t want to build in a language without types, but low code is even less types than Rails. I’ve just never worked on a public app that was simple enough for Rails to feel good - Airbnb was rails but by the time I got there it was very much not simple. Internal tools in rails though, that is okay.
I expect low code that can be translated into typed clean code. The low code side of it is just with more assumptions baked in. And with llms you can perhaps have a lot of leeway to in fact customize and allow low or no coders to specify somethinf exportable to readable typed code
Re: Rails is better low code than low code
#8It would be nice to get a brief definition of "low code." Otherwise great article. I've found myself using "low code" frameworks when they setup my environment for me and can generate the code files. Key example was a Minecraft mod maker. Within a minute I was fed up with the scratch style programming, but it had all the Java build stuff ready for me to just edit the files myself. No setting up gradle or anything.
Re: Rails is better low code than low code
#9It would be nice to get a brief definition of "low code." Otherwise great article. I've found myself using "low code" frameworks when they setup my environment for me and can generate the code files. Key example was a Minecraft mod maker. Within a minute I was fed up with the scratch style programming, but it had all the Java build stuff ready for me to just edit the files myself. No setting up gradle or anything.
I think this is the key to them actually being useful - generate a sane project in some widely used language under the hood, and let people give up on the low code solution when they outgrow the guardrails. Otherwise you're just dooming yourself to an eventual rewrite as soon as you need some feature that's not supported.
Re: Rails is better low code than low code
#10The low code space has been well explored. Excel is the flagship product in that space. You tell me if you want to be involved with a long lived and non trivial collection of spreadsheets.
[deleted]