I'm going to be taking some time off for the holidays. But before I go, something trivial to enjoy in my absence:
Someone pointed me to the uncyclopedia entry for "geologist" a while back. It's pretty amusing, although many of the jokes are getting old at this point. Geologists love beer? Whoda thunkit?
I will admit, however, that some stereotypes have a kernel of truth. I touched on the Great Geologist-Engineer Controversy ages ago, and it still pops up pretty high in search terms that end up here. Anything that strike you as exceptionally accurate, or completely off the mark?
Tuesday, December 23, 2014
Friday, December 19, 2014
arrogance
I occasionally see badly-written reports that will be read and picked apart by other stakeholders, and bidders who blatantly ignore proposal requirements. I have also attended meetings with technical experts who had no idea what they were supposed to discuss.
These are usually not signs of incompetence. They indicate arrogance - someone or an organization that thinks that they are above such inconsequential things as evidence or support for their position.
I have never been able to just waltz into a room and expect that everyone will think that I'm brilliant (or even that I know what I'm talking about). I've never been the "golden child" or the person who everyone can see is "going places". I was an academic nonentity in high school and in college. After I'd established myself in the field, I still had to fight to prove myself when I was job hunting. And I'm still (like, this year) getting strange "wow, you can give a presentation" compliments years after I thought that particular question was settled.
All those ridiculous experiences have given me a decent-sized chip on my shoulder. But they also mean that I take my shit seriously. And when I offer a technical opinion, you'd better believe I can back it up.
I have been gratified to see that certain persons/organizations that have been particularly careless because of overwhelming arrogance have gotten burned recently. Of course, some of the offenders that I've worked with/around more closely seem to be doing perfectly fine. Sigh.
These are usually not signs of incompetence. They indicate arrogance - someone or an organization that thinks that they are above such inconsequential things as evidence or support for their position.
I have never been able to just waltz into a room and expect that everyone will think that I'm brilliant (or even that I know what I'm talking about). I've never been the "golden child" or the person who everyone can see is "going places". I was an academic nonentity in high school and in college. After I'd established myself in the field, I still had to fight to prove myself when I was job hunting. And I'm still (like, this year) getting strange "wow, you can give a presentation" compliments years after I thought that particular question was settled.
All those ridiculous experiences have given me a decent-sized chip on my shoulder. But they also mean that I take my shit seriously. And when I offer a technical opinion, you'd better believe I can back it up.
I have been gratified to see that certain persons/organizations that have been particularly careless because of overwhelming arrogance have gotten burned recently. Of course, some of the offenders that I've worked with/around more closely seem to be doing perfectly fine. Sigh.
Labels:
miscellany,
short psychology
Tuesday, December 16, 2014
scientific $$$ competition
In both the academic world and the consulting business, many of us chase after big pots of money - the sort of money that would fund an entire research program or keep an office employed for years. Sometimes we compete for individual projects, or we compete for the chance to be put on a list for future work. It shouldn't come as a surprise that the sorts of organizations that have these pots of money are also big, and usually have complicated and occasionally opaque selection processes. If the proposal/bid requirements are especially onerous, part of the selection process may be to see how good the competitors are at following future onerous contract requirements.
With this in mind, I have two pieces of advice:
1. When putting together a bid or an application, follow the directions. If it says to include registered copies of corporate/individual certifications, scrounge them up. If the CVs/resumes/project examples are to be 1 page each and in Times New Roman Font, then format them. If it says you have 12 minutes for an in-person presentation, then don't prepare an hour long presentation.
2. If you do decide that the requirements are ridiculous, don't send an e-mail blast to the grant/contract people and the bidding group, saying that the entire process is bogus and that you're dropping out of contention because you have better things to do with your time.
With this in mind, I have two pieces of advice:
1. When putting together a bid or an application, follow the directions. If it says to include registered copies of corporate/individual certifications, scrounge them up. If the CVs/resumes/project examples are to be 1 page each and in Times New Roman Font, then format them. If it says you have 12 minutes for an in-person presentation, then don't prepare an hour long presentation.
2. If you do decide that the requirements are ridiculous, don't send an e-mail blast to the grant/contract people and the bidding group, saying that the entire process is bogus and that you're dropping out of contention because you have better things to do with your time.
Labels:
management,
miscellany
Friday, December 12, 2014
competitor advice
I gave a driller a ride to another site that his company was working at so he could borrow a particular tool. When we arrived, I introduced myself to the geologist, who worked for a firm that directly competes with mine, and we started chatting as the drillers rummaged around their rig. He seemed to be a complete newbie and unsure of himself, a position that I remember well and empathize with.
He needed to install a monitoring well at the top of rock or at a target depth, whichever was first, and he was trying to figure out if he'd hit bedrock yet. So where had I hit bedrock?
Well, I was on top of a bare bedrock knob, so we'd simply stuck the drill rig where it was supposed to go and started bedrock drilling. He was in a valley several miles away, and I didn't have the foggiest idea of the bedrock depth at his location.
He was pretty disappointed at this. But then he had another idea. What did my bedrock look like?
"Well, bedrock can be pretty variable in this area [it's composed of a bunch of different units smushed together]. But we encountered X rock, composed of mostly mineral A and some mineral B, and in a few places, this really distinct mineral C..." then I realized his eyes had glazed over.
He picked up a nondescript chunk of rock that did not look like what I had encountered. "So, did it look like this? Could this be bedrock? We drilled in about 3 inches."
In case you were wondering, we were working in boulder central. Three inches of rock drilling tells you nothing about where the parent rock actually is. At this point, I realized I was perilously close to suggesting that he take some action (drill deeper) that would have an impact on his firm's investigation, so I hemmed and hawed and suggested he follow whatever his home office/specification/work plan suggested. Luckily, my driller came back with what he needed and we skeddadled.
My instinct is to be as helpful as possible, but I also don't want to annoy either my organization or a competitor by inserting myself in someone else's work. What would you have done?
He needed to install a monitoring well at the top of rock or at a target depth, whichever was first, and he was trying to figure out if he'd hit bedrock yet. So where had I hit bedrock?
Well, I was on top of a bare bedrock knob, so we'd simply stuck the drill rig where it was supposed to go and started bedrock drilling. He was in a valley several miles away, and I didn't have the foggiest idea of the bedrock depth at his location.
He was pretty disappointed at this. But then he had another idea. What did my bedrock look like?
"Well, bedrock can be pretty variable in this area [it's composed of a bunch of different units smushed together]. But we encountered X rock, composed of mostly mineral A and some mineral B, and in a few places, this really distinct mineral C..." then I realized his eyes had glazed over.
He picked up a nondescript chunk of rock that did not look like what I had encountered. "So, did it look like this? Could this be bedrock? We drilled in about 3 inches."
In case you were wondering, we were working in boulder central. Three inches of rock drilling tells you nothing about where the parent rock actually is. At this point, I realized I was perilously close to suggesting that he take some action (drill deeper) that would have an impact on his firm's investigation, so I hemmed and hawed and suggested he follow whatever his home office/specification/work plan suggested. Luckily, my driller came back with what he needed and we skeddadled.
My instinct is to be as helpful as possible, but I also don't want to annoy either my organization or a competitor by inserting myself in someone else's work. What would you have done?
Friday, December 5, 2014
page padding
I remember high school essay assignments, where I had some outrageous page requirement, like 5 pages, and tried to pick the largest margins and font size I could get away with.
We don't have minimum report lengths in the environmental biz. But some people are still addicted to padding.
I will occasionally receive a PDF with several thousand pages, and everything except the first 15 pages are lab reports and copies of waste manifests, and maybe one appendix that I actually need buried between them. I've also received documents that have bundled every single reference, intact, within the file itself. Even if said documents are free, stupid easy to find, and gigantic. Like say, this. (or google "ATSDR arsenic" and it's the first hit). In those documents, PDF bookmarks were usually conspicuously absent. And many of those pages are (poorly) scanned photocopies, so the file size is gigantic for the actual information provided.
Storage space is cheap, and we're in the modern era, so opening a 300 MB file of filler doesn't usually crash my computer. And I can strip out the crap that I know I won't need myself. But really, at a time when labs use electronic data deliverables (EDDs), and we can convert practically everything to a PDF directly, and we can easily link to other documents without making a 10,000 page monster file, why do so many reports come out looking like a giant stack of poorly sorted papers?
We don't have minimum report lengths in the environmental biz. But some people are still addicted to padding.
I will occasionally receive a PDF with several thousand pages, and everything except the first 15 pages are lab reports and copies of waste manifests, and maybe one appendix that I actually need buried between them. I've also received documents that have bundled every single reference, intact, within the file itself. Even if said documents are free, stupid easy to find, and gigantic. Like say, this. (or google "ATSDR arsenic" and it's the first hit). In those documents, PDF bookmarks were usually conspicuously absent. And many of those pages are (poorly) scanned photocopies, so the file size is gigantic for the actual information provided.
Storage space is cheap, and we're in the modern era, so opening a 300 MB file of filler doesn't usually crash my computer. And I can strip out the crap that I know I won't need myself. But really, at a time when labs use electronic data deliverables (EDDs), and we can convert practically everything to a PDF directly, and we can easily link to other documents without making a 10,000 page monster file, why do so many reports come out looking like a giant stack of poorly sorted papers?
Labels:
writing
Tuesday, December 2, 2014
worst science grades
Geologists/scientists, did you have any terrible grades in a science class? This post discusses lousy grades from an academic's (ecology) perspective.
In college, I caught fire in chemistry, stunk up my math classes, did ok in my geology classes, and was generally a better student in my non-major classes. That post I referred to also discussed my lousy high school science classes, which temporarily convinced me that I couldn't hack "real science", so I won't rehash high school here. In the end, I got school honors as an undergrad, but not department honors. I didn't have that singular lousy grade, though.
When I was a senior in college and trying to figure out what to do next, I thought that only brilliant people who got all As were "allowed" into graduate school. None of my professors seemed to think I was good enough. Nobody said, "hey, have you considered grad school?" It didn't occur to me until much later that the only students from my department who went to grad school right from college were clearly preferred by the professors, who were aggressively "outdoorsy", dominated the class discussions, and generally sucked all the oxygen out of the room from those of us who were more reserved or unsure of ourselves.
Here's the thing. One bad grade won't keep you from being a stellar academic. One bad undergrad experience won't keep you from getting where you want to go, whether that's a "hard" science or academia, or somewhere else. I used to work with a science expert who had flunked out of college entirely. It may take some hard work initially. Maybe you need to build an industry reputation. Maybe you take a couple years to take (or re-take) some classes. But there are no iron gates preventing you from getting the experience/grades/confidence to get to the next step, whether it's academia or industry.
In college, I caught fire in chemistry, stunk up my math classes, did ok in my geology classes, and was generally a better student in my non-major classes. That post I referred to also discussed my lousy high school science classes, which temporarily convinced me that I couldn't hack "real science", so I won't rehash high school here. In the end, I got school honors as an undergrad, but not department honors. I didn't have that singular lousy grade, though.
When I was a senior in college and trying to figure out what to do next, I thought that only brilliant people who got all As were "allowed" into graduate school. None of my professors seemed to think I was good enough. Nobody said, "hey, have you considered grad school?" It didn't occur to me until much later that the only students from my department who went to grad school right from college were clearly preferred by the professors, who were aggressively "outdoorsy", dominated the class discussions, and generally sucked all the oxygen out of the room from those of us who were more reserved or unsure of ourselves.
Here's the thing. One bad grade won't keep you from being a stellar academic. One bad undergrad experience won't keep you from getting where you want to go, whether that's a "hard" science or academia, or somewhere else. I used to work with a science expert who had flunked out of college entirely. It may take some hard work initially. Maybe you need to build an industry reputation. Maybe you take a couple years to take (or re-take) some classes. But there are no iron gates preventing you from getting the experience/grades/confidence to get to the next step, whether it's academia or industry.
Labels:
academia
Subscribe to:
Posts (Atom)