Comment Obligatory Portal Release Comment (Score 1) 145
It's unfortunate Google didn't come up with this in time to avoid GLaDOS being revived
It's unfortunate Google didn't come up with this in time to avoid GLaDOS being revived
(b.) Meetings must be limited to information that *everyone* *needs* to know.
I've rarely seen this go well (if ever). Most meetings I have gone to (past tense due to being laid off) have been status meetings. Manager wants to find out what everyone has been doing, and somehow it's good for everyone to know what everyone else is doing. There is perhaps some merit to the latter, but not nearly as much as the manager would like to think. I really don't need to know about the supplier issues that one engineer is experiencing when I'm dealing with FPGA code on a completely different assembly. That engineer doesn't really need to know the trials and tribulations getting the EDA software licenses going. It's not like if either one of us was hit by a bus the other is going to jump right into the cockpit and be able to take off and complete the job -- we have widely varying specialities.
But I sit there and listen to everyone kvetch about what's going wrong with their portion of the project and trundle back to the desk eventually where it takes an hour to overcome the brain numbing.
"Can't you just gesture hypnotically and make him disappear?" "It does not work that way. RUN!" -- Hadji on metaphyics and Mandrake in "Johnny Quest"