I don't accept that you can divide the world into 'developers' and 'users'. Allow me to explain.
Think about when you buy something. Some things you buy, say a DVD player, probably comes with a sticker on the case saying "No user-serviceable parts inside. If you even think about opening this case, the warranty is void." Then there are other things, say a bicycle, which almost invite you to tinker with them. With a bike you can see all the machinery and exactly how it works. And it is designed to be easy to to adapt - easy to attach lights, or a bottle holder, or take the wheels off to fix a puncture.
Moodle is open source software, so it definitely wants to be like a bicycle, and invite people to tinker if they are so inclined.
Now, I fully accept that not everyone wants to tinker. As it happens, I am a very keen cyclist. I ride my bike to work every day. When something goes wrong with it, however, I normally choose to take my bike to the shop and pay them to fix it, rather than fixing it myself.
That is not lack of knowledge. I have always known how to do some basic things, and recently my local bike shop offered me a free bicycle maintenance course. I did not have to accept their offer, but as it happens I did, and it was interesting. I now know how to do more things myself, at least in principle. I expect, however, that I will go on taking my bike into the shop most of the time because a their staff can do a better job than me at most repairs. It was still good for me to expand my knowledge. It was good that the bike shop shared their expertise.
Like the bike shop, the Moodle community should be helping people learn how to tinker with Moodle, if they are interested. There is certainly no compulsion on anyone to be interested, but the opportunity should be there.
So, just like you cannot draw a clear line between bicycle riders and bicycle mechanics, I think it is wrong to try to draw a line between Moodle users and Moodle developers. I think that people who are more expert at Moodle development should be generally encouraging other people to have a go, not with the expectation that they must all become developers, but with the hope that a few of them will.
There are some good examples of teachers who arrived at the Moodle community with only limited development knowledge, and who have gone on to make very useful contributions. Ones that spring to mind include Anthony Borrow, Pierre Pichet, Joseph Reseau and Jean-Michelle Vedrine. (I hope they don't mind me mentioning them by name here.)
As I say, I do not expect everyone to follow that path. But I think it is something that should be encouraged in those people who are interested, so I will go on making suggestions to people about how they might start tinkering with Moodle. I don't mind if such suggestions are ignored, but I believe that we are a community of educators, and so I will go on trying to share what I know about how to do Moodle development with anyone who will listen.