Just out of curiosity, what does the dev env look like? A set of VMs? K8s?
If k8s, then mirrord for teams can be useful for testing code locally against the dev env dependencies without having to containerize while also not breaking the shared env dependencies for others.
Great article, thanks for sharing, as a recovering high school teacher (5 years ago I moved into tech after reaching full burn out in education) I must admit that I fantasised about teaching at the higher education level thinking that a minimal amount of student buy-in was what was needed to have a fulfilling experience teaching. But it's interesting see that in your class, students who wanted to be there still struggle to engage in a meaningful way for the most part.
For me, the most difficult part of teaching was dealing with the broken feedback loops. It’s challenging to gauge your own progress and performance as a teacher and to identify which areas need improvement and what is actually working.
Is the cost shown only the prices incurred post plugin integration or is there a way to show retroactive costs by comparing k8s object creation dates for example?
There are two ways to store map tile data like OSM. One is as pre-rendered raster tiles (256x256 png images) and the other is as tiles of vector data that get rendered either on the fly by dedicate rendering middleware or rendered client side by the browser. Vector tiles are anywhere between 20-50% smaller that corresponding raster tiles. Raster tiles was the standard way of doing web maps up until a few years ago, when client side rendering in the browser became feasible and now most people use vector tiles.
Yeah going to full 20 requires about 2TB iirc, OSM doesn't host beyond level 19 anymore either to reduce traffic. 14 is around 10m per pixel, best you'll be able to make out on that is like a street. Not useful enough to bother with imho, even 19 leaves a lot to be desired up close.
Worth noting that these are vector tiles and not raster tiles, so zoom levels work slightly differently. Generally you don't need as high zoom level with vector tiles since it is much easier to 'zoom in' on vector data than on raster data. A vector zoom level of 14 stores the data with roughly 50cm precision which is good enough for most casual mapping uses.
We are working on one, not intending to fully substitute for helm, at least not in the short term. But adding to what helm lacks like easy version updates, dependency mgmt and easy customization.
Disclaimer: I work for the parent company