[ben-gy]

This is impressive for sure. It really makes me think how hackathons must be evolving with this type of tech available (last hackathon I participated in was ~8 years ago).

That said, and I feel a bit old for saying this, but I still prefer to write the code myself.

In every instance (so far) I’ve found I can produce the exact outcomes required faster by writing code (Rails is still crazy fast to scaffold solutions and install libraries) than trying to force a no-code/low-code platform to produce an equivalent outcome in a similar time frame.

Anyone else feel this way?

[ramoz]

So... I wish I could share how my company/team-within has been approaching federal procurement tech challenges. We've built automation from a design-first perspective, to combine what generation tools like Create React App, Ruby On Rails, .NET Entity, JHipster, openapi, etc all do. But with further abstraction through templating and initial app overhead buildout.

We'd have an mvp reddit in a day, scalable as needed (right now on K8s in any cloud).

Working on open source!!

[jarpschop]

I prefer code in the end because the flexibility is provides. At the end, a bunch of edge cases and weird situations that can't be handled by the simplified solution will arise, and in those situations having a complete programming language is the only way to get above them.I find the simplifying assumptions that low-code frameworks rely on sooner or later end up braking.