Cursor (lifecycle) Hooks just dropped and GitButler already has support for it!
Thank you Cursor team for the early access! Check out what we built with it blog.gitbutler.com/cursor-hooks... 
Check it out here:
github.com/planetscale/... Migrate your Postgres database to PlanetScale, fast. Our migration-scripts repo has tools for migrating: - Postgres → PlanetScale PG (Logical or DMS) - Heroku PG → PlanetScale PG (via Bucardo) - Postgres → Vitess
Why iOS Teams Are Flying Blind (And How to Fix It)
pepicrft.me/why-ios-team... 
Yes! The Git Panel will surface conflicts and when they are clicked on, will take you to the file where you can choose which version to keep, or edit directly.
the "highly leveraged" piece really bounces around in my brain, if a t-shirt factory switches from sewing machines that make 1 shirt/worker/hour to robotic ones that let a worker make 20 shirts per hour does not increase pay 20x, right? what is the mechanism for that higher leverage becoming wages?
that said: the article is well-written, and definitely thoughtful in the domain that amodei is most passionate about, which is medicine / biology. i wish it covered the other domains a lot more, though.
i want a big ol' citation needed marker on "increasing compensation" in this paragraph because i cannot see any simple or complicated economics brain way in which this is inevitable
it seems, at the moment, lopsided: ai has a very visible (so far, negative?) impact on governance, definitely negative impact on economic measures (paying llm researchers $10M bonuses is not good for gini coefficient…), but its impact on medicine is uncertain, minimal, and not visible to most
spent some time reading dario amodei's "machines of loving grace" this morning.
found it surprisingly narrow? extensive ideas about how ai will assist medicine and then a pretty brief, noncommital discussion of economic, governance, and cultural impacts
www.darioamodei.com/essay/machin... porteur bag v2 update macwright.com/2025/09/27/p... Not sure if it crossed your way @josevalim but this is our love letter to the Elixir and Phoenix ecosystems too. Could we have used a React-based design system? Sure! But our product would have ended up looking like all the others, with a strong dependency on an ever-changing, intricate ecosystem. Instead, we chose to bet on the web and Phoenix. Tuist is crafted to maximize efficiency with minimal effort, and Noora's design system is crucial to this goal. While using it to develop our new marketing page recently, I was reminded of the incredible work made by @asmitbm and @cschmatzler. 
While I enjoy the concept of agentic coding, I'm not keen on the inauthentic design it produces. This has made me value the genuine work @asmitbm is doing for Tuist even more. 
It's becoming more and more clear that the two next areas of focus for Tuist should be Swift CAS and test infrastructure:
- Performance and flakiness insights
- Dynamic sharding across environments
- Snapshot testing tooling and infra
These are common needs across large ogs TIL about container style queries and the role they can play to simulate media queries with variables:
piccalil.li/blog/a-work... Making progress on the new Tuist's about page :) 
Hahaha I might have to use that 🤣
just got hella mansplained to at a motorcycle store pissed me off more than usual for some reason
"Can you please split this into smaller commits for easier code review?" This type of comments is one of the reasons we started working on GitButler. ⋈ Check out how easy it is with GitButler
We just added 4 new Insights columns for Postgres databases to track per-query pattern CPU and I/O utilization. - Cumulative CPU time - Cumulative I/O time - % of CPU time - % of I/O time
#ZedEditor Download Zed and view the full changelog here:
zed.dev/releases/sta...