DEV Community

Discussion on: Junior Developers Should Start A Technical Blog Early In Their Career

rachelsoderberg profile image
Rachel Soderberg Author

Thank you for the comment! That's really exciting to be in your first year - get ready for an exciting and challenging road!

I think my biggest tip would be to write regularly to really see benefits. I keep myself on a weekly schedule and release a post every Friday, but it doesn't need to be that often. You could do once a month or however often suits you.
Also, don't be afraid to write things and keep them to yourself! Writing things out plays a big part in the learning process, especially if you have time to write it out by hand too.

And one last thing - don't take it too seriously! You're ultimately writing to help yourself learn and it shouldn't be miserable. I like to alternate technical and less-technical topics. One week I wrote about Rubber Duck Debugging and people showed me their ducks! :)

lautarolobo profile image
Lautaro Lobo

So glad you answered Rachel!

I have my next blog post already done, waiting for the date to be uploaded :D

I write a few ideas per week, my next topic is already there, and I hope to upload a new post every 15 days, I think is a realistic objective.

Also, I use that web page as a play ground! Adding Ruby here or there and working on tags and social buttons and so.

I'm heading to a Neural Networks workshop this Thursday, may be if I learn something new there I can write bout it, what do you think about writing about a talk, workshop, or event that you participate? I mean, you are writing about something that other people sayd, feels like a knowledge heist (?), do you think that is anything wrong in that?


Thread Thread
rachelsoderberg profile image
Rachel Soderberg Author • Edited on

Writing about experiences like meetups, talks, and conventions is a great topic for your blog! There's a very successful C++ podcast (cppcast) that has a large portion of their episodes based on the same thing. They talk about their favorite speakers, what they learned, and whatnot.

As for knowledge heist, as long as you aren't using someone's words as your own there's no fear of plageurism or stealing. Your goal is to learn and hopefully benefit someone else in the process (why you shared it), and sometimes the unique way you write something will make it click for someone else. If your article or a passage looks similar to someone else's, just be sure to give them credit. One of my posts is an update to another blogger's post from years before to account for changes in Visual Studio since then, and it's now become a six-part Salesforce series that I continue to build onto!

Happy writing, friend. I am excited to read your posts and especially look forward to anything you have to teach us about neural networks. I've always found that topic incredibly interesting!