When to say NO to web development projects
No is a very powerful word to say and we developers don't say it enough
As developers we like to please and learn new skills and this often leads us to say 'YES' which isn't always the best approach.
Today I'm going to talk about when it's best to say NO and walk away from projects and opportunities.
Reasons why Web Developers should say no
- You can avoid learning technologies that you're not interested in.
- You will work happliy in your niche and comfort zone without additional distractions.
- Clients that don't pay on time and bad client relations can be avoided.
- Features are not rushed into production and code is well tested.
- Coding standards are upheld and respected.
Tips for saying no
- Look for a compromise. There is normally a middle grounds that you can find between you and the other person.
- Don't let it get too far. Putting a stop to things quickly is often eaiser then backing out of a bad desicion.
- Keep to the mission and to your principles. If you feel uncomfortable with the situation or if the decisions go against an argreed project mission then perhaps it's best to reevaluate your position.
- Speak up. Don't suffer in silance. If you're not happy then say something.
- Listen. Make sure you understand the situation, the needs of the client and the current status quo before making a desicion.
- Be respectful. Just beacuse you don't want to agree to something doesn't mean that someone else will snap to the chance.