Sometimes, being a developer, your job consists of just saying no. No to a feature, a client or your boss requested, no to a new project or no to a developer who is applying for a job.
For me writing code is easy. Sometimes I need to sleep over a problem, but usually I find a solution to a problem quite fast. But dealing with people is a hard thing to do. You have sometimes to do hard decisions.
I just want to give you some examples, where saying no saved my ass in the last two years and where saying no would have been a better approach.
Telling a to unexperienced developer that, he is still not ready is hard. Specially, when it's hard to find new people anyway. It took me a lot of time to find another co-worker, now I have someone, who wrote productive code after just after two weeks in the new job.
My boss asked me to not focus so much on the admin-interface of the online-shop. I refused to do a sloppy job. Now I have something, were I can tell everybody in the company to dispatch the orders with just a two minutes introduction on what they have to do.
My other boss asked me to change the color-schema of an online-shop to "anthracite". On a screen there is not such color. It would have slowed down the render-times, if I used images. So I refused to do so and customers are satisfied with the look and render-times.
A thing I did not clearly refused was to do a project with someone for a hourly monetary compensation. I told my boss, that this would just lead to a lot of emails which requests to change a lot of "small things". Always accompanied by the word "just". Here I instantly regretted not to stayed firm in my position to refuse to do this project for a fix price.
Especially when you are in an environment where you have to deal with non-technical-staff and employers, your role should be more than, "the one who just codes". You have technical insides and experiences, that maybe no-one else has. Use it for good.
What have been your experiences? What have been your success-stories and biggest fails?