DEV Community

loading...

Discussion on: Saying No in Development to Clients is Hard

Collapse
jeikabu profile image
jeikabu • Edited

"No" is the most powerful word there is.

It's the same whether you're a freelancer, work in outsourcing, deal with external partners, or even within the same company. Both inside and outside of development. If you're not ready to say "no" you're not prepared to say "yes".

I've never regretted saying "no", only "yes".

Collapse
madza profile image
Madza • Edited

This is some qoute-level material right here. Well said.

Collapse
adriantwarog profile image
Adrian Twarog Author

True words here! I know those feelings honestly!

Collapse
terkwood profile image
Felix Terkhorn

Wow. I want to be your friend but am afraid to ask πŸ˜‚

Collapse
adriantwarog profile image
Adrian Twarog Author

Hahhaa, saying yes can be just as hard as saying no, saying yes to friends, support, help. That's a good topic for another day!

Thread Thread
terkwood profile image
Felix Terkhorn

Yep. To be a little less facetious about my reply, this is genuinely good advice about saying No. I used to keep a spreadsheet which tracked my commitments, so that I would slow down on making them. I was able to keep up with my work, but without gaining more control over the time and expectations, I experienced too much stress.

For the most part, Mr. Cortisol isn't my buddy πŸ˜‰

Thanks for kicking off the discussion

Collapse
nirnaeth profile image
Monica

so much this.

I realized that for myself personally, but also for my team. time is finite, and attention is a precious commodity. something will got to give.

if you care about the quality of your work, it’s paramount to give things the importance and care they deserve.

this doesn’t mean to never change your mind, but to be careful because changing priorities, context, and adding work are all things that have a cost.