Sign In

Michelle Chen

Engineering Manager at Synthace

Michelle Chen is a Software Engineering Manager at Synthace, a company focused on revolutionizing biological research and development through advanced automation tools. She has been with Synthace for several years, transitioning from a software developer to her current managerial role, which she announced on LinkedIn in April 2022.23

In her position, Michelle plays a crucial role in enhancing user experience for scientists using Synthace's software platform. She emphasizes the importance of understanding how biologists interact with the software to improve workflows and facilitate better experimental outcomes. Her work involves collaborating closely with both engineering and scientific teams to create user-friendly interfaces that do not require programming skills, making automation accessible to a broader range of users.1

Michelle's educational background and previous experience in software engineering contribute significantly to her expertise in developing solutions that empower researchers in their work.4 Her commitment to creating impactful software aligns with Synthace's mission to streamline biological experimentation and enhance productivity in research settings.1

Highlights

May 15 · linkedin

Continuing on my reflections from the CTO Craft Con…Walking into the conference last week, I was worried that I wouldn't belong there. I’m not a CTO. I’m not a VP. I'm not <insert title>. Did I belong there?

Relatedly, I had always approached things as "Fake it until I make it" or telling myself that "You just need to have confidence" for whatever task I had or role that I was.

🦁 Last week when chatting, someone told me, "You don’t need confidence. You just need courage to do it." At first I wasn’t sure what to make of it, but the more I thought about it, the more I liked the idea. It became less about I don't have the skills and that I'm not good enough.

🖼 It became reframing it as "I'm not there yet. How do I have use my courage to get there?” All I need to do is slowly get different experiences which will ultimately lead to confidence.

So, walking out from the conference, I reflected on how I’m not a CTO (yet!) or not a VP (yet!), but I have courage to continue learning and finding opportunities to gain experience. For example, I had a great conversation with Adrian Grindrod about how he is thinking about how his teams are structured and how to staff them based on people's skillsets, which is actually quite similar to some of the challenges that we have been discussing at Synthace.

This was my long-winded way to talk about how changing the framing might change how you approach things. Do folks have recent reflections or sayings that have changed how they think about things?


Thanks again Sara Stephens for inviting me to attend. Thanks Rajani R. for the food for thought!

May 10 · linkedin

This week, I had the opportunity to attend #CTOCraftCon here in London. I'll start with sharing takeaways (and reminders) from one of my favorite talks about Observability 2.0 from Charity Majors at Honeycomb.

Observability 1.0 was all about the pillars of metrics, logs and tracing, but there was no consistent source of truth. Everyone is always struggling with figuring out which dashboards to look at and which tools to use when. I know we've always had too many dashboards with varying metrics. Debugging was all based on intuition about where to look and scar tissues from past outages.

Enter 2.0. Observability 2.0 is about reframing this problem and adding the context to create consistent structured data blobs so that it's no longer about having 3 pillars, but rather having 1 source of truth. You build everything on these log events that have all the necessary context. We need to become more like scientists and being able to better understand our complex systems.

If anyone is interested, you can read more about it here: https://lnkd.in/evVCzqBq

Two other great reminders from the talk:

  • Our job as technical leaders is to help create a faster feedback loop. The cost of finding and fixing bugs increases dramatically as you find the bugs later on.
  • Writing code is not the hard part. It's never been. The hard part is everything else - understanding, maintaining, scaling, refactoring, .... the list goes on.

Related Questions

What projects has Michelle Chen led at Synthace?
How did Michelle Chen transition from software developer to manager?
What are Michelle Chen's key achievements at Synthace?
How does Michelle Chen's role impact the company's mission?
What inspired Michelle Chen to join Synthace?
Michelle Chen
Michelle Chen, photo 1
Michelle Chen, photo 2
Add to my network

Location

London, England, United Kingdom