Company as Code
blog.42futures.com
Company as Code
1–10 of 135 posts
Re: Company as Code
#2I've used to do something like this, on a smaller scale and dubbed it "organization as code". As long as you have good enough providers for Terraform/Pulumi you can declaratively specify a lot of the interconnected stuff in a company.
I built this around GitHub as the indentity provider as my interest was declaratively defining repository access control, while also being able to use users public ssh keys to (re)provision services to get them access automatically.
Re: Company as Code
#3Re: Company as Code
#4A company is more than the function of it's org chart.
There's business description being uncaptured sporadically in every Slack message, watercooler moment and email. (two of those are much easier than the other).
If you boil someone's actual job down to a HR job spec and assume that will suffice... you'll produce both absurdly long HR job specs and still fail to capture the entirety of someone's role.
Re: Company as Code
#5Re: Company as Code
#6In the future, laying off half the company will be just one terraform apply away.
Fortunately AWS doesn't let you delete S3 buckets with files in them without emptying them first...
Re: Company as Code
#7Re: Company as Code
#8Re: Company as Code
#9This is not a bad idea but this person basically reinvented LDAP. Everything he wanted to do is already in LDAP, much already in Active Directory.
Re: Company as Code
#10Once I had to go through a security audit at a job I had. Part of it was to show managing secret keys and who had access to them. And then I realized that the list of people who had access to one key was different than the list of the code owners of the service I was looking at, which was yet different than the list of the administrators of that service. 3 different sources of truth about ownership, all in code, all out of sync.