Does the data community have any tips or advice for turning R code into a short article and working paper?
A bit about me. Over the past 4 years, I've written large internal audits and risk assessments for Fortune 10 companies using R Studio, but they cannot be shared to the public which limits my ability to showcase my data analysis skills on my portfolio. Since they're trapped behind NDAs, I only can share vague overview descriptions. I wanted to build up my portfolio by drafting working papers and articles for the public and government agencies to consume.
Long story short, I have a desire to become comfortable drafting R code and publish an analysis article alongside a parallel working paper that eventually will be submitted to a journal, and then repeat the process for a new project. Kinda like a LinkedIn article, substack article, and then submit the article to other publications like the Financial Times. All while drafting a working paper I have on github, R Studio CRAN, and my public portfolio.
However, I'm not sure if this process is the most industry standard method or a safe approach for repeating future papers. Idk if this article process would cause my working paper to be rejected. I've seen journals mention that the author cannot share the article to other publications (figures and tables) before submitting for peer review for copyright purposes, but they say sharing a working paper for feedback is acceptable if I source my articles within my working paper and final draft submission.
TLDR: I'm curious what process people in the data community go through when they create a custom graph and finish a working paper draft.
Do you draft articles for social media and online publications alongside a working paper?
Do you generally ignore research journals in your reporting due to length of peer review?
Any other tips or advice you may have before I begin converting my notes into an article and working paper?