Yeah, I still feel like you're misreading me in a strange way. The first three words are 'Soft skills like...'. The stuff that follows is an attempt to enumerate some examples in case someone doesn't understand what a soft skill is. I'd still say that reads as perfectly clear to me.
For the definition of friend, I'm happy with 1a, 1b, 2a, and 4. If you don't have anyone at work who meets one of those, I think it's a problem. Heck, if you don't have anyone at work who doesn't meet at least 2 of those, it is going to be a problem working in a more highly socialized setting.
Yeah, as I suggested before, I think the use of 'friend' caused more controversy than it was worth. Some people have too strict a definition of 'friend' (though webster [http://www.merriam-webster.com/dictionary/friend] favors me). The focus of my post was in fact intended to be on the question of whether or not you could get people to link-in you as a proxy for soft skills in general: call it the ability to be tolerably liked at work, rather than the ability to make friends if you prefer. Even on rereading I think I can make a reasonably justified claim that that was in fact pretty clear.
Where does your heat from the ducts GO? You reach the surface of the device, and now you still have 1000 times the heat to dissipate that you had trouble dissipating with fans/heatsinks/liquid cooling already. And that assumes you can do a PERFECT job of reaching the surface of the device with your strategy.
Yes, it's non trivial. Such a gap would have to be more than a few air molecules wide to allow free flow (avoid turbulence against the edges). This would make the size of your third dimension grow much faster, negating a lot of the proposed benefit in terms of Moore's law scaling. Also, existing air-flow dissipation strategies just wind up heating the nearby air, and trying to dispose of that heat, which means we'd still have a growing problem to deal with... so even if we've gotten the heat an inch away from the device with this strategy, we still have a thousand times as much heat in that inch to get even further away from the computer!
We're growing rapidly. We're hiring more than 30 new developers per year. Our turnover is quite low, about 3 per year.
And the only statistics I gave were: average age : easy to calculate, and reasonably accurate on any population over size 20. capability : mostly subjective, and I'm aware of that, but realistically I'm unlikely to be significantly wrong.
That's not at all true. A lot of the technologies that have succeeded have been invented in the commercial labs, where people care about productizability. I think the criticism here is aimed at the university labs, where people invent stuff using outrageous amounts of money that is difficult or impossible to commercialize.
We don't just go vertical without solving the heat dissipation problem. We already have a hard time dissipating the heat off the surface area of one layer. Now imagine trying to dissipate the heat off of the layer that is trapped between two more layers also generating the same amount of problematic heat. Then try to figure out how to dissipate the heat off a thousand layers to buy you just 10 more years of Moore's law.
I don't understand what you're trying to convey in either half of that. Whether it is 'friends' or not seems like semantics to me: the original question which started this thread was about whether or not linkedin-edness was a valid proxy for some kind of social skill with real value to employers. Nothing said here has shifted my opinion on that even a little bit. If you can't get anyone you've worked with to linked-in you, there is something really odd going on there. Odd enough to worry about in a highly social workplace.
As to whether every HR department would benefit from having an introvert... I don't understand what benefit you are claiming they would derive, so I don't really have an opinion to offer you on that.
I think there's a credible difference between an evolving platform in use at hundreds of companies with an active open source community behind it and one that has no serious ongoing development and that hasn't had anything going on in over twenty years.
If your only skillset is something that hasn't had any new development going on in over twenty years, and you no longer have the brain flexibility to learn something new in time for an interview, you are going to have a hard time getting a job.
Finally: Oracle vs Google is only scaring the stupid. The java licensing is clear, Google's violations of that are what are getting them into trouble. Almost no one else is doing anything remotely risky on the Java platform.
If all you care about is up, rather than what you do, I'm pretty sure what you're looking for is (the presumably british equivalent of) an MBA (business degree) from a working nights program.
Then you can move up into the management layer of any mid-sized or larger company. For you, probably, the larger the better. More opportunities to move up by doing nothing but socializing and taking credit for the work of others.
If you socialize at the workplace and can't convince the people you socialize with to linked-in you, there is something seriously different about you. Serious enough to be a significant impediment in most mid to large size companies where socialization is more vital to getting things done. If that's the case, both sides of the equation will be happier if you stick to working for smaller companies that can cater to and benefit from your differences.
We want both, actually. And we've done a great job of hiring both. Our average age is probably well above industry norms as a result. But I can definitely see why SOME old people have a very hard time getting work.
Well... I got burned out working 85 hour weeks for three years, and retired from game development to do enterprise software development. Now I have a very enjoyable life working 40-45 hours/week, and plenty of time with my kid, etc. I've been in software for a total of 20 years now, and I'd say right now I'm charged up.
Well... be honest... why WEREN'T you working with the design committee on HTML5? Could it be... laziness? I have 5 years of HTML5 experience... so should you!
I would guess it is much harder to prove than race or religion. I mean seriously, we interview a lot of candidates. No one I have ever worked with expressed the thought that older people can't be competent in CS, whereas I have run into actual racists/religionists.
Older people don't get hired because: 1) They let their skill sets get out of date. We're hiring people currently skilled in java. I have seen some older people apply who only knew cobol, apparently, and weren't willing to learn enough java to pass a basic technical interview. 2) Older people can appear tired. We're hiring energetic people with enthusiasm for their work. If you can't even fake it the length of an interview....
I say all this headed for my 30th birthday and knowing the clock is ticking.
About the same, because (take your pick): the fp op rate shouldn't matter to this algorithm as far as I can tell. the fp op rate is the same in tesla/gtx480 (ignoring minor clock speed differences)
There are SOME slower consumer gtx cards, where the fp rate is 1/4 of the gtx480/tesla, but since those aren't in the picture...
It's not that the operations aren't equal cost that is the problem in real implementations, it's the number of them. E.g., if my O(n) sort requires a million instructions setup, and a few hundred per bucket assignment, that may significantly impact how it compares in performance to an O(n log(n)) sort that requires only a hundred instructions of setup, and 3 operations per swap.
Researchers at the University of Virginia have recently open sourced
I stopped this shit about right there. You think I'm going to trust my sorting to some open sores buggy shit? I think I'll just keep using Microsoft for my algorithms thank you very much.
I'm assuming that was an attempt at humor. Otherwise, you're going to get modded all to hell very soon.
Just ask yourself: could someone possibly actually hold this opinion? He was clearly joking.
Education is a wonder, really. Go learn. You don't have to be laughed at behind your back all your life. You don't have to live with people wondering if the problem is inbreeding forever. But again, most importantly, you don't have to suffer with this, the tools to end your misery are at your disposal. Many people aren't anywhere near so lucky, don't spit in the face of opportunity.
Slashdot Mirror
Yeah, I still feel like you're misreading me in a strange way. The first three words are 'Soft skills like ...'. The stuff that follows is an attempt to enumerate some examples in case someone doesn't understand what a soft skill is. I'd still say that reads as perfectly clear to me.
For the definition of friend, I'm happy with 1a, 1b, 2a, and 4. If you don't have anyone at work who meets one of those, I think it's a problem. Heck, if you don't have anyone at work who doesn't meet at least 2 of those, it is going to be a problem working in a more highly socialized setting.
True, that does help with the ssd, as long as you don't try to write too much data too fast.
Yeah, as I suggested before, I think the use of 'friend' caused more controversy than it was worth. Some people have too strict a definition of 'friend' (though webster [http://www.merriam-webster.com/dictionary/friend] favors me). The focus of my post was in fact intended to be on the question of whether or not you could get people to link-in you as a proxy for soft skills in general: call it the ability to be tolerably liked at work, rather than the ability to make friends if you prefer. Even on rereading I think I can make a reasonably justified claim that that was in fact pretty clear.
Where does your heat from the ducts GO? You reach the surface of the device, and now you still have 1000 times the heat to dissipate that you had trouble dissipating with fans/heatsinks/liquid cooling already. And that assumes you can do a PERFECT job of reaching the surface of the device with your strategy.
Yes, it's non trivial. Such a gap would have to be more than a few air molecules wide to allow free flow (avoid turbulence against the edges). This would make the size of your third dimension grow much faster, negating a lot of the proposed benefit in terms of Moore's law scaling. Also, existing air-flow dissipation strategies just wind up heating the nearby air, and trying to dispose of that heat, which means we'd still have a growing problem to deal with ... so even if we've gotten the heat an inch away from the device with this strategy, we still have a thousand times as much heat in that inch to get even further away from the computer!
We're growing rapidly. We're hiring more than 30 new developers per year. Our turnover is quite low, about 3 per year.
And the only statistics I gave were:
average age : easy to calculate, and reasonably accurate on any population over size 20.
capability : mostly subjective, and I'm aware of that, but realistically I'm unlikely to be significantly wrong.
Metamods: overrated unmoderated post.
That's not at all true. A lot of the technologies that have succeeded have been invented in the commercial labs, where people care about productizability. I think the criticism here is aimed at the university labs, where people invent stuff using outrageous amounts of money that is difficult or impossible to commercialize.
We don't just go vertical without solving the heat dissipation problem. We already have a hard time dissipating the heat off the surface area of one layer. Now imagine trying to dissipate the heat off of the layer that is trapped between two more layers also generating the same amount of problematic heat. Then try to figure out how to dissipate the heat off a thousand layers to buy you just 10 more years of Moore's law.
I don't understand what you're trying to convey in either half of that. Whether it is 'friends' or not seems like semantics to me: the original question which started this thread was about whether or not linkedin-edness was a valid proxy for some kind of social skill with real value to employers. Nothing said here has shifted my opinion on that even a little bit. If you can't get anyone you've worked with to linked-in you, there is something really odd going on there. Odd enough to worry about in a highly social workplace.
As to whether every HR department would benefit from having an introvert ... I don't understand what benefit you are claiming they would derive, so I don't really have an opinion to offer you on that.
Is that a drug reference or a sex reference ... I don't know it.
I think there's a credible difference between an evolving platform in use at hundreds of companies with an active open source community behind it and one that has no serious ongoing development and that hasn't had anything going on in over twenty years.
If your only skillset is something that hasn't had any new development going on in over twenty years, and you no longer have the brain flexibility to learn something new in time for an interview, you are going to have a hard time getting a job.
Finally: Oracle vs Google is only scaring the stupid. The java licensing is clear, Google's violations of that are what are getting them into trouble. Almost no one else is doing anything remotely risky on the Java platform.
Right, because java isn't a current technology in active use by hundreds of companies with a thriving open source community.
If all you care about is up, rather than what you do, I'm pretty sure what you're looking for is (the presumably british equivalent of) an MBA (business degree) from a working nights program.
Then you can move up into the management layer of any mid-sized or larger company. For you, probably, the larger the better. More opportunities to move up by doing nothing but socializing and taking credit for the work of others.
If you socialize at the workplace and can't convince the people you socialize with to linked-in you, there is something seriously different about you. Serious enough to be a significant impediment in most mid to large size companies where socialization is more vital to getting things done. If that's the case, both sides of the equation will be happier if you stick to working for smaller companies that can cater to and benefit from your differences.
We want both, actually. And we've done a great job of hiring both. Our average age is probably well above industry norms as a result. But I can definitely see why SOME old people have a very hard time getting work.
Well ... I got burned out working 85 hour weeks for three years, and retired from game development to do enterprise software development. Now I have a very enjoyable life working 40-45 hours/week, and plenty of time with my kid, etc. I've been in software for a total of 20 years now, and I'd say right now I'm charged up.
Well ... be honest ... why WEREN'T you working with the design committee on HTML5? Could it be ... laziness? ... so should you!
I have 5 years of HTML5 experience
I would guess it is much harder to prove than race or religion. I mean seriously, we interview a lot of candidates. No one I have ever worked with expressed the thought that older people can't be competent in CS, whereas I have run into actual racists/religionists.
Older people don't get hired because: ....
1) They let their skill sets get out of date. We're hiring people currently skilled in java. I have seen some older people apply who only knew cobol, apparently, and weren't willing to learn enough java to pass a basic technical interview.
2) Older people can appear tired. We're hiring energetic people with enthusiasm for their work. If you can't even fake it the length of an interview
I say all this headed for my 30th birthday and knowing the clock is ticking.
They cheat in the rasterization phase rather than in the setup phase, generally, so anything written in CUDA should be pretty safe.
About the same, because (take your pick):
the fp op rate shouldn't matter to this algorithm as far as I can tell.
the fp op rate is the same in tesla/gtx480 (ignoring minor clock speed differences)
There are SOME slower consumer gtx cards, where the fp rate is 1/4 of the gtx480/tesla, but since those aren't in the picture ...
Different ns.
It's not that the operations aren't equal cost that is the problem in real implementations, it's the number of them. E.g., if my O(n) sort requires a million instructions setup, and a few hundred per bucket assignment, that may significantly impact how it compares in performance to an O(n log(n)) sort that requires only a hundred instructions of setup, and 3 operations per swap.
Researchers at the University of Virginia have recently open sourced
I stopped this shit about right there. You think I'm going to trust my sorting to some open sores buggy shit? I think I'll just keep using Microsoft for my algorithms thank you very much.
I'm assuming that was an attempt at humor. Otherwise, you're going to get modded all to hell very soon.
Just ask yourself: could someone possibly actually hold this opinion?
He was clearly joking.
Education is a wonder, really. Go learn. You don't have to be laughed at behind your back all your life. You don't have to live with people wondering if the problem is inbreeding forever. But again, most importantly, you don't have to suffer with this, the tools to end your misery are at your disposal. Many people aren't anywhere near so lucky, don't spit in the face of opportunity.