Yesterday was the most stressful day of my life.
I ran straight to the nearest restaurant, jumped on a table, and shouted the most important words I'd ever shouted:
"kapa NOW SUPPORTS SCIM PROVISIONING!"
The closest waiter frantically responded "But Emil, what does that mean?"
I then calmly explained that it means every Kapa customer can automatically provision and deprovision users through their identity provider.
"Oh, so like if I use Okta, and I hire an employee, they automatically have a Kapa account?"
"Yes!" I said to the surprisingly technical waiter.
Then, I stepped down, paid for everyone's meal, and set up a @kapa_ai assistant for the restaurant, just in case they ever launched an API portal and technical docs.
Did this happen? It could have.
But we DID actually launch SCIM provisioning, and you should really check it out.
Link is below.
Now, back to my stress-free week.
@forgebitz@paulg I don’t think system prompts are necessity bad, as long as they are open sourced, and people can contribute to them like like any other OSS, if grok is all about truth and transparency
Grok randomly blurting out opinions about white genocide in South Africa smells to me like the sort of buggy behavior you get from a recently applied patch. I sure hope it isn't. It would be really bad if widely used AIs got editorialized on the fly by those who controlled them.
In the past 200 days I've completed 93 sessions of hyperbaric oxygen therapy.
8,723 min / 145 hours
The results from the initial 60 sessions were the best I've seen from any therapy.
Excited to see what follow up measurements show on the continued usage.
The API and UX is terrible. The scope of K8s is too broad, it’s basically everything. Hence the complexity and bloated interface trying to cover all possible use cases. Every company chooses what subset they need and eventually creates their tooling/processes to work efficiently with it
@Alw3ys For me, I think it's just the management piece. K8 is really incredible.
The teams I've worked on have struggled with the time commitment DevOps takes, and K8 takes a lot.
Working to solve it, although the focus currently is on ECS:
trydeepspace.com
@thatdeepak ohh that's a good one, but isn't the whole point of Kubernetes than you can run it anywhere? if it's hard to run on-prem why choose it on the cloud the first place and not some cloud native solution? asking for a friend
@rauchg@bryan_johnson Hahaha. Build fitness in public! Show stats next time you go for a run or something, I believe apple health shows you a decent estimation of it
Different type of build you might be used to here, but here’s a year of consistent running.
1st it’s a year ago, 2nd one a couple weeks ago. Do the same with your company. Shit takes time to build