Notwithstanding participants will have language differences, Many requests on the forum are close to being simply careless or illiterate. Lazy - or if we're being generous, you're tired and frustrated with the problem - but that doesn't communicate well!
.
If you prefer to work in a non-English group - no problem... You can post in International Forums, but to be honest, the languages & tools have primarily been developed in English, and to offer assistance - most of the members are fluent in English.
Now - to the careless / lazy part... !
If you can't string a sentence together - then you have no hope of writing software, which has strict rules of syntax and structure. Stop now.
How to make your request gather more meaningful responses...
If you're trying to develop a complex project in one piece - we may discuss at length, but rapid assistance can only occur if we understand what you're trying to achieve.
You'll benefit more if you break the code down to the least size that will still fail to do what you are expecting - then once it's fixed, you can plug it back in to the whole project.
This will also reinforce the benefits of planning and structuring your code. It doesn't get bigger in the chip - the compiler squashes most things down.
Don't ask us to read your mind. This has been posted many times - but if you just say 'it doesn't work', we can certainly agree with you - but that's about all. If we have no idea what you are expecting, or what it's doing wrong - then neither of us will learn anything - and many helpers will just 'walk away'.
Drawings and/or photos.
Many problems are caused by wiring problems or misunderstanding how devices should be connected.
Easy answer - take a clear photo of your actual project (not blurry fro the other side of the garden in darkness). A photo is only half the solution - it is a representation of 'how it has been built' - unless you changed it afterward!
You should have a diagram of what you intended to build before you started building - if not, then no wonder you have wiring problems - only experienced hackers can successfully 'make it up as they go' - and they also make plenty of errors!
This schematic or logical/block diagram should be large and clearly detailed enough to identify pins/ signals and devices. (Taken on this side of the garden in the light please!)
The first time you do it, you'll hate us, but when the project comes together you'll understand - and two years later, you'll remember 'why'.
In the meantime - it helps us enormously to understand where, why and how your journey is moving - and where it may be going off track.
There are hundreds of people here that want to help you - if you want to make the effort.
They will become sarcastic very quickly if you demand assistance without putting in your own 2c worth.
