I thought it had been determined that this didn't happen. Unless they just recently decided it did happen, and I missed it....
The idea has resurfaced as we learn more about Neadertal DNA. Normally, you can estimate the time back to a common ancestor pretty well based on differences in DNA. But when you use the standard techniques on humans and Neandertals, you get two time estimates rather than one. Later interbreeding is one explanation. Contamination of the Neadertal DNA with the DNA of modern human labworkers, fieldworkers, etc is another. Mutual interbreeding with a third group is another. A bad theory about how DNA differences occur over time is another. But it has given new life to an old idea.
is this the new salad shooter and I missed something?
I just delivered a project to a client that has taken WEEKS to get correct. There were errors on top of errors on top of techical failures before, but finally, it is done.
Now moving on to Q/Aing our last 5 projects, because it seems no one did and there are a million small mistakes that the CEO keeps finding.
Maybe we drop them on a level dirt field in a time-free zone, and have translators tell each combatant that to get back to their time/family/freshly-killed aurochs, they need to kill the opponent.
Salad shooters were a nonchalance ploy. We don't have the provocation for that right now. What we do have is a hunger for knowledge and a thirst for trivia.
there are a million small mistakes that the CEO keeps finding.
Shouldn't everything be bright and shiny clean before the CEO sees it? I'm managing a project for whom I'll also be a user, as will my boss. I'm insisting on QAing before she gets her hands on it, since I'm a less scary person to hear about bugs from. It's amazing how much resistance this protection ploy is meeting from the very people who'll get their asses held to the fire by management if it's not shiny. And it's been quite not shiny the times I've gotten my hands on it so far.
Maybe we drop them on a level dirt field in a time-free zone, and have translators tell each combatant that to get back to their time/family/freshly-killed aurochs, they need to kill the opponent.
Works for me. I pick astronaut.
Maybe we drop them on a level dirt field in a time-free zone, and have translators tell each combatant that to get back to their time/family/freshly-killed aurochs, they need to kill the opponent.
With the appropriate
Star Trek
music playing over loudspeakers.
I read it in your quote-back this morning, and heard, "Physician, heal thyself." Words to live by, or caffeine deficit?
Nah - just a chapter or footnote in the book, see. Or, yeah, maybe just a good couple of cups of coffee...
I have no input on caveman vs. astronaut. Or salad shooters.
Ms.Havisham and Cabil: congratulations on the new work situations!
the problem has been that we are being asked to cut schedule times over and over and over again and Q/A is getting kicked out of the equation. when we ask people to look things over before going live, we almost always get NO feedback (including from the CEO), then a day or two after it is live, things will get noticed. It is growing and speeding up pains.
It is growing and speeding up pains.
We've recently clamped down big time on process. People freak out at the schedules, but as project manager I just shrug and say "Do you want to be the one that nixes testing?" And no one really wants to take that on themselves. So we have hella testing, and hella controls on moving code from one stage to the next. Yeah, people are pissed. But the people that get pissed if stuff goes out wrong are people that can get us all fired.
