I design motherboards for network devices; I keep the internet going.
Routes are inaccessible without access to them. The underlying machine states to check for access to a route is algorithmically similar to the other checking for user access.
It’s unfortunate so many are allowed to work in IT with cliff notes level awareness of how technology works.
The layers of indirection you work with are the knobs and buttons people like me choose. You merely obfuscate with vacuous jargon to serve your career goals.
Sysadmin, devops, platform eng all suffer from made up problems.
What’s IAM?
Access control.
What’s a firewall?
Access control.
What’s a route table?
Access control.
What are resource limits and reservations?
Access control.
Yet years of legacy solutions has us discussing all these things as if they are fundamentally different. User management comes wrapped in vacuous jargon. Network addressing schemes are completely design by the pocket protector committee (fuck off they can be wrapped in abstraction that is less obtuse jargon and more memorable/mnemonic).
There are no users, groups, or network routes in the machine. Devops is obtuse access control because a lot of companies can make money from insuring its obtuse access control.
Routes are inaccessible without access to them. The underlying machine states to check for access to a route is algorithmically similar to the other checking for user access.
It’s unfortunate so many are allowed to work in IT with cliff notes level awareness of how technology works.
The layers of indirection you work with are the knobs and buttons people like me choose. You merely obfuscate with vacuous jargon to serve your career goals.