A developer argues that no-code and low-code builders should ask harder questions instead of rushing to answers. Uncertainty and unfamiliar problems are where growth happens. Senior developers who seek out challenges, not just solutions, advance fastest.
Seek questions more than you seek answers. Particularly when you're working in these no-code, low-code environments, we're doing things that are mysterious to us. Mysterious in a way that is usually outside the realm of things that have been questions to us in the recent parts of our career. What's our domain knowledge? We might have great expertise about, which we got through being willing to experiment. We haven't had to do that in a while. And now here we are building some sort of technology product and we acknowledge we not know how to do something. We're not even sure what it is maybe that we should do. And I think we should be embracing those questions. Embrace the question, what is it I should be doing? And embrace the search for the answer to that question. That's not meant to be something that you have no, the answer to off the bat. It's going to be something you want to discover along the way. And I'll tell you, there are plenty of people who are very senior developers who have been building software all their lives and they don't quite know what they're going to build next. The most successful of them seek the questions. They seek the hard parts. That is going to be the way they grow. That's what you get people
