Congrats buildsync team!!

very proud of @emmyxth, @MAliyanIshfaq, & Carrie on their launch. Stanford builders on a mission to accelerate construction. BuildSync was one of the first teams I met when I started LeapYear, and it's been an absolute pleasure to work with them as part of LY F24 batch.

Introducing BuildSync: the very first public text-to-Building Information Modeling (BIM) platform created to make design easier! We're excited to share our public beta with community! Design now at: buildsync.app.

That's why it was designed with similar interfaces You can build transactions in lucid style by passing a provider pluts.harmoniclabs.tech/offc… From there you can incrementally upgrade to leverage `buildSync` or stay with the provider style

Check out our latest video for BuildSync, the five star review from Central London Job Planning, and dive into the history of the Cadbury Gorilla advert in our blog! #animatedexplainervideo #animatedvideo #2danimation #fivestarreview #blog #marketingblog #cadbury #cadburygorilla

That was my same thought process Plus I don't want to force async code for application that are sync That's why I think buildSync (similar to NodeJS API) is a good option Maintainace should not be that hard since at the end is the same process, just parallelyzed