i think one thing you also have to consider...we all have to google stuff we're unsure of. i have to google .net crap all the time. no one knows everything :) no one expects you to. but your employer will expect you to figure it out, whether you ask another coworker with more experience, or use your google-fu.

we do it every day. we even get stumped. even our senior devs :)

i wonder if after your job is done if you could shadow me at work. even for a couple hours. see what it's like. today we were joking that we should give you a mock phone interview (we were joking because we have a guy on the team that grills the crap out of applicants with questions even the rest of us don't know the answer to ;) just to kind of give you an idea of what we look for. :D

dude. i would love to spend a morning with you at work sometime in october. as long as you don't think i'd bug ya too much.

i think i'm having the fish vs. pond battle again, like i did after college. yeah, i'm the only person (left) in my dept who can build a database... but get me into the IT job applicant pool, and i'm a little fish again.

as much as i say my versatility is my strength... it's bs. it's a way to mask the fact that i know a little bit about a lot of things, and haven't really specialized at all.

*shakes head to get negative thoughts out*

bah.

well that's just it. we all feel that way. it's not just you :P i don't know a whole whopping lot about any one thing (although after 5 years, i do say .net is my strongest skill, but i'm still not a MASTER of it in any way shape or form). in fact, a lot of companies look for the jack-of-all-trades because they can put them wherever they want and let them adapt.

i honestly think that your search is difficult because of your location. there just arent a lot of jobs in toledo period, much less IT jobs. they exist, but they're hard to get into. because not only are you a little fish, there are 5,000 other little fish and only 100 tanks o.O

oh..and by "i wonder if you could" i meant "i wonder if it would be allowed by my employer" :D i'd have to check. there's not exactly "bring your friend to work day" here. :P

your company seems to have everything else -- they *should* have "bring your friend to work day"! :-D

srsly, tho -- i gotcha. assuming nothing magically pans out for me in the next two weeks, maybe we can work something out.

i know that if i were to expand my search even just to ann arbor, i'd have a better chance of finding something better. i'm just not willing to make a day trip for my commute every day. :-P sux.

it's funny how that will change, though. if you lived up here in detroit, an hour commute is pretty reasonable :P a lot of people work downtown so to live somewhere you like you mostly have to drive an hour to work :P

ann arbor can be 40 mins flat on a good day, which up here is pretty good. and it certainly beats the 2 hours per 20 mile rule of Boston ;)

at any rate, yeah, if it turns out you can come up, i'll ask :)

I'm with sheryls on this one. Don't underestimate the power of diversity on your resume, and don't sell yourself short on technical skills. Companies hire people, not technical databases. So, be a person.

I googled stuff all the time, bought books for that ONE paragraph that explained a concept, and got stumped regularly. It's the game. What makes an IT person is the ability to figure it out, and you, my dear, are good at figuring it out.

Thanks, guys. I feel a little better now. It'll still be a crapshoot as to whether I can find a company who will hire someone with problem-solving and troubleshooting skills, rather than programming knowledge, but I think it'll happen. Eventually.

Went through my desk at work today, throwing away things I won't need after next week. Found a bunch of notes and papers and flowcharts for developing the database. Pages of VBA that looks complex, but really isn't. Same with flowcharts. Made me realize that I *do* know what I'm doing. I just forgot. :-)