<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://lucassaldanha.github.io/</id><title>Lucas Saldanha</title><subtitle>Personal blog of Lucas Saldanha.</subtitle> <updated>2026-05-31T23:10:21+12:00</updated> <author> <name>Lucas Saldanha</name> <uri>https://lucassaldanha.github.io/</uri> </author><link rel="self" type="application/atom+xml" href="https://lucassaldanha.github.io/feed.xml"/><link rel="alternate" type="text/html" hreflang="en" href="https://lucassaldanha.github.io/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Lucas Saldanha </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>My Claude setup: Superpowers, claude-mem, and rtk</title><link href="https://lucassaldanha.github.io/posts/my-claude-setup/" rel="alternate" type="text/html" title="My Claude setup: Superpowers, claude-mem, and rtk" /><published>2026-05-31T09:00:00+12:00</published> <updated>2026-05-31T09:00:00+12:00</updated> <id>https://lucassaldanha.github.io/posts/my-claude-setup/</id> <content type="text/html" src="https://lucassaldanha.github.io/posts/my-claude-setup/" /> <author> <name>Lucas Saldanha</name> </author> <category term="Programming" /> <summary>A couple of weeks ago I wrote about how I went from refusing to use AI coding tools to actually enjoying working with them. That post was mostly about mindset: learning to plan first, to stay in the loop, to treat the AI like a fast collaborator rather than a vending machine for code. This one is about the what. A few tools and plugins have stuck around long enough that they’ve become part of ...</summary> </entry> <entry><title>From resistance to co-creation: my journey with AI coding tools</title><link href="https://lucassaldanha.github.io/posts/co-creation-with-ai/" rel="alternate" type="text/html" title="From resistance to co-creation: my journey with AI coding tools" /><published>2026-05-14T09:00:00+12:00</published> <updated>2026-05-14T09:00:00+12:00</updated> <id>https://lucassaldanha.github.io/posts/co-creation-with-ai/</id> <content type="text/html" src="https://lucassaldanha.github.io/posts/co-creation-with-ai/" /> <author> <name>Lucas Saldanha</name> </author> <category term="Programming" /> <summary>The diff keeps growing. I scroll through it and lose count of how many files have changed. New abstractions that nobody asked for, interfaces wrapping things that didn’t need wrapping, helper classes for problems I didn’t have. The feature I actually needed still isn’t working. I’d asked the AI to help me build something, and what I got back was a small city of code I didn’t understand and didn...</summary> </entry> <entry><title>Who Moved My Cheese Testnet?</title><link href="https://lucassaldanha.github.io/posts/who-moved-my-cheese-testnet/" rel="alternate" type="text/html" title="Who Moved My Cheese Testnet?" /><published>2025-03-13T08:58:00+13:00</published> <updated>2025-03-13T08:58:00+13:00</updated> <id>https://lucassaldanha.github.io/posts/who-moved-my-cheese-testnet/</id> <content type="text/html" src="https://lucassaldanha.github.io/posts/who-moved-my-cheese-testnet/" /> <author> <name>Lucas Saldanha</name> </author> <category term="Programming" /> <summary>The recent incidents on the Holesky and Sepolia networks have made me think about our current state of testnets and who is most affected by these issues. It also made me reflect on our current approaches for testing hardforks and other coordinated rollouts and where we can improve. In this post, I am hoping to share a little bit of my view on the current state of our testnets and give some sugg...</summary> </entry> <entry><title>Breakdown of EIP-7002</title><link href="https://lucassaldanha.github.io/posts/breakdown-of-eip-7002/" rel="alternate" type="text/html" title="Breakdown of EIP-7002" /><published>2024-11-22T15:00:00+13:00</published> <updated>2024-11-22T15:00:00+13:00</updated> <id>https://lucassaldanha.github.io/posts/breakdown-of-eip-7002/</id> <content type="text/html" src="https://lucassaldanha.github.io/posts/breakdown-of-eip-7002/" /> <author> <name>Lucas Saldanha</name> </author> <category term="Programming" /> <summary>Introduction The main idea behind EIP-7002 is to allow validator exits to be triggered by a transaction sent from their withdrawal address (also known as the eth1 address). Currently, the only mechanism to initiate a validator exit requires a message signed by the validator key. In this post we will look at why we would want a second mechanism to exit our validators and some technical details...</summary> </entry> <entry><title>From Blocktree to Blockchain and Block Finalisation - Ethereum Yellow Paper Walkthrough (7/7)</title><link href="https://lucassaldanha.github.io/posts/ethereum-yellow-paper-walkthrough-7-7-blocktree-to-blockchain-and-block-finalisation/" rel="alternate" type="text/html" title="From Blocktree to Blockchain and Block Finalisation - Ethereum Yellow Paper Walkthrough (7/7)" /><published>2020-06-03T09:00:00+12:00</published> <updated>2020-06-03T09:00:00+12:00</updated> <id>https://lucassaldanha.github.io/posts/ethereum-yellow-paper-walkthrough-7-7-blocktree-to-blockchain-and-block-finalisation/</id> <content type="text/html" src="https://lucassaldanha.github.io/posts/ethereum-yellow-paper-walkthrough-7-7-blocktree-to-blockchain-and-block-finalisation/" /> <author> <name>Lucas Saldanha</name> </author> <category term="Programming" /> <category term="Ethereum Yellow Paper" /> <summary>Welcome to the last post of the Ethereum Yellow Paper Walkthrough series! It took way longer than I expected when I started this almost two years ago, but here we are at the finish line. In this final post, we’ll cover sections 10 and 11 of the Yellow Paper. We’ll look at how a tree of candidate blocks becomes a single canonical chain (section 10) and what block finalisation actually involves:...</summary> </entry> </feed>
