Chase Adams

I turned thirty last August, and for the first time in my life, I started composing the principles that are important to me. This past week, I finalized the first version: cadams.io/principles

Zero to 1.0 After two years of work, 50+ releases, thousands of commits, and hundreds of bugfixes, we are officially declaring Zero stable and ready for production workloads. zero.rocicorp.dev/docs/release-n…

Zero 0.25 is out, including: * Completely overhauled query / mutator DX * Rewritten and simplified docs * Brand new install guide * Automatic query planning 🤯 – for much better perf by default, without manual query tuning ... and much, much more. See: zero.rocicorp.dev/docs/release-n…

@fat Thank you (and Ian) for putting this together! I honestly can't wait to read this.

A few of you asked for this – so Ian did an ENORMOUS deep dive on the technical aspects of our data rewrite / migration… Worth a read if you're doing local-first or considering replicache… docs.pierre.co/changelog/loca…

@aboodman @rocicorp You all should come back in the winter when it's nice here!

team @rocicorp is in arizona this week cranking on zerosync. We're working from this absurdly dilapidated old mansion. Only about 20% of the lights work at any given time. The pool is the color of lake water. Half the doors don't open. Having an absolute blast. Can't wait to share this with you.

@newcomputer Congrats on the launch!

dot is now available on the app store apps.apple.com/us/app/dot-liv…

@byteofbits Do you see this as eventually replacing Lists? Or is there still utility in "temporarily extending" an Object in a List?

When we set out to improve CRM - we realised that Custom Objects and the Data Model they enable sat at the centre of what made Salesforce great. I even wrote a blog post about it: attio.com/blog/why-sales… It's taken us a while to get Custom Objects just right - from tweaking our import tooling through to ensuring our integration partners support them well. Today we're really proud to share that Custom Objects is out of beta and firmly ready to help businesses of all shapes and sizes scale!

This tweet drops me to 39,000%.

@thdxr I'm super excited about D1 but as far as I can tell it doesn't support transactions (only a batching API). Once they're supported I'm all in.

drizzle just landed support for d1 http api what this means is there's finally a good way to manage schemas in cloudflare d1 which unblocks actually being able to have a fully cloudflare native app without compromise

@thdxr Do/will you support linking between providers? e.g. Cloudflare worker with SES email?

we're on a mission to eliminate every random SaaS provider in your stack sending email? directly use infra that handles billions of emails a day - all you have to do is define a sender quickstart in reply

Ideas and Execution On the relationship between the ideas that drive creation and the creation itself: Almost five years ago, I went to the Massachusetts Museum of Contemporary Art (MASS MoCa) and saw Sol LeWitt’s installation there. He had created over 100 wall drawings across 27,000 square feet of space, made of three stories of narrow hallways and expansive rooms with drawings on all sides. The work is driven by shapes and lines; there was mathematical rigor to every drawing, inspired by geometry and simple rules. They are accompanied by a short description: > Wall Drawing 1180: Within a four-meter circle, draw 10,000 black straight lines and 10,000 black not straight lines. All lines are randomly spaced and equally distributed. But “accompanied” is not the right word for it. It’s common for artists to use geometry. It was the rigor that was so impressive. The descriptions of the artwork were no longer than a few paragraphs, and usually only one or two sentences. All precise and meticulous. > Wall Drawing 46: Vertical lines, not straight, not touching, covering the wall evenly. He started his first drawings with a series of parallel, straight lines. The work grew to include minimalist geometric shapes driven by straight lines, drawn with pencil or pen with exacting geometry. As his career progressed, he incorporated more color and complex patterns into his art; more bold lines, vibrant colors, irregular shapes, different materials. All driven by initial instructions which he followed meticulously. > Wall Drawing 38: Tissue paper cut into 4-cm squares and inserted into holes in the gray pegboard walls. All holes in the walls are filled randomly. Closer to the end of his life, his work became increasingly collaborative. He viewed the rules as art in its own right; he would work with other artists and they would execute the complex instructions, while bringing their own unique perspective and style to the drawings. Each floor of Mass MoCa was a phase in his career, and the final floor included his collaborations with other artists. You could see the subtle departure from the rest of the work; more vibrant colors, a new material, but keeping the exacting rigor that LeWitt maintained. There is a story in the evolution of his work. He started individualistic, simple, regimented. His last works were collaborative, with diverse mediums and an expansive visual vocabulary. The instructions themselves are elegant and beautiful. The work clearly starts there. But it’s not only that. They are only abstract words; the execution brought them to life. The work didn’t exist without the painstaking execution. Let’s say you are drawing 10,000 straight black lines, and each line takes about 10 seconds each. That would mean almost 28 hours of meticulous focus. And that would be very fast, since each line must be evenly spaced and equally distributed. There is a lesson of “craft” in this space. The vision, the execution, and the constant exchange between the two. It is somewhere between science and art. The analytical see the geometry; the artistic see the symmetry. It is not definitively one or the other. Somewhere between them is the craft. The most incredible man-made achievements can be described in this way. Take an Eames lounge chair as an example: curved plywood, thick leather cushions, three distinct pieces. A moleskin notebook: oil-cloth bound cover, elastic closure, compact. A Montblanc pen: handcrafted ribs, iconic emblem, sleek body. They can be described with simple words, but it’s not only the words that make them beautiful. They are beautiful because their craftsmanship starts with their description and continues with their execution. Everyone starts where LeWitt did. Your early vocabulary starts narrow and elementary, separate from others. As you have more interactions with the work, it changes your vocabulary and your vocabulary changes the work. You start seeing what makes something have deep quality and the beauty in collaborating on that vision. There’s a widely known trap in the world for people without experience. They will say things like, “that [incredible] product would have existed no matter what, they were just the first to think of it.” This is not true. There is a feedback mechanism between what exists in the current moment and the way people view the world. You would not think to start an online store before the Internet. The reality is that the idea was only the beginning of a journey that created the product. The people who have experience will sometimes say the opposite, and they are also wrong. The idea matters. It's not only about execution. The two shouldn't be separated; the idea should evolve over time with the work. The idea drives the early work, and the early work changes the idea, and so on. It is the interchange between the two that makes craft. It's taking feedback from the work and allowing it to change the idea. The vocabulary evolves with the work. If you trivialize the idea, the work will suffer. And vice versa. Another way people commonly say this is that it’s about the journey, not the destination. This is not entirely true. The destination *is* the inspiration; it’s why you started in the first place. It’s why you keep going. Your experience along the way will change your expectations, things will happen that are beyond your control, and your destination will change. The destination still matters. The hardest part is allowing the idea to change with the work, while making sure the idea keeps its importance.

@zenorocha Do you plan on adding inbound email w/ webhooks soon?

What do you want to know about Resend? Reply here and I’m going to answer in a Q&A video! Could be anything related to the product, company, team, etc.

@neondatabase launched an embedding extension 20x faster than pgvector (why would you use a dedicated vector db now?) github.com/neondatabase/p…

@fraserbrown_org @Livepeer This just shipped to production a few seconds ago! Check it out now 🚢

@Livepeer @0xcadams Oh, got it working with OBS after reading docs )

THIS WEEK IN VIDEO // In-Browser Broadcasting 📹 @0xcadams gives us the scoop on how to get sub second latency livestreams without the hassle Try it out yourself today at Livepeer.org 👀

@nextjs Thanks! Loving the new app router and server components.

Next.js 13.4.8 includes improvements for compiler performance and various bug fixes. On Vercel​.com, this led to 1.5x faster local server startup and 54% faster updates when making changes (HMR / React Fast Refresh). Here are the changes we've made to improve performance ↓ ◆ Doing less work by caching or minimizing slow operations ◆ Optimizing expensive file system operations ◆ More incrementally traversing trees during compilation While these updates are more about the underlying tools like bundlers and compilers, we thought it would be interesting to share some of the work we’ve done. For example, to improve the local server startup (next dev) we’ve: ◆ Improved the traversal of the client / server graph, removing 100ms ◆ Moved unnecessary blocking synchronous calls to be lazy, removing 70ms ◆ Reduced initial compilation to only need either pages or app routes instead of both, removing up to 500ms To improve HMR / React Fast Refresh, we’ve: ◆ Added a shared cache for file system calls between different compilation phases ◆ Optimized file resolution for deeply nested directories, improving cold compilation by 30% ◆ Improved revalidation heuristic to prevent blocking the main thread, removed 1-2s on large pages We’ve also added default configurations for popular libraries with `modularizeImports`. This ensures you don’t accidentally try to reload thousands of additional modules, typically found with icon libraries. These performance improvements and various bug fixes are available today in 13.4.8. Our current focus remains optimizing performance and reliability, so expect more updates like this in the next release. github.com/vercel/next.js…

@sjwhitmore banana

was testing out falcon-chat on huggingface (huggingface.co/spaces/Hugging…) & this was my interaction with it. honestly cracked me up that being said, not sure i can make immediate use of this model lol

@snowmaker Could you expand on this? What does it mean to fix visa issues - is that just connections with immigration lawyers who can help with H1B?

19/ A lot of international students on visas weren't sure if they could do a startup and stay in the US.  Fortunately, while YC can't solve every problem for founders, this one we can.  When international students get into YC, we can almost always fix their visa issue.

Yesterday we hosted 400 top university students at the YC Summer Conference - a fun day of talks about startups.  Talking to the students afterwards, I found myself giving a lot of the same advice. So in case it's useful to others, here is my startup advice for students.

@benedictevans 80/20 on realistic photos vs uncanny valley

@rauchg I'm confused whether running functions that query a Vercel/Neon DB in the edge is best practice, or if they should run closer to the database in the same region. What are your thoughts on that?

I'm proud to say, we've delivered. Notice: ◆ `await` is now in there (making more sense in the context of the JS/TS ecosystem) ◆ We _opt into_ dynamism. This is necessary so that you get a random assortment of pokemon per request ◆ Edge, I choose you github.com/rauchg/how-is-…

I can't get over @vercel Postgres being queryable… ◆ From your React component ◆ From the Edge ◆ With no connection setup ◆ With streaming support… Some cool details🧵 how-is-this-not-illegal.vercel.app