I think it boils down to: you can write what you want to write or you can write what people want to read. If you're lucky then they overlap.
Dev.to is a place for all developers, so if you're writing specialised stuff, you're not going to get a lot of views. If you can't crank out a lot of articles, you won't get a lot of views.
There's no magic sauce, people are just people. BASIC is as BASIC does ;)
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
My whole rambling article summarised in just 2 paragraphs! 😁
The key bit is "balance", that is why I suggested the "one for them, one for you" method, growth with substance is the aim!
There's no magic sauce, people are just people.
But this is the bit that often gets missed, people are complex as individuals, but as a crowd we are still dumb irrational beings. I would argues there is a magic sauce...you need to understand crowd mentality and the overall population for the overall strategy and the understand the individual for how you interact with them and your tone of voice etc.
Amazing comment, honestly this whole comment section has just blown my mind with some of the insights!
I think the thing I underestimate, that you mentioned, is interacting with people. If you want to keep people coming back it helps to make them feel welcome.
Accessibility First DevRel. I focus on ensuring content created, events held and company assets are as accessible as possible, for as many people as possible.
It is more than that, engaged readers are 100 times more valuable than passers by. Engaged readers are where the job opportunities, friendships, repeat readers and advocates come from.
I think it all boils down to how you look at the relationship.
I view it as a privilege if someone takes the time to read and then comment on my writing (time is valuable), so I will give them the time and respond whenever I can as it is just good manners!
So I suppose at this point I should say thank you for reading and commenting 😁
I think it boils down to: you can write what you want to write or you can write what people want to read. If you're lucky then they overlap.
Dev.to is a place for all developers, so if you're writing specialised stuff, you're not going to get a lot of views. If you can't crank out a lot of articles, you won't get a lot of views.
There's no magic sauce, people are just people. BASIC is as BASIC does ;)
My whole rambling article summarised in just 2 paragraphs! 😁
The key bit is "balance", that is why I suggested the "one for them, one for you" method, growth with substance is the aim!
But this is the bit that often gets missed, people are complex as individuals, but as a crowd we are still dumb irrational beings. I would argues there is a magic sauce...you need to understand crowd mentality and the overall population for the overall strategy and the understand the individual for how you interact with them and your tone of voice etc.
Amazing comment, honestly this whole comment section has just blown my mind with some of the insights!
I think the thing I underestimate, that you mentioned, is interacting with people. If you want to keep people coming back it helps to make them feel welcome.
It is more than that, engaged readers are 100 times more valuable than passers by. Engaged readers are where the job opportunities, friendships, repeat readers and advocates come from.
I think it all boils down to how you look at the relationship.
I view it as a privilege if someone takes the time to read and then comment on my writing (time is valuable), so I will give them the time and respond whenever I can as it is just good manners!
So I suppose at this point I should say thank you for reading and commenting 😁
😁 you're welcome. Thanks for the post.