OTOH in a pipeline, you're mutating/summarising/joining a data frame, and it's really difficult to look at it and keep track of what state the data is in. I try my best to write in a way that you understand the state of the data (hence the tables I spread throughout the post), but I do acknowledge it can be inscrutable.
But it was kind of wild at that point there were still company mailing lists where these old heads would argue about iOS internals and flame each other in front of the whole company.
We still had a non-web bug tracking system while I was there. It was an interesting era! The product I worked on did have a web interface as essentially its only UI. We used Java, at some point we used MS Visual J++, and this was before JSPs existed. We used some proprietary templating engine to generate HTML.
Edit: just found this disclaimer in the article:
> I’ll show the generating R code, with a liberal sprinking of comments so it’s hopefully not too inscrutable.
Doesn't come out the gate and say who wrote the comments but ostensibly OP is a new grad / junior, the commenting style is on-brand.
I use Rmarkdown, so the code that's presented is also the same code that 'generates' the data/tables/graphs (source: https://github.com/gregfoletta/articles.foletta.org/blob/pro...).