This distinction is a more useful one that the article made. I love dockerfiles and immutability, but there are good cases for mutable containers, too.
You can also do some neat things with "--ephemeral" and "--volatile" to basically overlay the image (or a subset) with tmpfs; any changes to those overlays will be lost when the container is brought down. The specific mount points can be controlled in greater detail via "--tmpfs" and "--overlay".
Containers already are mutable on all popular runtimes. “Immutability” comes from destroying and recreating them from their image, but there’s nothing forcing you to delete/recreate them, and indeed that’s not even the default behavior.
S-57 charts are a derivative product manually authored based on hydrographic survey data. They differ from the raw data a little because they include extra metadata and hand-tweaked geometry to reflect safety issues.
To my knowledge S-100 is simply an updated “container” for ENC data and is replacing S-57. So it’s not necessarily related to this effort except that the new format may support gridded bathymetry data being encoded?
The two are mostly unrelated, IHO members are supporting seabed 2030 but the new data formats coming at the same time is more of a coincidence than anything else
Although S-101 is the updated ENC standard for S-100 the new S-102 standard will enable the visualisation of processed bathymetric data by mariners, biggest benefits will be more granular no-go areas
asciidoc is my favourite too, thanks to Asciidoctor. I agree, asciidoc hits the sweet spots as a format. Been frustrated by the tooling lately though. I can see the huge effort put into Asciidoctor, and am thankful for it, but there are still big downsides i.e. no semantic html 5 output, difficult (or at least more difficult than necessary) integration with image generators, heavyweight (only ruby dependency on my entire machine). I imagine this just needs more time and resources put to it, as all these issues (except the ruby one) are open on GitHub.
I have no expertise, but this is my sleep. It turns out I have sleep apnea. I can "sleep" for 8 hours, but it does very little good. With apnea, you wake up as much as a few times an hour, getting very little REM. It took me years to consider apnea because I'm thin and somewhat fit. But all sorts can have it.
Definitely recommend going to a sleep clinic and see a sleep specialist if you have untreated sleep apnea. I have friends with sleep apnea who managed to resolve their insomnia by using cpap machines (although it might take a while to get used to it). In some instances, surgery might help too.
When I played hockey, I used to wrap my wrists with tape. If I left the tape on too long I would always get this itchy rash. I believe the technical term is, " irritant contact dermatitis"
I have to disagree with other responses. I think you could make a career of this for the same reason management consultants can.
You could swoop in and "fix" some stuff and then leave the in-house team not understanding what you've done. That sounds profitable. You might even get called back to fix things a second time.
As with management consulting, I think it would at the system level tend to do more harm than good, even if you do good work and get paid well for it. I agree strongly with feoren that the code needs to reflect the in-house developers' mental models of the domain or everything will fall apart. If you fix things and then give them a bunch of processes and coding standards to follow, they will not do well and you will be thought of as some clueless architecture astronaut by them. But profitably.
reply