Tobias Lins
@tobiaslins.bsky.social
· Observability TL at Vercel
· Splitbee Founder (acquired by Vercel)
· Co-Creator of http://react-notion.com
· Co-Creator of http://feedback.fish (acquired)
· Splitbee Founder (acquired by Vercel)
· Co-Creator of http://react-notion.com
· Co-Creator of http://feedback.fish (acquired)
Reposted by Tobias Lins
The Lins Bros. are the 🐐
vercel.com/changelog/f...
vercel.com/changelog/f...
Filter for your own requests in Logs - Vercel
Filter browser-specific requests with the new "My Logs" filter in Vercel's Logs UI, simplifying debugging.
vercel.com
January 29, 2025 at 11:17 PM
The Lins Bros. are the 🐐
vercel.com/changelog/f...
vercel.com/changelog/f...
We've been using this for months already to debug vercel.com and customer issues
→ See health of your deployed functions
→ See latencies of external APIs
→ Dive into usage patterns of ISR, FDT and more
I'm so proud what we have put together here, and its just the beginning! 🚀
→ See health of your deployed functions
→ See latencies of external APIs
→ Dive into usage patterns of ISR, FDT and more
I'm so proud what we have put together here, and its just the beginning! 🚀
Vercel Observability—now generally available and free on all plans.
Observability delivers framework-aware insights, helping you optimize cost, usage, and performance.
Also available: Observability Plus. Extended retention, advanced metrics, and Monitoring.
vercel.com/changelog/ve...
Observability delivers framework-aware insights, helping you optimize cost, usage, and performance.
Also available: Observability Plus. Extended retention, advanced metrics, and Monitoring.
vercel.com/changelog/ve...
Vercel Observability is now generally available - Vercel
Observability is now available to all Vercel customers, delivering insights to optimize infrastructure and application performance.
vercel.com
December 12, 2024 at 8:59 PM
We've been using this for months already to debug vercel.com and customer issues
→ See health of your deployed functions
→ See latencies of external APIs
→ Dive into usage patterns of ISR, FDT and more
I'm so proud what we have put together here, and its just the beginning! 🚀
→ See health of your deployed functions
→ See latencies of external APIs
→ Dive into usage patterns of ISR, FDT and more
I'm so proud what we have put together here, and its just the beginning! 🚀
Someone at @golang, please add code highlighting to your documentation. Thanks!
December 5, 2024 at 11:52 AM
Someone at @golang, please add code highlighting to your documentation. Thanks!
Reposted by Tobias Lins
Edge Requests and Fast Data Transfer: Unpacking the core usage metrics of requests on the Vercel Edge Network.
Learn how Vercel handles network routing and data transfer—while giving you control over performance and costs.
vercel.com/blog/life-of...
Learn how Vercel handles network routing and data transfer—while giving you control over performance and costs.
vercel.com/blog/life-of...
Life of a Vercel request: Navigating the Edge Network - Vercel
Unpacking the core usage metrics of Edge Requests and Fast Data Transfer. Learn how Vercel handles network routing and data transfer—while giving you full control over performance and costs.
vercel.com
November 21, 2024 at 5:10 PM
Edge Requests and Fast Data Transfer: Unpacking the core usage metrics of requests on the Vercel Edge Network.
Learn how Vercel handles network routing and data transfer—while giving you control over performance and costs.
vercel.com/blog/life-of...
Learn how Vercel handles network routing and data transfer—while giving you control over performance and costs.
vercel.com/blog/life-of...
Reposted by Tobias Lins
You can just ship things
 for decisions. 1-way doors are rare. Never act like something is a 2-way-door if it is a 1-way-door
- Don’t ask for permission, ask for forgiveness but be smart about it
- [Understand what experiments are for](https://www.notion.so/When-to-experiment-8fd91090ef7a418a9532b9681524fe0b?pvs=21)
- Actually QA your shit. Abusing users for QA is inefficient and disrespectful. Users are a source of feedback about the product
- Send your stuff to trusted testers and ask for feedback
- Don’t let indecision go into your head
- If in doubt ship the version that is closer to ship and iterate
- The outcome-differential between two options in a decision is usually lower than the opportunity cost of not shipping either of them
- **You don’t need approval from anyone at Vercel to ship.** People can tell you not to ship, but you don’t have to ask them for permission, they have to reach out to you proactively if they feel strongly enough
- You reach out to legal, finance, security, privacy for their expertise not their permission
- Be transparent about what you are shipping in channels such as product-area-updates, but it is not your responsibility to ensure everybody is consuming your updates](https://cdn.bsky.app/img/feed_thumbnail/plain/did:plc:efr3ow2v22u45efltglpm3rs/bafkreih4cmsvnsrp6ey2wbrvpg5o7jp7mdbxjjt5mj2waez7duh3lfl4sy@jpeg)
November 19, 2024 at 1:31 AM
You can just ship things
Reposted by Tobias Lins
Spot when we shipped partial pre-rendering on v0 🤤
November 11, 2024 at 4:17 PM
Spot when we shipped partial pre-rendering on v0 🤤
Reposted by Tobias Lins
Here’s the thing that local-first unlocked for me and that I really leaned into with jazz.tools:
When you build an app, you *don’t* want your abstractions to be servers, DBs, the network and requests.
You want them to be *the objects your app is about* and *the humans collaborating on them*
When you build an app, you *don’t* want your abstractions to be servers, DBs, the network and requests.
You want them to be *the objects your app is about* and *the humans collaborating on them*
November 5, 2024 at 9:52 AM
Here’s the thing that local-first unlocked for me and that I really leaned into with jazz.tools:
When you build an app, you *don’t* want your abstractions to be servers, DBs, the network and requests.
You want them to be *the objects your app is about* and *the humans collaborating on them*
When you build an app, you *don’t* want your abstractions to be servers, DBs, the network and requests.
You want them to be *the objects your app is about* and *the humans collaborating on them*