DEV Community

Discussion on: No, it is not shameful for a developer to use No-code

Collapse
 
karthik2206 profile image
karthik2206

Showing the "code" we write today to programmers from 50 years ago they would probably think that everyone from CEOs to grandmothers to school children must be writing software with how easy it became

Haha, well said and yet here we are :).

Addressing some of the other points raised:

  1. Non-proprietary: I totally get where you are coming from and would love that too. But I doubt that's going to happen anytime soon. The reason I don't have a problem is that I think most people don't ever tread the path of building products because they don't know to code - so clearly there is no success in that path.

I would rather that they easily build products and succeed, to then realise that they might have to refactor a lot of things. I would consider that a great problem to have.

  1. I think apps will integrate with one another more natively, so that a testing framework will be more implementable. This would happen, but you are right currently there isn't one.

By no means is nocode for very complex usecases, but I think for a large set of first-version products, it does an amazing job.

  1. I personally haven't felt the lack of a versioning system to be very painful. Yes, there are times when I am working on multiple parts of the app and want to push only part of it, but I can't do it. But that's again fine.

Overall, I am not saying that it is world without compromises. It is just that this world opens the doors for a lot of non-developers to build products. For developers, I think implementing such solutions allows them to outsource the management of certain workflows to non-developers. You aren't always responsible to add features, debug, etc.

Collapse
 
kallmanation profile image
Nathan Kallman • Edited

I would rather that they easily build products and succeed, to then realise that they might have to refactor a lot of things. I would consider that a great problem to have.

It's a better problem than never having built anything, I agree. But being the one who's come in to clients that need to either rebuild their whole tech stack or go out of business; I can't call that a "great" problem ;) always a tough conversation.

I think implementing such solutions allows them to outsource the management of certain workflows to non-developers. You aren't always responsible to add features, debug, etc.

Sometimes this works... what I've often experienced is the non-developers don't want to be technical enough to even use the "simpler" tool provided to them, and just make me do it (again, I'll stick by my claim that "syntax isn't the hard part")


I'm glad people are finding success and I do hope no/low code can grow into a useful thing for all; but for me it's not there yet (but it totally could be with a few changes).