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".
My goal is to make useful and helpful advice and content that will help others!
New content everyday, please leave feedback if there is something you want to see!
Software producer specialized in data and distributed systems.
Past: tech lead for Disney+ DRM (NYC), consulting and contracting (NYC), startup scene, Salesforce, full-time lab staff.
My goal is to make useful and helpful advice and content that will help others!
New content everyday, please leave feedback if there is something you want to see!
Software producer specialized in data and distributed systems.
Past: tech lead for Disney+ DRM (NYC), consulting and contracting (NYC), startup scene, Salesforce, full-time lab staff.
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 π
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.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
"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".
This is some qoute-level material right here. Well said.
True words here! I know those feelings honestly!
Wow. I want to be your friend but am afraid to ask π
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!
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
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.