Killa Bees

Sometimes a flurry of ideas come from the big man. He thinks faster than we can come up data, adn the tendency is to do new things rather than figure out why old things didnt work. Its part of what made him successful, but you have to make some wall around the project to protect it from changes. If I could figure out the tags I would call this Project Protection. Thats for another day.

Today I want to silently give a shoutout to college boy, who saved my ass my learning a processing step last week that he was able to do on samples when I was an hour late to work today. Wouldnt do for him to be sitting there idly. Its critical that he keeps his head in the game. His freshman summer, I cant really figure out why he is here. He is vauguely interested in how things work on a large scale, but not so much biology. I dont care though, he does his 8hrs, and happily. So, awesome.

I think I am doing a good job of getting him with the program, and I wish someone did that for me three years ago. There were some people helping, but no one was responsible for me. When I have a lab everyone coming in will be on probation for three months unless everything works flawlessly. I have seen many rotations crash and burn because of insufficient oversight. Wetwork is a long train of steps, and until you get the fidelity high enough, any number of small f ups can kill the output. If you work in a lab that never really asks twice whether results are correct, and on one is gonna follow you up, fine. If you want to do things right and they are not passing the controls, you need someone to turn to. Big labs with old bosses are more self organizing, and the total throughput is high enough that a ton of crap gets washed through. People get jobs based on reputation rather than product.