Closes #37 cross company development (#81)

* draft post:
cross company development

* draft post

* update wordlist

* fixed image size. Also for default admiral app

* fixed post

* added code chunk

* Update posts/2023-07-20_cross_company_dev/cross_industry_dev.qmd

* Update posts/2023-07-20_cross_company_dev/cross_industry_dev.qmd

* Update inst/WORDLIST.txt

* fixed link

* Implemented comments from Ross

---------

Co-authored-by: Kangjie Zhang <47867131+kaz462@users.noreply.github.com>

inst/WORDLIST.txt

@@ -268,3 +268,4 @@ Rimler
 siloed
 stefanthoma
 useR
+admiralroche

posts/2023-07-20_cross_company_dev/cross_industry_dev.qmd

@@ -39,8 +39,8 @@ The move toward cross-industry collaboration when developing clinical reporting
 As the industry moves toward new (to them) programming languages, fit-for-purpose tools need(ed) to be developed.
 The realization that siloed solutions -- in an area where competitiveness does not benefit patients -- are simply resource hungry ways to solve the same problem in parallel provided a great argument for a shift toward collaborations. 
 
-Such cross-industry collaborations gave rise to the pharmaverse, an opinionated collection of R packages designed to solve clinical reporting in R.
-[{admiral}](https://github.com/pharmaverse/admiral), the project that I work on, is part of the [pharmaverse](https://pharmaverse.github.io/admiraldev/devel/index.html) and covers the creation of ADaM data sets (CDISC standard data).
+Such cross-industry collaborations gave rise to the pharmaverse, a curated collection of R packages designed to solve clinical reporting in R.
+[{admiral}](https://github.com/pharmaverse/admiral), the project that I work on, is part of the [pharmaverse](https://pharmaverse.org/) and covers the creation of ADaM data sets (CDISC standard data).
 These data sets are subsequently used to produce tables, listings, and graphs and are usually part of the submission package for regulators.  
 <!-- You can read about the inception of [{admiral}](https://github.com/pharmaverse/admiral) in [this recent blog post by ...](). -->
 
@@ -52,7 +52,7 @@ When creating an open source package in an industry where currently there is a l
 No, I don't mean: Move fast and break things. 
 I mean: Communicate! Get people on board! 
 We aimed [{admiral}](https://github.com/pharmaverse/admiral) to be **the** package for ADaM creation even before deciding to create the package together with GSK. 
-By being transparent about our endeavor, e.g. Thomas Neitmann (then at Roche) posting on LinkedIn, we managed to connect with Micheal Rimler from GSK and soon realized that we were dealing with the exact same challenge at both companies, and that a collaborative effort would improve the final product while reducing individual efforts.
+By being transparent about our endeavor, e.g. Thomas Neitmann (then at Roche) posting on LinkedIn, we managed to connect with Michael Rimler from GSK and soon realized that we were dealing with the exact same challenge at both companies, and that a collaborative effort would improve the final product while reducing individual efforts.
 A working prototype of [{admiral}](https://github.com/pharmaverse/admiral) was to be created by GSK and Roche within six months, and would then be open sourced. 
 In our effort to communicate openly, we informed statistical programmers from over 20 companies about the [{admiral}](https://github.com/pharmaverse/admiral) project and invited them to try it out and provide feedback once released. 
 In the end, we received over 500 comments from over 50 programmers. 
@@ -76,8 +76,10 @@ In that spirit, its permissive [apache 2.0 licence](https://www.apache.org/licen
 
   - Having this package backed by Roche and GSK ensures (as far as this is ever possible) funding for properly maintaining the packages. This is crucial, as a package is rarely **finished**. 
 
-Up to now, experts from many more companies have joined [{admiral}](https://github.com/pharmaverse/admiral) or one of its therapeutic area specific package-extensions, inspiring even more trust into its reliability.
-If you would like to learn more about licenses for open source projects in the clinical reporting world please check out the [recent E2E guidance on open source license](https://phuse-org.github.io/E2E-OS-Guidance/) 
+
+  - Up to now, experts from many more companies have joined [{admiral}](https://github.com/pharmaverse/admiral) or one of its therapeutic area specific package-extensions, inspiring even more trust into its reliability.
+
+If you would like to learn more about licenses for open source projects in the clinical reporting world please check out the [recent PHUSE E2E Guidance on open source license](https://phuse-org.github.io/E2E-OS-Guidance/) 
 
 ## Development workflow
 
@@ -105,7 +107,8 @@ Just last February we organised the [{admiral}](https://github.com/pharmaverse/a
 
 For Roche, cross-industry package development work out in their favor: They get access to software created by specialists and users from across the industry but paying only a fraction of the developmental costs. 
 Of course, they don't have total developmental control but they do get a seat at the table. 
-Any gaps between the open source [{admiral}](https://github.com/pharmaverse/admiral) package and the proprietary Roche workflow were bridged by the internal {admiralRoche} package. 
+Any gaps between the open source [{admiral}](https://github.com/pharmaverse/admiral) package and the proprietary Roche workflow were bridged by the internal {admiralroche} package. 
+
 
 The switch towards a more language agnostic platform, and open source languages specifically, opens the door to a broad population of university graduates with diverse backgrounds.
 I personally would not have considered this position five years ago due to a misalignment of skills and job requirements.