Sounds like it might be a good time to start a new career focused social network.
Integrating Microsoft and LinkedIn
61–70 of 75 posts
Re: Integrating Microsoft and LinkedIn
#62Earlier quoted context omitted.
Just a pet peeve, but please re-consider the casual use of the word "poach" when referring to companies hiring employees. It reduces a worker's agency to that of a farm animal or wild game, as if they were owned by their employer and "stolen" away by some other employer. I think we can all agree that we are not the property of our employers, so the word "poach" is pretty inappropriate and I'd argue moderately offensi…
I'd argue moderately offensive. I was deliberately and enthusiastically nodding with the "we are not the property of our employers" bit. Then you dropped the O-word and now, mostly because I'm curious to the point of disaster, I think I actually kind of need to see one argue that 'poach' is carte-blanche "offensive".
"Offensive" was probably a bad choice. "Uncomfortable" maybe?
Re: Integrating Microsoft and LinkedIn
#63Earlier quoted context omitted.
I'd argue moderately offensive. I was deliberately and enthusiastically nodding with the "we are not the property of our employers" bit. Then you dropped the O-word and now, mostly because I'm curious to the point of disaster, I think I actually kind of need to see one argue that 'poach' is carte-blanche "offensive".
"Offensive" was probably a bad choice. "Uncomfortable" maybe?
But how? As another commenter accurately pointed out, it's a perfectly cromulent word to describe the act
Re: Integrating Microsoft and LinkedIn
#64Earlier quoted context omitted.
"Offensive" was probably a bad choice. "Uncomfortable" maybe?
But how? As another commenter accurately pointed out, it's a perfectly cromulent word to describe the act
Hard to describe. I'm as uncomfortable with the word as I am uncomfortable being referred to as a "resource" which is also used commonly in business. Personal pet peeve, probably not shared by many.
Re: Integrating Microsoft and LinkedIn
#65Earlier quoted context omitted.
But how? As another commenter accurately pointed out, it's a perfectly cromulent word to describe the act
Hard to describe. I'm as uncomfortable with the word as I am uncomfortable being referred to as a "resource" which is also used commonly in business. Personal pet peeve, probably not shared by many.
Interesting. I wont belabor the affair. The relationship some have with words is an interesting one to me, more so lately than ever.
Re: Integrating Microsoft and LinkedIn
#66Earlier quoted context omitted.
It's not really up to other firms though, it's up to the employees who see value in the social network.
Strictly speaking that's true. But employers have a fair amount of leverage, especially in terms of recruiting and what-not. I suspect a lot of people are on LI because it serves as a sort of default online resume, and if companies quit recruiting through LinkedIn and switch to something else, I think the users might follow. OTOH, maybe most people only use LI as an online Rolodex and maybe it'll all turn out to be a…
I think this is potentially an "if you build it" situation in the making. I mean, iirc, LI wasn't the "social network for recruiters" but it kind of turned into that... It's still a fairly poor fit, and while some of the posts on message boards are useful, most are spam.
A more curated social recruiting site is a pretty big potential if one were built... I keep hoping that Stack Exchange will move their careers stuff more in that direction, as they've been one of the better options imho as a developer, but they just don't have the critical mass even in the niche of IT.
Frankly, all the job sites suck... any number of them could make the move to a better UX for all concerned, but part of that really needs to be the empowerment of saying, "Hey, I'm not looking and have been where I am less than a half a year, let me be." That's another thing I wouldn't mind seeing... a place to post your resume, your phone number and email address... A recruiter could put in your email address, or phone number, and it give them your current status, the latest resume and that's it... just an update mechanism to avoid contacting people who'd rather not be bothered. Then they could pay for a hot feed when a resume gets updated, and/or someone marks themselves as passively looking, etc.
I think it comes down to more quality engagement on both sides... It gets tiring to get the constant phone calls for 3 months after starting something, and 3-9 months away from your project coming to an end... that doesn't even consider the FTE-types that will stay somewhere for several years before considering a move.
Re: Integrating Microsoft and LinkedIn
#67The coming feature list, from the article: * LinkedIn identity and network in Microsoft Outlook and the Office suite * LinkedIn notifications within the Windows action center * Enabling members drafting résumés in Word to update their profiles, and discover and apply to jobs on LinkedIn * Extending the reach of Sponsored Content across Microsoft properties * Enterprise LinkedIn Lookup powered by Active Directory and…
The online stuff from MS is pretty compelling... even though the hosted version isn't quite as good as onsite Exchange, it's still one of the better integrations of an enterprise email + calendar option out there... and the skype for enterprise integration could still be a little better.
I think the web options for office will probably be good enough for most, which is why they pushed that way in light of the google docs properties. This is where the money will be made for MS in the next decade to be sure.
Re: Integrating Microsoft and LinkedIn
#68Earlier quoted context omitted.
Just a pet peeve, but please re-consider the casual use of the word "poach" when referring to companies hiring employees. It reduces a worker's agency to that of a farm animal or wild game, as if they were owned by their employer and "stolen" away by some other employer. I think we can all agree that we are not the property of our employers, so the word "poach" is pretty inappropriate and I'd argue moderately offensi…
Use "lure" ... no, that implies that employees are like rodents. Next time try "propositioned"... no that's for whores. This is tough stuff.
Entice.
Re: Integrating Microsoft and LinkedIn
#69Earlier quoted context omitted.
Just a pet peeve, but please re-consider the casual use of the word "poach" when referring to companies hiring employees. It reduces a worker's agency to that of a farm animal or wild game, as if they were owned by their employer and "stolen" away by some other employer. I think we can all agree that we are not the property of our employers, so the word "poach" is pretty inappropriate and I'd argue moderately offensi…
Are you going to suggest a better term?
How about "employ"? :)
Re: Integrating Microsoft and LinkedIn
#70Given the hue and cry Salesforce made to try and block the acquisition from going through, I suspect an integration with Dynamics as well.