Going from studying cell division to debugging React is a smaller jump than the syntax suggests.
I did two years of Bio Science in school, fully expecting lab benches and microscopes, before admitting I wanted to build things instead. What surprised me later was how much of it came along anyway.
Living systems and built ones
Biology trains you to watch tightly connected systems, where poking one pathway causes trouble somewhere you didn't expect. Software does the same thing with fewer ethics forms. An infinite loop in a useEffect looks a lot like runaway cell division. Two data fetches racing each other behave like competing reactions. Careless shared state is a mutation: small upstream, ugly downstream.
The habit that transferred
The facts mostly stayed behind. The method came with me.
When a test fails, the tempting move is to tweak things until the red goes away. Biology taught me the slower way, which turns out to be faster. Reproduce the failure. Strip away everything until only the failing part is left. Change one variable at a time and compare against a version that works. Then write the regression test, which is the code version of writing down your protocol so someone else can repeat it.
School labs also drilled in that an experiment you didn't write down didn't happen. I still write down why I chose something, because in six months a clever decision looks irrational without its context.
The speed shock
The hardest part was the speed. Biology runs on slow clocks: cultures take days, studies take years. Software moves as fast as the deploy pipeline, and it often wants a reasonable guess today because the API contract changes next week. I had to get comfortable deciding with far less evidence than I was used to.
Mitosis hasn't come up in a code review yet. The lab habits show up every day.