📝restricted stock units: the hidden trap
🔗 jacobbednarz.com/post/restric...
RSUs can be great but not without intentional effort. don't blindly step into them, doing nothing in acceptance is riskier than declining!
📝 skip the hype, sell the shovel
🔗 jacobbednarz.com/skip-the-hyp...
📝 what emperor penguins taught me about building high performing teams
🔗 jacobbednarz.com/what-emperor...
after 6 years, today is my last day at @cloudflare.
from building the edge control plane to maintaining the SDK ecosystem, it’s been a wild, rewarding experience. grateful for the amazing humans who came along for the ride.
at it takes a village to pull these sorts of things off so big thanks to everyone who kicked the tyres, slung code or contributed in other ways ❤️ we made it and it's only going to get better.
and finally, a bit more deep in the code but we eliminated terraform-plugin-sdk entirely (no more unset/true/false bugs to chase!) _and_ made the state handling simpler with marshal/unmarshal instead of d.Set() calls riddled everywhere that inevitably get forgotten.
with the provider now automated, tools like cf-terraforming can also be more dynamic, automated and no longer have the broad constraints we previously encountered because of the API + provider mismatch.
out of the box, we support 95%+ of resource types to generate.
attribute coverage is now on par with the libraries and API docs -- a unified experience! no more wondering when that pesky attribute you want will be available after being documented.
v4 of the provider had 19 datasources and 139 resources.
v5 of the provider has 288 datasources and 174 resources.
the resource count is about 🚀 as the internal teams validate and onboard more compatible endpoints.
at the beginning of this journey, we had 1200 documented endpoints. that is now over 1500 and increasing. more documented endpoints means better integrations and customisation options for our tooling (both internal and external)
don't get me wrong, as the primary maintainer, this is SUPER nice to finally have but my favourite things are actually the byproducts of this ship.
we've just released terraform-provider-cloudflare v5 ⭐ 🚀
just like the libraries and API documentation, the provider is now automatically generated using the OpenAPI schemas as the source of truth.
🧵
onlyfans but where you pay me to look in my tool collection.
i'm slightly biased but developers.cloudflare.com/analytics/an... is probably the most important part to understand the indexing/trade offs.
let me know if you get stuck or have different use cases (jb@cloudflare.com) and i'll help out where i can.
