Am I the only one that who is forced to implement some funcionality that I know that wont work only to prove to the client that actually wont work as I predicted?

And then implement how I suggested at the begining?

Everyones a developer.

I tell my objections and what I think will happen, and that I will be billing them if they want to change it.

Usually I can convince them not to do it. Some clients are too stubborn and have to learn the hard way (through their wallet).

@morgh It's true. But in my case I can't convince them. I think is a age problem because I am only 22 years old but already have 6 years experience. They may think I am a noob who doesn't know what is talking about.

@Shadow117 Age can definitely be a factor. In my experience, some clients just suck.

Regardless of age: if you can impress on them that you're the expert, and know what you're doing. Your chances of convincing them will go up.

What I like to is meticulously email the client every step of the way. Every task/requirement is on trello. Every change, or deviation from any agreed task I will email them with a description why it's being changed (along with a bill if necessary). After a while most clients begun to trust my judgement because they notice that I think more about these things than they do, and am approaching it from multiple perspectives.

Just don't get hung up on being right. Or proving that you were right. Be a pro.

At the end of the day the client is always right (they have the money). If you can't convince the client of your recommendation. You either suck it up and finish the job or stop working for them.

@morgh thank you for the advice. I will put your wise words to action.

Good luck man. Hope to see some good news from you here too :)