[echohack5]

If the thing standing in your way to engineering a great product was syntax, and a bunch of gate-kept and inconsistent linux cli tooling, then its fine to call it engineering.

I dunno, do you read bytecode?

[GeneralMayhem]

I don't think that's the point. If non-technical people are able to make a product happen by asking a machine to do it for them, that's fine. But they're not engineering. It simply means that engineering is no longer required to make such a product. Engineering is the act of solving problems. If there are no problems to solve, then maybe you've brought about the product, but you haven't "engineered" it.

I don't think that memorizing arcane Linux CLI invocations is "engineering" either, to be clear.

[thunky]

If I were to "build" the next big app entirely using llms, never writing a line of code, did I create it and do I own it?

If you answered yes that's really all that matters imo. Label me what you want.

[NotAnOtter]

If the thing gating your from creating a great product was the engineering, then I would call you a great product designer and not an engineer. If you suddenly can create products with a new tool - you didn't change, the tools did.

You're still a great product designer and not an engineer.