DEV Community

Discussion on: Should Developers Put Themselves Out There?

Collapse
 
jeremyf profile image
Jeremy Friesen

I try to steer clear of generalizations but instead want to think about consequences. Putting yourself out there comes with a cost; as does not "putting yourself out there".

Putting yourself out there takes time and energy; you need to assess if you have that to spare. Being "out there" is perhaps a form of teaching; which is a great way to learn a subject; it's the process of synthesis and restating that helps cement the learning.

By not putting yourself out there, you may be conserving time and energy. But you may be less visible for future opportunities. Further, you may be closing one channel for synthesizing and learning, so my hope is you have a game plan.

I leave two aphorisms that are contradictory:

Better to remain silent and be thought a fool than to speak and to remove all doubt.

And

If you speak you die, if you do not speak you die, so speak and die.

There is no right answer.

Collapse
 
adiatiayu profile image
Ayu Adiati

That's interesting, Jeremy!
But you're right. There is no right answer.
Sometimes pushing ourselves out of our comfort zone would do no harm I guess.
We can always pivot if it's not for us :)

Collapse
 
jeremyf profile image
Jeremy Friesen

Your circle of comfort is never static, it is either growing or contracting. And to grow that space is done by being open to and acting on new opportunities.

I hope folks can give a go at "putting themselves out there." For me, it has lead to tremendous and rewarding growth.

Thread Thread
 
adiatiayu profile image
Ayu Adiati

Can't agree more, Jeremy!
Had I not stepped out of my comfort zone, I never learn and grow and experience the rewards! 😄