Great question! In my experience with ruby on rails, the application runtime is so dynamic, that even unit tests may not be reliable if run outside the production image.
I think normally this isn't much of an issue because other automated/manual integration testing in the staging environments will catch any major problems, to your point.
Another example would be for browser testing via chromedriver. I've usually seen this implemented along side unit tests (i.e., prior to the build phase) but since it generally serves as an integration level test for many applications, this has lead to issues due to the testing and production environments being out of sync.
I think multi-layer Docker images are a compelling solution to this, but it's not usually how I've seen it implemented.
Instead, I've typically seen that test and prod environments are manually maintained. Sometimes these are two separate Dockerfiles or some shared CI environment managed by different teams.
I think it's common (and important!) to build your "production" image once and deploy it into a dev/staging environment first. This means there are no re-builds between deploys to each environment.
However, I think it's less common to run automated testing within the same Docker image you build and deploy to these environments.
This is challenging because you probably don't want to include any build/test related packages in your production image (or layer) but you still want some level of confidence that your CI and Prod environments are the same.
I have often see builds pass automated testing but fail after deployment because our production Dockerfile/layer was missing packages or shared libraries that were present in the CI environment.
Personally, I would like to see a markdown spec that eliminates parsing ambiguity by restricting the "edge-case" features that HTML is really much better at describing in a standard and structured way.
I think we could pick one way to handle emphasis, lists, and code blocks that covers a specific and predictable 80%.
Anything that becomes hard to describe without including additional notation to the grammar is probably best suited to be left as HTML, as was the intention behind markdown to begin with.
You can't bring up Feyerabend without mentioning Imre Lakatos. The "methodology of scientific research programmes" is another fun read that takes the matter of demarcation a bit more seriously than AM.
For example, Lakatos isn't satisfied with "anything goes" because it fails to consider the political and social consequences of being unable to recognize science from pseudoscience. For Lakatos, demarcation is necessary to maintain a "standard of objective honesty", and avoid falling into an "intellectual decay".
Overall, Lakatos is much less provocative than Feyerabend, but is equally invested in picking apart the historical nuances of scientific progress brought into question by Popper and Kuhn.
I recently picked up the Fellow Ode for myself. I'm very happy with it so far and it's working exactly as advertised. Quiet, consistent, and very fast.
Blink[1] is a really cool open source app that will give you a shell on iOS and allow you to SSH into another machine. You can install it yourself, or purchase from the App Store.
If you want to use another computer you own, rather than a server in the cloud, Tailscale[2] will let you easily connect when away from home.
The moka pot is super cool and I thought it made great coffee...until I discovered that I preferred almost every other possible brew method.
The moka pot is very hard to dial in and almost always burns the coffee. It requires care, focus, and attention. They're much more inconsistent than pour over and even the lever espresso machines I've used are less work.
I think moka pots are fun and worth experimenting with but I find it hard to believe people really love the results. But if you are always adding milk and sugar, then I can definitely see the appeal.
Arch is great, although I think fedora does a much better job at providing a no-nonsense Linux workstation and would make for a smoother transition from macOS.
You better believe it. This was exactly my experience as a TA in my College's computer science department from 2014-2018.
It's not incompetence though, as the article points out, we've moved beyond an intimate understanding of the filesystem being a prerequisite for using computers.
Using interactive browser based environments like jupyter notebooks have made needing to deal with files even less of an issue.
Whitespace is definitely a legitimate critique of python.
The fact that people have learned to live with it or just ignore it is pretty irrelevant in my opinion.
Significant whitespace means I can't copy+paste without introducing bugs or breaking the code. It means code formatting becomes more complex to automate. It's seriously the dumbest language feature to defend and should be pretty acceptable to admit was a mistake.
I agree that having whitespace sensitive scoping isn't a compelling enough reason in itself to avoid python, but it is hard for me to understand how python programmers insist on defending it as a great design choice that "improves readability". To me that indicates an inexperienced developer who is unfamiliar with the alternatives.
I feel similarly for people who reject (or say they hate) static types and compilers.
I use this with "three finger drag", and resizing at the window border hasn't been much of an issue for me.