And, while the design cycle for biology is longer than CS, it's not that bad, especially now. Given that I have decades of computer programming and wet biology in my background, I guess you can 'trust' that I'm not one of these guys that thinks progamming a cell is as easy as programming a computer. But I do also frequently lament that the approach to biology is often the 'script kiddie' approach.
Among academics and in industry, I OFTEN see that the operator's understanding lacks depth (not the field). We were having a problem with DNA shearing once, and I asked all of my coworkers if they could explain to me the chemical mechanism of DNA shearing and not a single person could even postulate a testable experiment that could have a positive effect on both what we were trying to do and our global understanding.
In another case, I asked around if anyone knew the mechanism of electroporative transformation into E. coli. Looking it up (the answer had been known for about two decades) resulted in a small change in our transformation procedure (at no extra cost!) and a reproducible 20x improvement in the transformation efficiency of 500+kbp DNA.
Yeah, maybe "we just don't understand it well", but it's often because the scientists don't understand it well, not the corpus of humanity as a whole. Now: I'm not saying we have a comprehensive understanding of biology, I'm saying it what we the culture have is enough that simple, useful, garage operations are really in striking range.