Ask HN: Do engineers like the term low-code?
Hey ve been wondering if engineers genuinely like the term “low code”?
Or is it something they might scowl at like “digital transformation”.
Or is it something they might scowl at like “digital transformation”.
20 comments
[ 0.26 ms ] story [ 45.4 ms ] threadIt usually means “that has a shitty DSL”.
So I don't think I have any opinion on "low code", but would evaluate the product on a case by case basis.
For example, my startup Appsmith.com, helps developers make internal tools by connecting to datasources and not worry too much about the frontend/UI components. And then they can use JS to make these UI widgets to interact with the data.
I write complex distributed applications, but wish my life would be easier. I don't care about having my job forever nor fear innovation. Anyhow, I think it might take a while until low code or no code becomes a thing on what I do, but I deeply believe in a future that doctors, engineers and everybody will use those tools to build amazing things, or cure really hard diseases, or whatever people might invent.
I think we are living in an awesome time and I love to hear about it, how clever some low code or no code are, and how it empowers people.
I don't have a better name to offer, so I have no major gripes with low code.
For example AWS Lambda is low-code in a way. You only need to write the code for the function, not the server or scaling. But that might not be low enough.
Excel is low code, but that's old. Does low code mean newfangled?
I think it could be confusing what is low code and what is not.