It’s also a good idea for a developer to actually contribute to Stack Overflow by asking questions of their own and providing answers to others’ questions. I’ve always wanted to do this, but felt VERY overwhelmed by the prospect. It seemed like every question already had an answer with a bazillion upvotes. Oh, and if the masses aren’t fond of your answer, you can get downvoted. No one wants to be downvoted! So, how could little, old Sarah contribute?
As part of my mission to get out of my own damn way, I decided to look for some SIMPLE questions on Stack and start there. I found that if you simply go to the homepage, you can filter by topic and the most recent questions show up at the top. If you’re paying attention, you can jump in and be one of the first few people to answer a question.
The point is, I had this big mental barrier in my head that was preventing me from a) doing something that could make me a better developer and b) putting myself in a position to a favorable candidate should I ever go for something full-time, or even a contract gig. Hiring folks look at things like Stack Overflow and GitHub and so on.
As with most things related to coding, the answer to overcoming Stack Overwhelm (as I have dubbed it!) is to break things down into smaller, more manageable goals. My goal now is to answer one question a day, on a topic in which I have a decent level of confidence. I know I won’t become a top contributor overnight, but you have to start somewhere, right?
I’ll let you know when the upvotes start rolling in 😉
Photo by rawpixel on Unsplash