Employers are paying $395 for inaccurate results, and job seekers are paying for a feature that can hurt their chances of getting an interview, much less the job, because employers can’t trust the results before them, and no one can turn any of this off for the sake of accuracy.
So job seekers pay for top billing, and the employer knows the top applicants paid for their positions because their names are highlighted and have a little badge beside them. (Wink, wink! You paid, but employers know you’re not really the top applicant!)
Ask The Headhunter: Is LinkedIn Cheating Employers and Job Seekers Alike?
I have had an off-and-on relationship with LinkedIn over the years, currently off (and likely to stay that way) given their recent spate of security problems. If job prospects on LinkedIn were more lucrative, I’d probably be convinced to stay. But as noted in the article I am not going to spend $150 just to go fishing, and I refuse to play a game with such questionable integrity baked in like that. No wonder I only ever got called upon by sales reps selling me services of which I had no use, which would have been apparent if they had taken the time to actually read my job history.
There are a number of reasons why I moved away from using RapidWeaver to WordPress.
The primary one is that I need to flex my web skills regularly in such a way that RapidWeaver didn’t allow. I can tweak WordPress at a very low level whereas RapidWeaver keeps things at a very high, GUI level.
I also wanted to resurrect the blog, but RapidWeaver’s built-in blog tool doesn’t really suit my needs. I had to have RapidWeaver installed and running to post, but with WordPress I can manage the site from anywhere. I didn’t want a separate blog site where the designs didn’t match (or rather, I didn’t want to take the time to tweak the designs to match).
None of the above is to say that I don’t like RapidWeaver; I still use RapidWeaver for another ongoing project. I think I just wanted to add something new to the mix, so WordPress since it is new to me.
Oatmeal & Coffee is owned and operated by Philip Regan.
Applescript, Objective-C, and their variants are the main topics found on this site, mainly in the form of my favorite code snippets from my personal wiki. I post them in the hopes that they will help someone out of similar jams I have found myself in after I had found documentation seen elsewhere lacking for whatever reason. Some large and mostly complete projects have been placed on GitHub for others’ use and enjoyment.
Beyond that, there is also my resume and some obligatory legal jargon. Below is a copy of my usual avatar for the online forums I frequent to varying (usually lesser) degrees and elsewhere a picture of a shoe. The shoe is important.
Anyone is welcome to contact me (an email address is casually hidden in the Legal page) with comments and questions.