Never trust the network in any circumstance. If you start from that basis then life becomes easier.
Google has a good approach to this: https://cloud.google.com/beyondcorp
EDIT:
I’d like to add a tangential rant about companies still using shit like IP AllowLists and VPNs. They’re just implementing eggshell security.
I actually disagree. I only know a little of Crowdstrike internals but they’re a company that is trying to do the whole DevOps/agile bullshit the right way. Unfortunately they’ve undermined the practice for the rest of us working for dinosaurs trying to catch up.
Crowdstrike’s problem wasn’t a quality escape; that’ll always happen eventually. Their problem was with their rollout processes.
There shouldn’t have been a circumstance where the same code got delivered worldwide in the course of a day. If you were sane you’d canary it at first and exponentially increase rollout from thereon. Any initial error should have meant a halt in further deployments.
Canary isn’t the only way to solve it, by the way. Just an easy fix in this case.
Unfortunately what is likely to happen is that they’ll find the poor engineer that made the commit that led to this and fire them as a scapegoat, instead of inspecting the culture and processes that allowed it to happen and fixing those.
People fuck up and make mistakes. If you don’t expect that in your business you’re doing it wrong. This is not to say you shouldn’t trust people; if they work at your company you should assume they are competent and have good intent. The guard rails are there to prevent mistakes, not bad/incompetent actors. It just so happens they often catch the latter.
At the cost of leg room.
Just beware of their reclamation policy:
I’m curious as to thoughts regarding documenting intent which cross over with what in my opinion.
Regarding self documenting: I agree, but I also think that means potentially using 5 lines when 1 would do if it makes maintenance more straightforward. This crazy perl one liner makes perfect sense today but not in 3 years.
Thanks for taking the time to respond.
I appreciate the info, but I am not a patient man. :)
Where on earth are you buying HP Mini machines for so cheap? Even the older gen seem to be 5 times as expensive as your estimate.
If the cast iron is well seasoned you’re fine.
The acid in the tomato will attack the coating you’ve developed but if you use it and season it regularly there is nothing to worry about.
The great thing about cast iron is even if you “wreck it” it’s pretty much always possible to fix.
As other comments have alluded to, a sharpening stone is a far better investment and only takes a half hour to learn.
Even if you do a bad job it’ll likely be a better result and better for your knives. Most sharpeners absolutely destroy knives and take far too much material off.
1000 grit is a good place to start.
They’re not more effective. They might assist with speed of absorption but that’s it.