Cradle

Looking forward to speaking today at Decoding Bio AI x Bio Conference ! No doubt we will discuss and debate predictions on the impact of AI on drug discovery and what it means to be a (human) scientist in the future as some of our future colleagues will be AI models. What will they contribute, are we clear on what we expect, how will we work with them - and they with us? Yiannis Kiachopoulos thoughtful and educational piece takes us beyond buzzwords into the world of Co-Scientists. One quote particular resonated with me: “Like the detective (…), the scientist has to find and understand the clues before deciding which story they support. The scientist is not forcing every puzzle piece into the first coherent story. The scientist is laying out the competing stories, identifying the clue on which they disagree, and choosing a test that could change which story is most credible.” Success not only defined as giving us more answers, but also giving us better questions and an actionable path forward. Is it too simple to think AI’s greatest impact will be augmenting scientific judgement rather than replacing it? What are your thoughts?

Looking forward to AIxBio today! Will chat with Marcus Schindler about how we can not only make discovery faster, but also get better medicines along the way. See you there?

We have joined A-Alpha Bio, Dyno Therapeutics, Boltz, and GSK in a mission to solve the bottleneck holding AI protein engineering back: data! More on the Atlas Consortium:

NOBODY warns you how disorienting the first months with a new solution actually feel. You expected progress. Instead you're re-explaining the same thing, re-running the same meeting, wondering if something's wrong with the rollout. *Nothing* is wrong. This is what change actually costs. Not the license fee. Not the implementation hours. The mental load of learning to think differently - about your data, your workflows, your team's assumptions. Value doesn't arrive on schedule. It arrives after repetition. After the sixth conversation lands differently than the first five. After someone on your team stops asking "how do I use this" and starts asking "what should we try next." The teams that get there aren't necessarily the ones who moved fastest. They're the ones who were given enough space to actually change how they think, not just what they use. Give yourself and your team permission to be in that in-between space longer than feels comfortable. That's not a delay. That's the work 🙂↕️

We're #hiring a new Backend Software Engineer, Python in Zurich, Zurich. Apply today or share this post with your network.