Startups and tech enthusiast. Loves building products that make your life easier. Currently, building Qovery - a platform revolutionizing application deployments in the cloud.
Good point. Sure, this approach may lead to me writing longer & higher quality articles.
I'm wondering how to make the process public and transparent. Maybe I'll push drafts of my articles to a public Github repo. It's gonna be easy to track the history of my writings there :)
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 isn't a bad idea, but just consider that your drafts may contain some stuff that you prefer not to go public (as you have mis phrased something just to get the idea down and it could be potentially inflammatory - it all depends very much on what you are writing about, if it is just purely about code and development you will be fine, straying into politics, religion, gender issues etc...probably best not to have a public record while you formulate thoughts and ideas and haven't had chance to check your writing cannot be misinterpreted!)
I mean, if you want a rough and ready way to do it just write on dev.to - at the end of one article point to a page for the next article (saved as draft as you then have a public URL) and then people can follow along that way.
If I were doing this challenge, I perhaps would dedicate the first few articles to building a custom blog that allows people to see when you worked on what. A fun way to have loads to write about initially and a fun way to be transparent!
There is no reason these couldn't be short posts (what framework you chose for back-end, what (if any) you chose for the front-end, libraries you explored for syntax highlighting, including a daily word count graph etc.) obviously it all depends on your experience levels and stuff as to how you frame those articles.
Anyway just a couple of ideas, I hope this goes well for you as a fellow "newbie to writing" who hasn't quite nailed down a schedule (but I am close 😋).
Startups and tech enthusiast. Loves building products that make your life easier. Currently, building Qovery - a platform revolutionizing application deployments in the cloud.
I am writing using roamresearch.com app. I'll not be writing about coding exclusively. I'll be writing about whatever I feel like to write about, about things I'm currently doing/learning, about things I think may be helpful to others. I don't really care about numbers - I'll be writing for myself, but at the same time with the intention to give as much value to the readers as I can.
Some of the posts may be about fetchings CPU usage metrics from Pods in Kubernetes and others about productivity tips, biohacking, philosophy or whatever. I'm pretty geeky, so the posts are going to be connected to the software industry no matter how hard I'd try to avoid it :P
Probably I'll write privately in the Roam app and publish only 'ready' drafts to the public.
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.
I know you want to share every detail with people but at the end of the day if each week you produce 3500 words or more it doesn't matter how you got there (one sitting or several days). It requires very similar effort levels and you still have "your money where your mouth is" to keep you on track!
Bear in mind that 3500 words per week is the same as writing 2 novels (180k words!), so nobody is going to begrudge a tiny bit of "slack" in your original idea of daily writing for if you need a break, so I think weekly updates is more than enough.
Before you set your goal in stone, just bear in mind the time it takes to research subjects, that is the bit I see a lot of people forgetting!
Startups and tech enthusiast. Loves building products that make your life easier. Currently, building Qovery - a platform revolutionizing application deployments in the cloud.
You are completely right that research takes time. I'm currently exploring the Zettelkasten method to combine consuming content with writing. You may find this short article useful shime.sh/use-zettelkasten-to-write... or read "How to take smart notes" by S. Ahrens if you are interested in this topic.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Good point. Sure, this approach may lead to me writing longer & higher quality articles.
I'm wondering how to make the process public and transparent. Maybe I'll push drafts of my articles to a public Github repo. It's gonna be easy to track the history of my writings there :)
It isn't a bad idea, but just consider that your drafts may contain some stuff that you prefer not to go public (as you have mis phrased something just to get the idea down and it could be potentially inflammatory - it all depends very much on what you are writing about, if it is just purely about code and development you will be fine, straying into politics, religion, gender issues etc...probably best not to have a public record while you formulate thoughts and ideas and haven't had chance to check your writing cannot be misinterpreted!)
I mean, if you want a rough and ready way to do it just write on dev.to - at the end of one article point to a page for the next article (saved as draft as you then have a public URL) and then people can follow along that way.
If I were doing this challenge, I perhaps would dedicate the first few articles to building a custom blog that allows people to see when you worked on what. A fun way to have loads to write about initially and a fun way to be transparent!
There is no reason these couldn't be short posts (what framework you chose for back-end, what (if any) you chose for the front-end, libraries you explored for syntax highlighting, including a daily word count graph etc.) obviously it all depends on your experience levels and stuff as to how you frame those articles.
Anyway just a couple of ideas, I hope this goes well for you as a fellow "newbie to writing" who hasn't quite nailed down a schedule (but I am close 😋).
I am writing using roamresearch.com app. I'll not be writing about coding exclusively. I'll be writing about whatever I feel like to write about, about things I'm currently doing/learning, about things I think may be helpful to others. I don't really care about numbers - I'll be writing for myself, but at the same time with the intention to give as much value to the readers as I can.
Some of the posts may be about fetchings CPU usage metrics from Pods in Kubernetes and others about productivity tips, biohacking, philosophy or whatever. I'm pretty geeky, so the posts are going to be connected to the software industry no matter how hard I'd try to avoid it :P
Probably I'll write privately in the Roam app and publish only 'ready' drafts to the public.
I think that the smart way to do it.
I know you want to share every detail with people but at the end of the day if each week you produce 3500 words or more it doesn't matter how you got there (one sitting or several days). It requires very similar effort levels and you still have "your money where your mouth is" to keep you on track!
Bear in mind that 3500 words per week is the same as writing 2 novels (180k words!), so nobody is going to begrudge a tiny bit of "slack" in your original idea of daily writing for if you need a break, so I think weekly updates is more than enough.
Before you set your goal in stone, just bear in mind the time it takes to research subjects, that is the bit I see a lot of people forgetting!
You are completely right that research takes time. I'm currently exploring the Zettelkasten method to combine consuming content with writing. You may find this short article useful shime.sh/use-zettelkasten-to-write... or read "How to take smart notes" by S. Ahrens if you are interested in this topic.