Eduardo Bouças
@eduardoboucas.com
Thoughts from when I was younger • Engineer @netlify.com • He/him
If you use Scheduled Functions on @netlify.com, this one is for you.
You can now manually trigger your functions from the logs page.
Since scheduled functions only run automatically on production deploys, testing with deploy previews was a bit awkward. No more!
🔗 docs.netlify.com/build/functi...
You can now manually trigger your functions from the logs page.
Since scheduled functions only run automatically on production deploys, testing with deploy previews was a bit awkward. No more!
🔗 docs.netlify.com/build/functi...
November 6, 2025 at 6:55 PM
If you use Scheduled Functions on @netlify.com, this one is for you.
You can now manually trigger your functions from the logs page.
Since scheduled functions only run automatically on production deploys, testing with deploy previews was a bit awkward. No more!
🔗 docs.netlify.com/build/functi...
You can now manually trigger your functions from the logs page.
Since scheduled functions only run automatically on production deploys, testing with deploy previews was a bit awkward. No more!
🔗 docs.netlify.com/build/functi...
At @netlify.com, we use Netlify to build Netlify.
This is a small anecdote of a customer who sent us a feature request regarding our Blobs product: they wanted to delete entries and entire stores from the UI.
We used Netlify Agent Runners to build this and shipped it to production in record time.
This is a small anecdote of a customer who sent us a feature request regarding our Blobs product: they wanted to delete entries and entire stores from the UI.
We used Netlify Agent Runners to build this and shipped it to production in record time.
November 5, 2025 at 9:12 PM
At @netlify.com, we use Netlify to build Netlify.
This is a small anecdote of a customer who sent us a feature request regarding our Blobs product: they wanted to delete entries and entire stores from the UI.
We used Netlify Agent Runners to build this and shipped it to production in record time.
This is a small anecdote of a customer who sent us a feature request regarding our Blobs product: they wanted to delete entries and entire stores from the UI.
We used Netlify Agent Runners to build this and shipped it to production in record time.
I used my vibe-coded app to plan my dinner.
sandwish.netlify.app/645773cc4012...
(The photo is terrible, but the burger was yummy.)
sandwish.netlify.app/645773cc4012...
(The photo is terrible, but the burger was yummy.)
September 21, 2025 at 9:35 PM
I used my vibe-coded app to plan my dinner.
sandwish.netlify.app/645773cc4012...
(The photo is terrible, but the burger was yummy.)
sandwish.netlify.app/645773cc4012...
(The photo is terrible, but the burger was yummy.)
This has been haunting me for months. What could I possibly have done to get a bad review from an Uber driver?
August 24, 2025 at 3:18 PM
This has been haunting me for months. What could I possibly have done to get a bad review from an Uber driver?
August 9, 2025 at 8:05 AM
Up until now, achieving the same functionality required two separate operations: a first one for reading the current state and a second one for conditionally writing the update.
This was slower, more verbose and prone to TOCTOU bugs.
This was slower, more verbose and prone to TOCTOU bugs.
June 12, 2025 at 9:48 AM
Up until now, achieving the same functionality required two separate operations: a first one for reading the current state and a second one for conditionally writing the update.
This was slower, more verbose and prone to TOCTOU bugs.
This was slower, more verbose and prone to TOCTOU bugs.
With `onlyIfMatch`, you can update an entry only if it exists and its content matches a given ETag.
When performing multiple updates to an entry, this gives you a safeguard against data inconsistencies resulting from multiple sources mutating the entry.
When performing multiple updates to an entry, this gives you a safeguard against data inconsistencies resulting from multiple sources mutating the entry.
June 12, 2025 at 9:48 AM
With `onlyIfMatch`, you can update an entry only if it exists and its content matches a given ETag.
When performing multiple updates to an entry, this gives you a safeguard against data inconsistencies resulting from multiple sources mutating the entry.
When performing multiple updates to an entry, this gives you a safeguard against data inconsistencies resulting from multiple sources mutating the entry.
Support for conditional writes has landed in Netlify Blobs.
The `set` and `setJSON` now let you perform create-only and update-only atomic operations.
For example, here's how you can use the `onlyIfNew` option to write an entry only if the key is new.
🧵
The `set` and `setJSON` now let you perform create-only and update-only atomic operations.
For example, here's how you can use the `onlyIfNew` option to write an entry only if the key is new.
🧵
June 12, 2025 at 9:48 AM
Support for conditional writes has landed in Netlify Blobs.
The `set` and `setJSON` now let you perform create-only and update-only atomic operations.
For example, here's how you can use the `onlyIfNew` option to write an entry only if the key is new.
🧵
The `set` and `setJSON` now let you perform create-only and update-only atomic operations.
For example, here's how you can use the `onlyIfNew` option to write an entry only if the key is new.
🧵
For the best DX without compromising interoperability, a new `fetchWithCache` method extends `fetch` and lets you conveniently get a resource from the cache (if available) or from the network, caching it for future invocations.
It's optional and even works with other providers.
It's optional and even works with other providers.
May 8, 2025 at 4:50 PM
For the best DX without compromising interoperability, a new `fetchWithCache` method extends `fetch` and lets you conveniently get a resource from the cache (if available) or from the network, caching it for future invocations.
It's optional and even works with other providers.
It's optional and even works with other providers.
Waving the flag of the open web and calling out the risks of vendor lock-in is not good enough — we have to show up and build our platform that way. So the entire feature is built on web standard APIs for full interoperability.
You can use it with any framework — or without one.
You can use it with any framework — or without one.
May 8, 2025 at 4:50 PM
Waving the flag of the open web and calling out the risks of vendor lock-in is not good enough — we have to show up and build our platform that way. So the entire feature is built on web standard APIs for full interoperability.
You can use it with any framework — or without one.
You can use it with any framework — or without one.
My first foray into 3D printing. Might keep my day job.
April 30, 2025 at 3:18 PM
My first foray into 3D printing. Might keep my day job.
March 25, 2025 at 11:23 PM
Addendum #2:
Vercel have published a postmortem. For the first time we're hearing that on the 21st they were able to «verify Netlify and Cloudflare Workers were not impacted».
And yet on the 22nd they reached out offering to get a patch... for the issue we were not affected by?
Vercel have published a postmortem. For the first time we're hearing that on the 21st they were able to «verify Netlify and Cloudflare Workers were not impacted».
And yet on the 22nd they reached out offering to get a patch... for the issue we were not affected by?
March 25, 2025 at 11:23 PM
Addendum #2:
Vercel have published a postmortem. For the first time we're hearing that on the 21st they were able to «verify Netlify and Cloudflare Workers were not impacted».
And yet on the 22nd they reached out offering to get a patch... for the issue we were not affected by?
Vercel have published a postmortem. For the first time we're hearing that on the 21st they were able to «verify Netlify and Cloudflare Workers were not impacted».
And yet on the 22nd they reached out offering to get a patch... for the issue we were not affected by?
Yes, @vercel.com completely changed the changelog I linked to in my thread leaving no traces to the firewall marketing spin. And yes, I knew it would happen so I took a screenshot.
Here's the version of reality you'd be presented had they not been called out.
Here's the version of reality you'd be presented had they not been called out.
March 23, 2025 at 12:22 AM
Yes, @vercel.com completely changed the changelog I linked to in my thread leaving no traces to the firewall marketing spin. And yes, I knew it would happen so I took a screenshot.
Here's the version of reality you'd be presented had they not been called out.
Here's the version of reality you'd be presented had they not been called out.
Yes, I may have helped ship a feature or two, but this is my best work at @netlify.com: an emoji that respectfully shames people for not using Slack threads.
December 18, 2024 at 4:31 PM
Yes, I may have helped ship a feature or two, but this is my best work at @netlify.com: an emoji that respectfully shames people for not using Slack threads.
@danabra.mov Apologies for the random mention — if you can point me to a more appropriate channel for feedback, I’m happy to post it there.
I occasionally get into this state on iOS where the view is partially cut off. Navigating to the home view and then back to the notifications fixes it.
I occasionally get into this state on iOS where the view is partially cut off. Navigating to the home view and then back to the notifications fixes it.
November 12, 2024 at 3:04 PM
@danabra.mov Apologies for the random mention — if you can point me to a more appropriate channel for feedback, I’m happy to post it there.
I occasionally get into this state on iOS where the view is partially cut off. Navigating to the home view and then back to the notifications fixes it.
I occasionally get into this state on iOS where the view is partially cut off. Navigating to the home view and then back to the notifications fixes it.
Do you want to use your @netlify.com site domain as a custom handle in Bluesky?
You can now set it up with a few clicks on the Netlify UI.
Look for "Bluesky Custom Domain" in the Netlify Extensions directory or head to app.netlify.com/extensions/b....
You can now set it up with a few clicks on the Netlify UI.
Look for "Bluesky Custom Domain" in the Netlify Extensions directory or head to app.netlify.com/extensions/b....
November 12, 2024 at 11:40 AM
Do you want to use your @netlify.com site domain as a custom handle in Bluesky?
You can now set it up with a few clicks on the Netlify UI.
Look for "Bluesky Custom Domain" in the Netlify Extensions directory or head to app.netlify.com/extensions/b....
You can now set it up with a few clicks on the Netlify UI.
Look for "Bluesky Custom Domain" in the Netlify Extensions directory or head to app.netlify.com/extensions/b....
As an incurable pessimist, I’ve summarised my take on recent world events into a short song called “Things”.
Follow me for more demotivational content.
Follow me for more demotivational content.
November 11, 2024 at 3:55 PM
As an incurable pessimist, I’ve summarised my take on recent world events into a short song called “Things”.
Follow me for more demotivational content.
Follow me for more demotivational content.
Choosing a database, as with any other piece of technology, is about tradeoffs.
For example, TripAdvisor chose a solution optimised for fast writes (my email was added to their list before I could blink), but *really* slow deletes.
For example, TripAdvisor chose a solution optimised for fast writes (my email was added to their list before I could blink), but *really* slow deletes.
November 9, 2024 at 9:57 AM
Choosing a database, as with any other piece of technology, is about tradeoffs.
For example, TripAdvisor chose a solution optimised for fast writes (my email was added to their list before I could blink), but *really* slow deletes.
For example, TripAdvisor chose a solution optimised for fast writes (my email was added to their list before I could blink), but *really* slow deletes.