June 30, 2025

💡 Automatic syncing from Raindrop.io to WordPress link posts

Automatic syncing from Raindrop.io to WordPress link posts

I read Ethan Marcotte’s Link bug this week, which led me to Sophie Koonin’s Automated weekly links posts with raindrop.io and Eleventy , and that is such a cool idea that I had to do something similar.

Thanks to getting nerdswiped by Ethan and Sophie I now have a Cloudflare Worker that takes links that I tag with blog on Raindrop.io, and posts it (with excerpt taken from the Notes section) as a link post to this blog. You can just scroll down to see a bunch of example.

It’s not fancy but it works beautifully! Every hour it checks for new link with the blog tag, and then it creates a posts like this:

<h1>Link title</h1>
<p>This is my note about the article, with <strong>markdown</strong> support.</p>
<p>→ <a href="https://example.com" target="_blank" rel="noopener">Article Title</a></p>

If this is something that could be useful to you, you can view the source code here and deploy to Cloudflare Workers to make it your own.

---

On estimates as navigation, not promises

I’ve been thinking about engineering estimates a lot and need to write about it. But for now, Adam Keys sums it up nicely:

Everyone knows surprises will happen. The estimate should help the team make better decisions when they do, not box them into promises they can’t keep. The best estimates I’ve given weren’t the most accurate—they were the ones that helped teams navigate uncertainty instead of pretending it away.

→ On estimates as navigation, not promises

---

Interdependence is My New Retirement Plan

Ok I love this story.

I’ve been reading a lot of Robin Wall Kimmerer lately. She tells a story in The Serviceberry that’s become a sort of guiding star for me, about the experience of a linguist who was studying a hunter-gatherer community in the Brazilian rainforest.

“He observes that a hunter had brought home a sizable kill, far too much to be eaten by his family. The researcher asked how he would store the excess. Smoking and drying technologies were well known; storing was possible. The hunter was puzzled by the question […]‘Store my meat? I store my meat in the belly of my brother,’ replied the hunter.”

And yes to this:

I’ve been thinking so much about what it would mean for me to “store my meat in the belly of my brother”—to give to my loved ones and communities and trust that my generosity will circle back to me when I need it. I know it’s how I want to live. It’s how I want us all to be able to live.

→ Interdependence is My New Retirement Plan

---

My AI Workflow for Understanding Any Codebase

Great tip!

Convert GitHub repos to markdown with repo2txt, drag into Google AI Studio, and ask questions. Gemini’s massive context window makes it amazing for code comprehension.

The rest of the article goes into Peter’s AI coding workflow. I’ve mostly been using ChatGPT o3 for spec creation, but this is another compelling alternative.

→ My AI Workflow for Understanding Any Codebase

---

Field Notes From Shipping Real Code With Claude

I know we’re drowning in vibe coding stuff right now, but this extensive post about shipping code with Claude is a fantastic resource. Great prompt rules and tips, and also solid advice for what the humans are for…

Your role as a senior engineer has fundamentally shifted. You’re no longer just writing code—you’re curating knowledge, setting boundaries, and teaching both humans and AI systems how to work effectively.

Lean management and continuous delivery practices help improve software delivery performance, which in turn improves organizational performance—and this includes how you manage AI collaboration.

→ Field Notes From Shipping Real Code With Claude

---

How to provide feedback on documents.

This is great advice on providing feedback on docs. This especially resonated:

Before starting, remember that the goal of providing feedback on a document is to help the author. Optimizing for anything else, even if it’s a worthy cause, discourages authors from sharing their future writing. If you prioritize something other than helping the author, you are discouraging them from sharing future work.

→ How to provide feedback on documents.

---

In Praise of “Normal” Engineers

I love this take on the “10x engineer” phenomenon. Ubuntu (the African concept, not the operating system…) strikes again. “I am because you are.”

Individual engineers don’t own software; engineering teams own software. It doesn’t matter how fast an individual engineer can write software. What matters is how fast the team can collectively write, test, review, ship, maintain, refactor, extend, architect, and revise the software that they own.

→ In Praise of “Normal” Engineers

---

Platform reality

Robin Sloan discusses Substack, and platforms in general, in another excellent post:

Expect enclosure; expect a few big winners; expect advertising, with all the attention-hacking that will demand. Expect, also, that writers will con­tinue to mold their work to fit Sub­stack’s par­tic­ular ecology, rather than “merely” use the tools to pursue their inde­pen­dent visions and ambitions. We learned this about plat­forms a long time ago.

→ Platform reality

---

Thanks for reading Elezea! If you find these resources useful, I’d be grateful if you could share the blog with someone you like.

Got feedback? Send me an email.

PS. You look nice today 👌