This applies to any project, really. At my workplace, if someone refuses to let other teams look under the hood of a product, 95% of the time, it's because their code is absolute garbage, but their leaders didn't want to wait so they pushed it to prod and now it's up to some junior employee to fix all the shit that blows up in prod.
And just for closure, 5% of the time, it's because there actually is no product at all.
Man, I didn't agree with any of your comments before this one, but I could at least see your point of view, but this...
You can plug in anything you want here. Now, the engineers can give their opinions and estimates, but they can't decide it. The PM can. It's his job to weigh the risks and uncertainties and decide on the path forward.
You are either a PM yourself or are just making shit up to argue. The PM, at best should only be responsible for signing off on tech choices. If PMs were making decisions, then we would all be using Excel as an enterprise database, documentation tool, and version control.
I have a very similar setup, but I recently switched to using CasaOS on top of the DietPi. It comes with docker compose presets for all the arr apps, and also creates a homescreen with icons for all apps. I was doing this using a bunch of different services before, but CasaOS bundles it all together.
Love this. I haven't written any R code in years, but I do miss the simple and intuitive syntax of dplyr and the rest of the tidyverse. PRQL looks like it is built on the same philosophy. Can't wait for it to get fully integrated into dbt.
What thinking about the Roman Empire does to a mf