Ron Paul owns his likeness. Just because you've been playing in his playground and making improvements for the past 5 years doesn't mean you own it. It was his from the start.
Now he's asked you to decamp. Perhaps that's rude and abrupt, but guess what? It never was yours. All that effort of yours? You donated it. If that donation proves to have been to someone unworthy, well, that's the way cookie crumbles.
If you want to own it, play in your own playground instead of someone else's.
Impressive. And there's every reason to believe that more such work will eventually yield a theory of evolution that's actually solid. But frankly it reads like Lenski's experiments are only now approaching the level of Edison's experiments with electricity. Get far enough past that to do the evolutionary equivalent of building a transistor and I'll call whatever is then the theory of evolution, "good."
Until then, students deserve to know that they're hearing Edison-level theory. Not wrong, and certainly not without value, but very very incomplete.
Relativity is a testable theory. It tells me that light will usually go in a straight line. It also tells me that if light travels near a very large mass, it will curve. I can then go out and observe light curving around a large mass. And the curve I measure will match the curve relativity predicted.
Evolution can't tell me what conditions to subject rats to so that I end up with something that isn't a rat. And it can't tell me how many generations it'll take. Evolution can't tell me where to dig to find a creature whose bones are part way between a form believed to be a descendent of another. And it can't reliably tell me what those bones will look like when I do find them.
That's a neat trick. Display messages before the kernel starts scheduling me *and* after the kernel stops running me too. You did say the console was implemented in *user space*, right?
Perhaps "all sides" means diligently pointing out flaws in the theory where behavior is observed but not adequately understood. Punctuated equilibrium, missing link, I'm looking at the two of you in particular.
Evolution is the only theory for how species came to be as they are which is both credible *and* scientific. But it isn't a very good theory. If it was a good theory then it would be *testable*. One could use it to make reliable predictions about generational change in short lived animals based on whatever the factors are that induce change.
But it's not fully fledged.... it doesn't provide two of the three features I need in a text console: kernel diagnostic messages prior to the start of user space and kernel diagnostic messages following a crash.
From the study: In the super flight condition, participants controlled their flight through the VR environment. In the two helicopter conditions, participants were merely told that they were to be a passenger in a helicopter and their task would be explained once immersed in virtual reality. Their field of view varied only as a function of their head movements (i.e., they did not control translation of the helicopter but could look around the vehicle and out the window). Both flights were through an empty, generic city.
When the researcher dropped his pens, one participant had been actively flying through a VR environment, choosing where to go and going there, for several minutes. The other had been passively seated, with no control over the avatar except to look around.
So, the folks who had just been active moments before continued to be active, assisting with the dropped pens while the folks who had just been passive moments before continued to be passive, observing the researcher as he retrieved the dropped pens.
Had the study been fliers versus walkers with both in control of the avatars, I bet the study results would have shown identical helping behavior.
Yes, I should probably have mentioned that I'm hiring for creative roles. I have no work for an admin who can't script and little work for a coder who can't find his way around Linux.
The only hiring recommendation I regret is the very first one I made. I don't regret it much because we hired the guy anyway. I thought he was way overqualified for the job. I was wrong: the job adapted. As it always will if your employer doesn't suck. Hire the best people you can get and let the division of responsibilities sort themselves out later.
I've seen some places put a payback requirement on the reimbursement if you leave within 6 to 12 months.
Generally, though, if you treat the employees well and have interesting work for them, you won't lose them. And if you're likely to lose them after, it'll be obvious in their attitude before you make the investment.
Think of it like buying off ebay: sure, some small percentage of the transactions will be fraudulent. You come out so far ahead on the ones that aren't that it doesn't matter.
They won't help for a programming job. I've hired programmers, and give absolutely no weight to someone who has done server maintenance. I've hired network admins, and give little to no weight to someone who has done VB or C#, without OS experience.
I never finished my degree as my original university seemed to delight in messing with my finances and withholding books
And you didn't persevere.
All universities "mess with you" in arbitrary ways. Funny thing is, even if you're lucky enough to have a good direct boss, customers and senior management do that too.
As the employee becomes better at the job you give him raises and change his responsibilities to match. A lot of employers screw that up but if you genuinely want to keep the employee that's what you have to do -- regardless of *how* he got better at the work.
And you do want him better at the job. The guy who is twice as productive still only consumes one set of healthcare, one office, etc. If he wants to spend his unpaid time on coursework which will make him better at the job, paying for the tuition and books is a bargain.
1. I do look for a technical degree though not necessarily a CS degree. There's a certain maturity of the thinking process that rarely happens outside of college. Blind spots that you don't know are there. You won't get it chasing the problem du jour.
I will generally consider someone who is *finishing* a degree but I'll insist that the job be contingent on actually finishing. I'll generally offer enough scheduling flexibility to continue school. You're a programmer after all - I care about your results, not which hours you sit in the chair.
If you do have a CS or CE degree, try to have some basic knowledge about the field. I recently interviewed a guy with a CE degree who couldn't tell me that accessing a CPU register was faster than accessing main DRAM. Yet his senior project was in assembly language. The hell dude? Also, if you present yourself as God's gift to computer networking, you'd better be able to recognize a path MTU discovery problem when I describe the symptoms to you.
2. University of Phoenix, DeVry, Strayer and similar "degree mills" do carry a negative stigma. If your resume speaks of clue I'll ask for a phone interview anyway but presenting a degree from there speaks of poor judgement on the applicant's part. I'll be looking to refute my initial impression rather than confirm it. This is bad for you.
Same goes for presenting an associates degree from a community college. When you write your resume, you don't have a AS. You have a BS "in progress." Be ready to tell me where its in progress.
3. Certifications can be very bad. If you have one or two very strong certifications, like CCIE, they'll help you. Not much, far less than a degree, but they're a positive factor. I'm not every employer, but I'll never turn someone away for lack of a technical certification.
On the other hand, if you have 10 weak certifications (CCNA, MCSE, A+, Security+, etc.) and you list them all, that's a big negative. Huge. And the more you list the worse it is. I want self-starters. Doers do. They rarely bother with certifications and even if they do they have far more important things to tell me to sacrifice the space on their resume to such trivia.
I once had a network engineer applicant list his Kentrox CSU/DSU certification. A Kentrox CSU/DSU is usually configured with a few dip switches on the bottom. Roundfiled the resume.
4. Field-related stuff you do *for fun* outside of work is a huge plus. Contribute to an open source project? Run a sophisticated network in your basement? Hang out on any IETF mailing lists? Tell me all about it!
The current learning language for Computer Science is Java. It used to be Pascal. Switched to Java because of the importance of object oriented programming.
The language of choice for Linux/Unix system administration is Perl. Windows admins don't generally code though one of the dot-net's would likely be the choice if they did.
Pick one. Then buy a book and work through writing and running the example code. Then come up with an idea for a simple program you want to write. Then write it, referencing your books and Google search.
Baloney. If least cost routing were at fault VoIP services like Vonage would fail long before a rural telco. Whatever the problem is at Shoreham Telephone it has nothing to do with least cost routing and everything to do with their technical infrastructure and choice of direct vendors.
Of course. Maryland and DC aren't a right to work states so their unemployment hovers at 6.9% and 8.7% respectively. Virginia's is at 5.9%, despite the direct and indirect influx of massive amounts of federal dollars to all three.
The major difference is that the Internet industry settled in Northern Virginia ignoring Maryland's every attempt to lure it across the border. Of course there was more to that than right to work. In Virginia we sarcastically refer to our northern neighbor as the "People's Republic of Maryland" because they enact a lot of nanny-state laws, not just on employment.
Well, the mean hourly wage for employed folks in Virginia (right to work state, 5.9% unemployment) is $23.50 while the mean hourly wage in Michigan (not a right to work state, 9.3% unemployment) is $21.01.
If you feel like putting together a complete table, you can find the data at http://www.bls.gov/oes/current/oessrcst.htm. If I had to make a bet, I'd bet on the pool of unemployed workers dragging down the wage of employed workers so that there's a similar correlation between right to work and wages as there is between right to work and unemployment.
23 states are right to work. 27 states and DC are not.
The average of the unemployment rates listed at your source for states designated right to work is 7.07%
The average of the unemployment rates listed at your source for states NOT designated right to work is 7.82%
Of the 25 states with the lowest unemployment, 13 are right to work states. Of the 25 states with the highest unemployment, 10 are right to work states.
All five of the states with the lowest unemployment are right to work states and none of them see their primary income from tourism. Only two of the states with the highest unemployment are right to work states and one of them (Nevada) lives and dies on a tourism market that goes very soft in a bad economy.
Correlation is not necessarily causation, but there IS a pretty clear correlation between right to work and lower unemployment.
For example, Netflix has done a poor job with their Anime catalog. If you have a local demand for that genre there will be a couple stores who sell Anime DVDs alongside other Anime products. But most folks are happy to rent a disc for $2 rather than buy it for $20.
Create a web site linking your inventory. Allow customers to reserve and pay for disc rentals on the web site and then pick them up on the way home instead of having to hang around the store and either stand in the checkout line or find all copies of the desired movie out of stock.
The web inventory also allows you to warehouse less popular titles so that they're available but don't consume retail space. Long tail stuff.
Also start a policy: any disc you don't have in stock, you'll buy and rent out upon customer request. Only deal is the customer has to prepay the minimum rental before you'll order it. Place like Netflix can't handle that. They can stock a disc or not, but they can't have just one ad-hoc copy.
There's also a decent niche for buying and selling used DVDs instead of renting them. Sell that new movie for $20 and it's a guaranteed buyback at $18 if they return it in acceptable condition by the end of the week. After that you'll buy it at market value. This works decently well for video games too.
What kind of nutbags start a job without the protection of a collective bargaining agreement?
How about that, there is such a thing as a stupid question.
Answer #1: Any professional with any ambition at all. Collective bargaining agreements are a noose around the neck of anybody with the ambition to better themselves.
Answer #2: Any unskilled employee who'd like to have a paycheck if they live in a right to work state where "at will" employment predominates. Which unsurprisingly happens to be the states with the lowest unemployment rates right now.
Now how do we change this status-quo to something better and remove this blasted vendor lock-in?
Like I said earlier in the thread: you subsume the status-quo format and support its quirks all the way in and out of your core.
X86 didn't win because it was the best. X86 won because it ran the software folks wanted to run. If you want to compete in that market, your product will successfully run everything a genuine x86 processor runs.
That or you'll start in an entirely new market (smartphones) where there is no initial expectation of cross-over and then incrementally cross over.
Slashdot Mirror
Ron Paul owns his likeness. Just because you've been playing in his playground and making improvements for the past 5 years doesn't mean you own it. It was his from the start.
Now he's asked you to decamp. Perhaps that's rude and abrupt, but guess what? It never was yours. All that effort of yours? You donated it. If that donation proves to have been to someone unworthy, well, that's the way cookie crumbles.
If you want to own it, play in your own playground instead of someone else's.
Impressive. And there's every reason to believe that more such work will eventually yield a theory of evolution that's actually solid. But frankly it reads like Lenski's experiments are only now approaching the level of Edison's experiments with electricity. Get far enough past that to do the evolutionary equivalent of building a transistor and I'll call whatever is then the theory of evolution, "good."
Until then, students deserve to know that they're hearing Edison-level theory. Not wrong, and certainly not without value, but very very incomplete.
Relativity is a testable theory. It tells me that light will usually go in a straight line. It also tells me that if light travels near a very large mass, it will curve. I can then go out and observe light curving around a large mass. And the curve I measure will match the curve relativity predicted.
Evolution can't tell me what conditions to subject rats to so that I end up with something that isn't a rat. And it can't tell me how many generations it'll take. Evolution can't tell me where to dig to find a creature whose bones are part way between a form believed to be a descendent of another. And it can't reliably tell me what those bones will look like when I do find them.
So, what exactly does it predict?
That's a neat trick. Display messages before the kernel starts scheduling me *and* after the kernel stops running me too. You did say the console was implemented in *user space*, right?
Perhaps "all sides" means diligently pointing out flaws in the theory where behavior is observed but not adequately understood. Punctuated equilibrium, missing link, I'm looking at the two of you in particular.
Evolution is the only theory for how species came to be as they are which is both credible *and* scientific. But it isn't a very good theory. If it was a good theory then it would be *testable*. One could use it to make reliable predictions about generational change in short lived animals based on whatever the factors are that induce change.
But it's not fully fledged.... it doesn't provide two of the three features I need in a text console: kernel diagnostic messages prior to the start of user space and kernel diagnostic messages following a crash.
From the study: In the super flight condition, participants controlled their flight through the VR environment. In the two helicopter conditions, participants were merely told that they were to be a passenger in a helicopter and their task would be explained once immersed in virtual reality. Their field of view varied only as a function of their head movements (i.e., they did not control translation of the helicopter but could look around the vehicle and out the window). Both flights were through an empty, generic city.
When the researcher dropped his pens, one participant had been actively flying through a VR environment, choosing where to go and going there, for several minutes. The other had been passively seated, with no control over the avatar except to look around.
So, the folks who had just been active moments before continued to be active, assisting with the dropped pens while the folks who had just been passive moments before continued to be passive, observing the researcher as he retrieved the dropped pens.
Had the study been fliers versus walkers with both in control of the avatars, I bet the study results would have shown identical helping behavior.
The republicans run Windows. the GOTV code from the Obama campaign would be unusable to them.
Hear hear! You can shoot that burglar just as soon as you get a GPS fix. Any minute now...
As you say, you all know the certifications are junk. Do you *want* to work for an employer who thinks they're the bee's knees?
Target your resume to the kind of employer to *want* to work for. Tell him the things about you that *he* is likely to consider important.
If you *want* to work for an employer who places high stock in certifications, you won't be happy working for me.
Yes, I should probably have mentioned that I'm hiring for creative roles. I have no work for an admin who can't script and little work for a coder who can't find his way around Linux.
The only hiring recommendation I regret is the very first one I made. I don't regret it much because we hired the guy anyway. I thought he was way overqualified for the job. I was wrong: the job adapted. As it always will if your employer doesn't suck. Hire the best people you can get and let the division of responsibilities sort themselves out later.
I've seen some places put a payback requirement on the reimbursement if you leave within 6 to 12 months.
Generally, though, if you treat the employees well and have interesting work for them, you won't lose them. And if you're likely to lose them after, it'll be obvious in their attitude before you make the investment.
Think of it like buying off ebay: sure, some small percentage of the transactions will be fraudulent. You come out so far ahead on the ones that aren't that it doesn't matter.
They won't help for a programming job. I've hired programmers, and give absolutely no weight to someone who has done server maintenance. I've hired network admins, and give little to no weight to someone who has done VB or C#, without OS experience.
That's a mistake. Read up on "devops."
I never finished my degree as my original university seemed to delight in messing with my finances and withholding books
And you didn't persevere.
All universities "mess with you" in arbitrary ways. Funny thing is, even if you're lucky enough to have a good direct boss, customers and senior management do that too.
As the employee becomes better at the job you give him raises and change his responsibilities to match. A lot of employers screw that up but if you genuinely want to keep the employee that's what you have to do -- regardless of *how* he got better at the work.
And you do want him better at the job. The guy who is twice as productive still only consumes one set of healthcare, one office, etc. If he wants to spend his unpaid time on coursework which will make him better at the job, paying for the tuition and books is a bargain.
Speaking as an employer...
1. I do look for a technical degree though not necessarily a CS degree. There's a certain maturity of the thinking process that rarely happens outside of college. Blind spots that you don't know are there. You won't get it chasing the problem du jour.
I will generally consider someone who is *finishing* a degree but I'll insist that the job be contingent on actually finishing. I'll generally offer enough scheduling flexibility to continue school. You're a programmer after all - I care about your results, not which hours you sit in the chair.
If you do have a CS or CE degree, try to have some basic knowledge about the field. I recently interviewed a guy with a CE degree who couldn't tell me that accessing a CPU register was faster than accessing main DRAM. Yet his senior project was in assembly language. The hell dude? Also, if you present yourself as God's gift to computer networking, you'd better be able to recognize a path MTU discovery problem when I describe the symptoms to you.
2. University of Phoenix, DeVry, Strayer and similar "degree mills" do carry a negative stigma. If your resume speaks of clue I'll ask for a phone interview anyway but presenting a degree from there speaks of poor judgement on the applicant's part. I'll be looking to refute my initial impression rather than confirm it. This is bad for you.
Same goes for presenting an associates degree from a community college. When you write your resume, you don't have a AS. You have a BS "in progress." Be ready to tell me where its in progress.
3. Certifications can be very bad. If you have one or two very strong certifications, like CCIE, they'll help you. Not much, far less than a degree, but they're a positive factor. I'm not every employer, but I'll never turn someone away for lack of a technical certification.
On the other hand, if you have 10 weak certifications (CCNA, MCSE, A+, Security+, etc.) and you list them all, that's a big negative. Huge. And the more you list the worse it is. I want self-starters. Doers do. They rarely bother with certifications and even if they do they have far more important things to tell me to sacrifice the space on their resume to such trivia.
I once had a network engineer applicant list his Kentrox CSU/DSU certification. A Kentrox CSU/DSU is usually configured with a few dip switches on the bottom. Roundfiled the resume.
4. Field-related stuff you do *for fun* outside of work is a huge plus. Contribute to an open source project? Run a sophisticated network in your basement? Hang out on any IETF mailing lists? Tell me all about it!
The current learning language for Computer Science is Java. It used to be Pascal. Switched to Java because of the importance of object oriented programming.
The language of choice for Linux/Unix system administration is Perl. Windows admins don't generally code though one of the dot-net's would likely be the choice if they did.
Pick one. Then buy a book and work through writing and running the example code. Then come up with an idea for a simple program you want to write. Then write it, referencing your books and Google search.
Baloney. If least cost routing were at fault VoIP services like Vonage would fail long before a rural telco. Whatever the problem is at Shoreham Telephone it has nothing to do with least cost routing and everything to do with their technical infrastructure and choice of direct vendors.
Of course. Maryland and DC aren't a right to work states so their unemployment hovers at 6.9% and 8.7% respectively. Virginia's is at 5.9%, despite the direct and indirect influx of massive amounts of federal dollars to all three.
The major difference is that the Internet industry settled in Northern Virginia ignoring Maryland's every attempt to lure it across the border. Of course there was more to that than right to work. In Virginia we sarcastically refer to our northern neighbor as the "People's Republic of Maryland" because they enact a lot of nanny-state laws, not just on employment.
Well, the mean hourly wage for employed folks in Virginia (right to work state, 5.9% unemployment) is $23.50 while the mean hourly wage in Michigan (not a right to work state, 9.3% unemployment) is $21.01.
If you feel like putting together a complete table, you can find the data at http://www.bls.gov/oes/current/oessrcst.htm. If I had to make a bet, I'd bet on the pool of unemployed workers dragging down the wage of employed workers so that there's a similar correlation between right to work and wages as there is between right to work and unemployment.
Challenge accepted.
Unemployment rates by state:
http://www.bls.gov/web/laus/laumstrk.htm
Right to work states:
http://www.nrtw.org/rtws.htm
23 states are right to work. 27 states and DC are not.
The average of the unemployment rates listed at your source for states designated right to work is 7.07%
The average of the unemployment rates listed at your source for states NOT designated right to work is 7.82%
Of the 25 states with the lowest unemployment, 13 are right to work states. Of the 25 states with the highest unemployment, 10 are right to work states.
All five of the states with the lowest unemployment are right to work states and none of them see their primary income from tourism. Only two of the states with the highest unemployment are right to work states and one of them (Nevada) lives and dies on a tourism market that goes very soft in a bad economy.
Correlation is not necessarily causation, but there IS a pretty clear correlation between right to work and lower unemployment.
Got anything else to say clever guy?
Yep. Create a niche.
For example, Netflix has done a poor job with their Anime catalog. If you have a local demand for that genre there will be a couple stores who sell Anime DVDs alongside other Anime products. But most folks are happy to rent a disc for $2 rather than buy it for $20.
Create a web site linking your inventory. Allow customers to reserve and pay for disc rentals on the web site and then pick them up on the way home instead of having to hang around the store and either stand in the checkout line or find all copies of the desired movie out of stock.
The web inventory also allows you to warehouse less popular titles so that they're available but don't consume retail space. Long tail stuff.
Also start a policy: any disc you don't have in stock, you'll buy and rent out upon customer request. Only deal is the customer has to prepay the minimum rental before you'll order it. Place like Netflix can't handle that. They can stock a disc or not, but they can't have just one ad-hoc copy.
There's also a decent niche for buying and selling used DVDs instead of renting them. Sell that new movie for $20 and it's a guaranteed buyback at $18 if they return it in acceptable condition by the end of the week. After that you'll buy it at market value. This works decently well for video games too.
What kind of nutbags start a job without the protection of a collective bargaining agreement?
How about that, there is such a thing as a stupid question.
Answer #1: Any professional with any ambition at all. Collective bargaining agreements are a noose around the neck of anybody with the ambition to better themselves.
Answer #2: Any unskilled employee who'd like to have a paycheck if they live in a right to work state where "at will" employment predominates. Which unsurprisingly happens to be the states with the lowest unemployment rates right now.
Now how do we change this status-quo to something better and remove this blasted vendor lock-in?
Like I said earlier in the thread: you subsume the status-quo format and support its quirks all the way in and out of your core.
X86 didn't win because it was the best. X86 won because it ran the software folks wanted to run. If you want to compete in that market, your product will successfully run everything a genuine x86 processor runs.
That or you'll start in an entirely new market (smartphones) where there is no initial expectation of cross-over and then incrementally cross over.
You are mistaken. The frequency which which *business* people create or view power point presentations is quite high.