HN user

zhala

24 karma
Posts0
Comments13
View on HN
No posts found.

We do this regularly in production. We do biweekly container rebuilds, many running alpine and installing version unpinned packages. So far very few (if any) actual issues with that. We do of course do smoketests prior to promoting to production.

I've seen these studies before and done some testing of my own and found this to be true to some degree. I've used PMSA003I and BME688 sensors to check for particulate and VOC's. I didn't notice any significant increase in PM1 or PM2.5 (which is probably to be expected since the particles emitted are probably <1um and lower than I can detect). I did see some increase in VOC's but nothing alarmingly high from baseline. Roughly equivalent to lighting a candle.

As someone who did IT at a public transit agency for a medium sized city briefly, this is all pretty accurate and similar at most public transit agencies. Even brand new busses are still using old hardware under the hood that requires special deutsch to serial cables that require windows 7 machines to interface.

Likewise all the software that runs transit agencies is extremely dated and heavy.

"Anything under 10 minutes is good" for running the CI pipeline (not true anywhere I've been at Google) or "The steps should be 'do a git clone...'" (also not true at Google).

Are these both true/common in the industry? At least where I work CI takes at most a couple minutes (depending on what all you're doing in your docker file) and likewise you can just pull and run CI locally on your machine for nearly any repo.