The point I was trying to make is that if my resume somehow got to the resumatic, it would rank me very low, and I wouldn't get considered. That's cool with me because the resumatic is used by large corporations, which I hate working for. My advice was about how to get a job at a small company. It's the only advice I can offer, as it's the only type of job I've enjoyed, and it's the only place I've read resumes (and cover letters, which are far more important than the resume in getting an interview with me)
Perhaps people would apreciate your insight more if you gave some indication what the hell you're talking about. For example a google seach on "important persons act" still leaves me clueless. Care to explain, or is this just random trolling babble?
Do like it? Why aren't you petitioning the Supreme Court to let you have nukes? Ensuring that the populace at large have access to sufficient weaponry to resist the government and/or foriegn invaders if they find it neccesary, while a fine thing in 1783, is not really workable today. While it would make a lot of sense to repeal the second ammendment, the bill of rights is such a sacred cow today, it would be political suicide to suggest. It is clearly unconstitutional to not allow citizens of the US to have any weapon they please, right up into the multi-megaton range. Watching psychos nuke our cities for the sake of this principle would obviously be idiotic, so we ignore the principle to a certain degree. The question is what degree makes sense. All of which is not to say that I don't find this troubling. The "sacred" staus accorded the Bil of Rights is great for protecting basic, needed freedoms, but it prevents us from removing the obviously out of date second amendment. Those who wrap themselves in the second amendment to protect their right to a handgun should wake up. That pea-shooter is worht diddly-squat when the army comes after you, and you can't have something that isn't. The second is already dead.
"Software does exist, or can be contracted out"
That sounds a hell of a lot like "in due time". Open source rules, and is an inherently better way to develop software, but I see the folowing conversation all the time:
Zealot: You don't need proprietary software, convert to Free software today!
User: What about aplication FOO?
Zealot: Use open source program BAR instead!
User: But it desen't do x, y and z.
Zealot: But project BAZ is making great strides! when it's done, BAR will integrate with it and all you problems will be solved. Convert Today!
User: You're an idiot.
Clue time:
coming soon != available now,
and for the vast majority of us,
almost as good, but Free == not as good
"tic-tac-toe, that game on a 3x3 grid played with X's and O's and you try to get 3 in a row. Isn't it proven that when any experienced players play the best result is a draw?"
Yes. Furthermore you can define "experienced" as "not a jibbering idiot". My 2 year old can play perfect tic-tac-toe.
Alright try this: My grandfather was Jewish, but neither I nor any ancestor for 100+ years have ever lived in Israel. My friends (palestinian) parents were born in Israel. Israeli law gaurantees me the right to become a citizen and live in Israel if I choose, but my friend would not be allowed off the plane. Explain how this is anything but atrociously racist.
I'm certainly no fan of the BSA, and being "happy" about an audit is certainly a stretch; but if they showed up where I work and wanted to know who was using what and see licenses for every copy, it would be no problem. We'd point them to the file cabinet in our IT guys office and say "knock yourself out".
If figuring out who is using what and finding the licenses is a problem for you, that tells me you're not already tracking it. Which means you don't really know if you're legal. Which means, frankly, you're probably not.
Whether you strongly doubt it or not, it has, does and will happen all the time. If Canada (for example) presents the US with convincing evidence you murdered someone in Canada, you'll be on the bus right quick. It's known as extradition, and the US has treaties covering it with most countries. They certainly vary in the crimes covered and the evidence required, but never "surrender a citizen"? Wouldn't count on it.
Re:Ever wondered *why* you're not getting jobs?
on
Resume Tips For Jobs
·
· Score: 1
"the second approach has gotten me more interviews, the job of a resume and cover letter."
But are they interviews for jobs you really want and are particularly well suited to? That you research the companies is great, you're way ahead of the masses. But the point of the research should be to reject companies that aren't a good match, and not even bother sending them a resume. All that said, the lots of resumes approach may be the way to go with big companies. I wouldn't know, I hate big companies. For small companies, or at least the one I'm now at (and occasionally read resumes for) a customized resume is essential. Just to throw in my own appocryphal (sp?) evidence- My last job hunt lasted a month and I wound up with a job I love. I sent out exactly one resume after spending a day and a half on the cover letter. The cover letter detailed why this was the perfect job for me, and I the perfect candidate for the job well enough that my boss has since admitted he didn't read my resume until after arranging the interview.
Re:Most Resume Advice is Totally Subjective?
on
Resume Tips For Jobs
·
· Score: 1
I'd agree about dropping anything that identifies your religion. Not because I have anything against Mormons, but because anyone who puts their religion on their resume is likely to babble on about it in other irrelevant contexts, which drives me up the wall. I don't care what religion it is. I mean I really, really don't care, and putting it on your resume tells me you're the type who's going to insist I should.
Perhaps you've heard of this tech bubble bursting thing there's been all this talk about? The demand for tech workers may not be as strong today as two years ago.
Well, lets see, I started out with the same dillemma and got my experience doing what... Oh, I remember! Grunt work for a little more than minimum wage.
Seriously though, try to find grunt work that's sorta-kinda-maybe related to what you want to do, and keep at it. Also try to concentrate on what you want to do (i.e. enjoy and are good at) If you try to go for something you don't actually like in hopes of bucks, you'll wind up sucking at it and won't get the bucks.
Nearly impossible? Are you under the impression there are any rules whatsoever for what must be listed on a resume? Summarize! When I'm reading resumes, if it's not listed on the first page, it's not there. Do you have experience with every database system ever concieved of? Great, say that; don't waste my time listing them. Admittedly, this approach will not serve you as well if the job is with a company scanning resumes with a computerized buzzword-finder or it's human equivalent, the HR drone. I consider that OK, because I don't want that job.
Yes! You just made my "read the whole thing" pile while the other 95% that sent me the same resume they sent everyone else went straight to the trash can. Ideally, I'd be slightly more subtle, but not so much that they don't get the point: You've spent at least a small amount of time thinking about whether this job is right for you. To those that send out any more than 10 resumes a day, I say this: If you can't spend the time to figure out if the position I've got is right for you, why should I? Both of my last two job hunts were highly successful (great jobs found quickly). In both of them combined, how many resumes did I send out? Three.
"How does anyone stand a chance in what has become more a game of chance than skill?"
4 things: 1. Be very picky about the jobs you aplly for. Only send resumes to the ones that are a very good match. 2. Cover Letter 3. Cover Letter 4. Cover Letter
As for the automated HR systems, they'll reject my resume every time. I consider this a feature.
Yes and no. A good cover letter, telling me why you want the specific job you're applying for is the best thing you can do, hands-down. Unfortunately, in some cases (particularly when the incoming resume stack is five-miles tall) cover letters get ditched. So my advice is that in addition to a good coverletter, you should include an objective, and make it a two-line cover letter. i.e. customize it every time, and tell me why this job is particularly well suited to your goals. A general (boilerplate) objective is crap. (Well, crap to you, gold to me - I can trash your resume in minimum time!)
Couldn't agree more. There is zero chance I will look past the first page of a resume. If it's over three, I'll probably trash it on that basis alone. I don't care about every job you've ever had. In my first pass, I'm not even looking at your experience directly at all. I'm looking solely to find out if you are after *this* job or after *any* job. A well stated objective can make this instantly clear. Once I've got the 10% who are actually interested specifically in the job I'm offering, almost all of them will have acceptable levels of experience anyway. I may be unusual in that if I'm hiring, for example, a database guy, having worked with the exact RDBMS we use is a very minor bonus at best. I'm mainly looking for someone who is genuinely excited about data (It still shocks me that they exist, but that's a different issue)
Regarding dropping two balls from the tower, the big reason Galileo is thought not to have actually done it is that it would not have worked! Assuming two balls of equal size, but significantly unequal mass, air resistance will cause the heavy ball to hit the ground first, rather underwhelming the assemled crowd. In my opinion, Galileo's big achievement was managing to figure out inertia despite this.
HAHAHAHA! That's so funny I've completely forgotten about all my positive experiences with MSSQL and about all the features I need that MySQL is lacking.
Well, you (and the other responder who noted it) are quite correct that tracking suggestions as "enhancement" severity bugs is entirely appropriate. The bug in question, however, is marked "blocker". It looks to me like this very issue was the subject of extensive disscussion, after which a decision was made, and implemented. Someone didn't like that decision, so they entered their view as a bug, got rightly slammed, and now they're complaining about it in other inapropriate places (this thread).
Your assumption that hybrids are necessarily lacking in power is way off. Hybrids are generally targeted toward efficiency more than performance yes. But if it's quick response to the accelerator you wan't, an electric motor is the end-all-be-all. A gas motor must rev up to the power level you ask for (assuming it's big enough to provide it). An electric motor will go from 0 to max torque as fast as you can push down the pedal. And if we step back to design time, doubling the rate at which you can dump energy through an electric means increasing the cost by a tiny fraction of what it means for gas. Now, I have no idea which way they've gone with this one, but don't assume that because other hybrids go for efficiency that this one couldn't compete on performance if they wanted to. IIRC, the max power output for the EV1 was picked solely as a function of tire traction.
***Parent is Off Topic. this is too. moderate as you see fit***
You do not seem to understand the distinction between a bug and a suggestion. A bug is when the program is not behaving as designed. A suggestion is when you would like it to behave differently than designed. You have a suggestion and that's great. There are various apropriate forumns where suggestions are welcomed and debated. Bugzilla is not one of these. Bugzilla is a bug tracking database. Entering non-bugs is just adding noise, and apropriately generates the same feelings and reactions as spam or telemarketing.
Sounds good to me. Actually the way I've typically used this is in a module where the header only exposes static functions. The implementaion of these functions then call members of the singleton. This lets the object in question do what ever it needs to (one-time initialization, internal cacheing) without the caller having to even know it exists.
Slashdot Mirror
The point I was trying to make is that if my resume somehow got to the resumatic, it would rank me very low, and I wouldn't get considered. That's cool with me because the resumatic is used by large corporations, which I hate working for. My advice was about how to get a job at a small company. It's the only advice I can offer, as it's the only type of job I've enjoyed, and it's the only place I've read resumes (and cover letters, which are far more important than the resume in getting an interview with me)
Perhaps people would apreciate your insight more if you gave some indication what the hell you're talking about. For example a google seach on "important persons act" still leaves me clueless. Care to explain, or is this just random trolling babble?
Do like it? Why aren't you petitioning the Supreme Court to let you have nukes? Ensuring that the populace at large have access to sufficient weaponry to resist the government and/or foriegn invaders if they find it neccesary, while a fine thing in 1783, is not really workable today. While it would make a lot of sense to repeal the second ammendment, the bill of rights is such a sacred cow today, it would be political suicide to suggest. It is clearly unconstitutional to not allow citizens of the US to have any weapon they please, right up into the multi-megaton range. Watching psychos nuke our cities for the sake of this principle would obviously be idiotic, so we ignore the principle to a certain degree. The question is what degree makes sense. All of which is not to say that I don't find this troubling. The "sacred" staus accorded the Bil of Rights is great for protecting basic, needed freedoms, but it prevents us from removing the obviously out of date second amendment. Those who wrap themselves in the second amendment to protect their right to a handgun should wake up. That pea-shooter is worht diddly-squat when the army comes after you, and you can't have something that isn't. The second is already dead.
"Software does exist, or can be contracted out"
That sounds a hell of a lot like "in due time". Open source rules, and is an inherently better way to develop software, but I see the folowing conversation all the time:
Zealot: You don't need proprietary software, convert to Free software today!
User: What about aplication FOO?
Zealot: Use open source program BAR instead!
User: But it desen't do x, y and z.
Zealot: But project BAZ is making great strides! when it's done, BAR will integrate with it and all you problems will be solved. Convert Today!
User: You're an idiot.
Clue time:
coming soon != available now,
and for the vast majority of us,
almost as good, but Free == not as good
"tic-tac-toe, that game on a 3x3 grid played with X's and O's and you try to get 3 in a row. Isn't it proven that when any experienced players play the best result is a draw?"
Yes. Furthermore you can define "experienced" as "not a jibbering idiot". My 2 year old can play perfect tic-tac-toe.
Alright try this: My grandfather was Jewish, but neither I nor any ancestor for 100+ years have ever lived in Israel. My friends (palestinian) parents were born in Israel. Israeli law gaurantees me the right to become a citizen and live in Israel if I choose, but my friend would not be allowed off the plane. Explain how this is anything but atrociously racist.
I'm certainly no fan of the BSA, and being "happy" about an audit is certainly a stretch; but if they showed up where I work and wanted to know who was using what and see licenses for every copy, it would be no problem. We'd point them to the file cabinet in our IT guys office and say "knock yourself out".
If figuring out who is using what and finding the licenses is a problem for you, that tells me you're not already tracking it. Which means you don't really know if you're legal. Which means, frankly, you're probably not.
Doh! Thanks for the correction.
"I am sure that I don't have all the facts."
Like the fact that South Africa and Rwanda aren't the same country perhaps?
Whether you strongly doubt it or not, it has, does and will happen all the time. If Canada (for example) presents the US with convincing evidence you murdered someone in Canada, you'll be on the bus right quick. It's known as extradition, and the US has treaties covering it with most countries. They certainly vary in the crimes covered and the evidence required, but never "surrender a citizen"? Wouldn't count on it.
"the second approach has gotten me more interviews, the job of a resume and cover letter."
But are they interviews for jobs you really want and are particularly well suited to? That you research the companies is great, you're way ahead of the masses. But the point of the research should be to reject companies that aren't a good match, and not even bother sending them a resume. All that said, the lots of resumes approach may be the way to go with big companies. I wouldn't know, I hate big companies. For small companies, or at least the one I'm now at (and occasionally read resumes for) a customized resume is essential. Just to throw in my own appocryphal (sp?) evidence- My last job hunt lasted a month and I wound up with a job I love. I sent out exactly one resume after spending a day and a half on the cover letter. The cover letter detailed why this was the perfect job for me, and I the perfect candidate for the job well enough that my boss has since admitted he didn't read my resume until after arranging the interview.
I'd agree about dropping anything that identifies your religion. Not because I have anything against Mormons, but because anyone who puts their religion on their resume is likely to babble on about it in other irrelevant contexts, which drives me up the wall. I don't care what religion it is. I mean I really, really don't care, and putting it on your resume tells me you're the type who's going to insist I should.
Perhaps you've heard of this tech bubble bursting thing there's been all this talk about? The demand for tech workers may not be as strong today as two years ago.
Well, lets see, I started out with the same dillemma and got my experience doing what... Oh, I remember! Grunt work for a little more than minimum wage.
Seriously though, try to find grunt work that's sorta-kinda-maybe related to what you want to do, and keep at it. Also try to concentrate on what you want to do (i.e. enjoy and are good at) If you try to go for something you don't actually like in hopes of bucks, you'll wind up sucking at it and won't get the bucks.
Nearly impossible? Are you under the impression there are any rules whatsoever for what must be listed on a resume? Summarize! When I'm reading resumes, if it's not listed on the first page, it's not there. Do you have experience with every database system ever concieved of? Great, say that; don't waste my time listing them. Admittedly, this approach will not serve you as well if the job is with a company scanning resumes with a computerized buzzword-finder or it's human equivalent, the HR drone. I consider that OK, because I don't want that job.
Yes! You just made my "read the whole thing" pile while the other 95% that sent me the same resume they sent everyone else went straight to the trash can. Ideally, I'd be slightly more subtle, but not so much that they don't get the point: You've spent at least a small amount of time thinking about whether this job is right for you. To those that send out any more than 10 resumes a day, I say this: If you can't spend the time to figure out if the position I've got is right for you, why should I? Both of my last two job hunts were highly successful (great jobs found quickly). In both of them combined, how many resumes did I send out? Three.
"How does anyone stand a chance in what has become more a game of chance than skill?"
4 things:
1. Be very picky about the jobs you aplly for. Only send resumes to the ones that are a very good match.
2. Cover Letter
3. Cover Letter
4. Cover Letter
As for the automated HR systems, they'll reject my resume every time. I consider this a feature.
Yes and no. A good cover letter, telling me why you want the specific job you're applying for is the best thing you can do, hands-down. Unfortunately, in some cases (particularly when the incoming resume stack is five-miles tall) cover letters get ditched. So my advice is that in addition to a good coverletter, you should include an objective, and make it a two-line cover letter. i.e. customize it every time, and tell me why this job is particularly well suited to your goals. A general (boilerplate) objective is crap. (Well, crap to you, gold to me - I can trash your resume in minimum time!)
Couldn't agree more. There is zero chance I will look past the first page of a resume. If it's over three, I'll probably trash it on that basis alone. I don't care about every job you've ever had. In my first pass, I'm not even looking at your experience directly at all. I'm looking solely to find out if you are after *this* job or after *any* job. A well stated objective can make this instantly clear. Once I've got the 10% who are actually interested specifically in the job I'm offering, almost all of them will have acceptable levels of experience anyway. I may be unusual in that if I'm hiring, for example, a database guy, having worked with the exact RDBMS we use is a very minor bonus at best. I'm mainly looking for someone who is genuinely excited about data (It still shocks me that they exist, but that's a different issue)
Regarding dropping two balls from the tower, the big reason Galileo is thought not to have actually done it is that it would not have worked! Assuming two balls of equal size, but significantly unequal mass, air resistance will cause the heavy ball to hit the ground first, rather underwhelming the assemled crowd. In my opinion, Galileo's big achievement was managing to figure out inertia despite this.
HAHAHAHA!
That's so funny I've completely forgotten about all my positive experiences with MSSQL and about all the features I need that MySQL is lacking.
Well, you (and the other responder who noted it) are quite correct that tracking suggestions as "enhancement" severity bugs is entirely appropriate. The bug in question, however, is marked "blocker". It looks to me like this very issue was the subject of extensive disscussion, after which a decision was made, and implemented. Someone didn't like that decision, so they entered their view as a bug, got rightly slammed, and now they're complaining about it in other inapropriate places (this thread).
Your assumption that hybrids are necessarily lacking in power is way off. Hybrids are generally targeted toward efficiency more than performance yes. But if it's quick response to the accelerator you wan't, an electric motor is the end-all-be-all. A gas motor must rev up to the power level you ask for (assuming it's big enough to provide it). An electric motor will go from 0 to max torque as fast as you can push down the pedal. And if we step back to design time, doubling the rate at which you can dump energy through an electric means increasing the cost by a tiny fraction of what it means for gas.
Now, I have no idea which way they've gone with this one, but don't assume that because other hybrids go for efficiency that this one couldn't compete on performance if they wanted to.
IIRC, the max power output for the EV1 was picked solely as a function of tire traction.
***Parent is Off Topic. this is too. moderate as you see fit***
You do not seem to understand the distinction between a bug and a suggestion. A bug is when the program is not behaving as designed. A suggestion is when you would like it to behave differently than designed. You have a suggestion and that's great. There are various apropriate forumns where suggestions are welcomed and debated. Bugzilla is not one of these. Bugzilla is a bug tracking database. Entering non-bugs is just adding noise, and apropriately generates the same feelings and reactions as spam or telemarketing.
Sounds good to me.
Actually the way I've typically used this is in a module where the header only exposes static functions. The implementaion of these functions then call members of the singleton. This lets the object in question do what ever it needs to (one-time initialization, internal cacheing) without the caller having to even know it exists.