An opinionated list of Python frameworks, libraries, tools, and resources
I'll be honest before I started, I think I expected blockchain data to feel exotic. Like there'd be some kind of ceremony to accessing it. What I got instead was a JSON RPC endpoint. You call it, it talks back. That was the first surprise: how boring the infrastructure felt in the best possible way. It's just a database you can ask questions to. The "public ledger" framing stopped being an abstrac
What if your Kubernetes cluster simply refused to run unsigned images? I spent some time experimenting with enforcing image provenance in a small Kubernetes setup using MicroK8s. The idea was simple: Only container images with valid cryptographic signatures are allowed to run in the cluster. For this I used: GitLab CI/CD (build + signing pipeline) Cosign / Sigstore (image signing) Kyverno (admissi
I'm doing the 100 Days of Solana challenge by MLH, and Week 2 just changed how I think about blockchain data entirely. Week 1 was about identity — generating keypairs, understanding wallets, getting devnet SOL. That part felt familiar, like setting up a dev environment. Week 2 was different. Week 2 was about reading the chain — and that's where the mental model shift actually happened. I expected
I’ve been exploring Solana for the past few days and a few things stood out pretty quickly No traditional database everything revolves around accounts The biggest shift so far has been adjusting to the accounts model. Coming from a typical backend mindset it forces you to think differently about how data is stored who owns it and how state changes over time I also built a small dashboard in the
Been spending the last ~10 days getting hands-on with Solana as part of a hackathon. Went in expecting things to feel completely different from what I’m used to. It wasn’t as far off as I thought. What I’ve Done So Far Generated a keypair + airdropped devnet SOL Created a wallet and checked balance programmatically Understood SOL vs lamports Connected a browser wallet Read on-chain data (accounts,
Most teams I have worked with have one auth test in their suite. It looks like this: test('valid token verifies', () => { const token = signSync({ sub: 'user-1', aud: 'api://backend' }, secret); const result = verify(token, options); expect(result.valid).toBe(true); }); That test is fine. It is also a smoke test, not a regression suite. It catches the case where verification is completely b
The on-call alert at 02:14 said auth_5xx_rate spiked from 0.01 to 31.4. Not a deploy window. Not a traffic spike. Just thirty-one percent of authenticated requests failing for ~four minutes, then back to baseline. The cause was a JWKS rotation on the issuer side. New keys came in. Old keys went out. Caches in our service didn't refresh fast enough. Tokens signed with the new key were rejected beca