You have a voice. One that should be heard. This is for you. This is geared toward the tech world, especially programming where the gatekeepers, trolls, and snarks rule the kingdom of online tech writing and LinkedIn posts. I have news for you, these are not the leaders of this domain. You are.

I run into so many brilliant people who can write but don’t. Maybe they have tried or witnessed the flaming trails of an idea shot down or imploded online by “experts” who write challenging comments that belittle the idea. Gatekeepers who feel threatened that their “brand” of tech is somehow diminished a bit by a good idea from a new writer. Then there are the snarks who hide behind a monitor and do what they do best, snark at any idea.

But you have a voice. One that is growing and maturing and needs to be heard. Public discussion is a good thing when done in the voice of encouragement and an eye for a good seed that needs nurturing. Constructive observation is not destructive, but the true elders need to come beside new voices and mentor them. We all need input.

In my world from which I am writing, I know where my strengths are as a writer and voice in the tech community. I am a top-level coder and database developer. I could flash my code and methods but I don’t. Shure when I read other folk’s posts I wonder why they did something a certain way, why they indent or loop in a particular fashion. Why did they do this or that, or even if I know a better way, the point is did I catch the “main thing” from the post? Did I understand the point behind it even if I disagree with a point or method presented? Was there something to take away and maybe apply to my own work so the “collective” code base is improved?

You have a voice. Even if it is not saying or writing anything. But I hope you write. We all know lots of things. We all are opinionated. I sure know I am. The key is that we can collectively build our knowledge together in an “iron sharpens iron” fashion. Sure there may be sparks. There will also be filtering of ideas and methods that may not make it to the finish line, but the process forges better ones that will. And with your voice, you will have a part in that process.

I am a senior developer. I certainly don’t want to trump the future by bashing new ideas with my past. Honestly, the past is history, not something I would want any new developer to have to live through. The new things bring fire to the community and it’s OK if the bringer of the fire stumbles a bit here and there.

You have a voice. Use it responsibly.