The dirtiest management trick I know is get a manager to make a promise to employees, fire the manager, and then refuse to honor the promise, because the organization is not accountable for honoring promises made by its representatives (which is bullshit but we haven’t cracked how to push back).
This is probably a huge reasoning error, but wouldn’t you “expand away” with the expanding away part of the universe at the same rate, sort of riding along with the expansion given that c is the same in the point of reference (the expanding away faster than c part)?
n.b. I obviously lack the vocubulary to communicate properly about this, help needed!
Perhaps anecdotal, but I have never got any negative response on answering “no, we do not enforce password rotation as this is against NIST recommendations.”
Unfortunately that's not how it plays out in most large organizations, which have separate network, hypervisor, security, etc., teams. Everyone works off a playbook, whose origins are usually lost in time and space.
If you want them to change the playbook, it'll involve some schlub having to run from pillar to post between those organizations, trying to get everyone to agree to a change to this policy, and you can bet he or she is not paid or motivated to do this. If another vendor comes along who will go with the flow, they get the sale.
Every organization I’ve worked for has been able to change policies at will. I’ve written them for half a dozen. I don’t particularly like writing policies but if you do you’ll be able to remove the absurd and broken parts.
You don't get to pencil in your own policy when the organization must conform to standardized compliance rules (such as HITRUST for health related companies) that mandate certain policies, or risk losing customers who look for compliance to these rules. These guidelines can take years to catch up to modern best practice.
If you - or others here - are interested I can spend some time to clean-up my own "boilerplate" a bit.
It's using Golang + Chi + Templ, uses SQLite as its database and has a multi-tenant-multi-db setup by default (i.e. 1 master database for user/tenant management, and "stem-data", 1 sqlite database per tenant), and uses passkeys for authentication. I'm using some HTMX + Hyperscript + a really small amount of plain-js for passkeys in the apps themselves.
I reckon that switching out Chi for Fiber - for the boilerplate only - would take about 90 minutes.
Edit: Forgot to include TailwindCSS. So for completeness sake.
Remember the importance of checklists in the "grand scheme of things". It helps maintain proper "authority" during operation and makes sure you don't forget things. If you don't write it down and check it, someone, at a certain moment will forget something.
Also, the "Aviate, navigate, communicate" axiom (as mentioned by author) is really helpful if you're trying to setup incident/crisis response structures. You basically get your guiding principles for free from an industry that has 100+ years of experience in dealing with crisises. It's something I teach during every incident/crisis response workshop.
edit: Although it's not aviation specific, and a little light on the science, "The Checklist Manifesto" by A. Gawande is a nice introduction into using (and making) checklists.
And the value of good documentation, and actually reading that documentation as well as making sure the documentation is indexed and quick to peruse in a situation where you don't have time to waste.
Yes, I no longer have the business. It got harder and harder to compete with larger players as the market begin to attract more players. I sold of the business to a larger company (just contracts and not tech).
Getting a visa is definitely easier than getting a passport. My advise is to look for a good employer, and have a relocation agency take care of the rest. They know what to do and know the intimacies of - e.g. - tax benefits you might be eligible for.
(n.b. Not immigration specialists but married to expat tax advisor)
The evolution of the setup is the thing I'm aiming for. Right now it's plain, simple stupid. But if the progression of challenges is the same this year when compared to 2019, then reusability will come in handy, and a more involved setup might be appropriate. ;-)
edit: thanks for pointing out the erred link, updated.
