172 karma · joined March 2, 2009
LinkedIn is probably a closer approximation to what's needed, but as far as I can tell it's hard to get far out of your acquaintances with a basic account.
To use the case of florist licensing to condemn all licensing is an egregious leap. In general I believe it is sound policy to license professions where the ordinary consumer of their services cannot be expected to know how to judge their quality. Highly specialized professions dealing with the general public such as doctors and lawyers are obvious candidates. For the actuarial profession, you might argue that the hiring companies should be sufficiently sophisticated to judge their competence without formal credentialing. The hidden consumer in this case are the insurance regulators and the public relying on them. And, in fact, companies don't always require credentials in actuarial roles, but regulators won't accept annual statements without a supporting statement from a properly credentialed actuary.
I think lawyers are a problematic case. With most professions you can go to court if the designated gatekeepers are acting in an illegal or unethical fashion. The state Bar association, on the other hand, is going to be nearly impossible to fight for anyone who plans on making a living as an attorney. So, while I do support the goal of ensuring a base level of competence for a professional that may be the only thing standing between you and a jail cell, I am deeply concerned about the current mechanism for achieving that goal. The completely free market leaves too much blood on the floor for my taste to be worth considering as a solution.
Now that you mention it, though, when did marriage and children become either nefarious or ulterior reasons for dating?
Second, she soundly observes that marriage is basically a business partnership, except she considers it nonprofit (I do not). Assuming you aren't somehow committed to the single life, you should evaluate marriage opportunity based on your appetite for risk and a frank assessment of the opportunity at hand. Just as you shouldn't base decisions on sunk costs, you should ignore illusory opportunity costs. Physical capital decays, if you want a return on it you'll have to take a risk before it loses all of its production capacity. Of course, the older you get without taking a plunge, the easier it becomes to see the illusory nature of the opportunity cost you might have been using.
This all assumes you have a marriage opportunity that you can see having a profitable return (profit measured in happiness here). I would go so far as to say that it's impossible to judge marriage as an institution to be inherently profitable for you personally; it will always depend on the particulars. You might think marriage sounds like the place you want to be, but if you don't find a good partner for yourself in particular, marriage isn't for you.
As long as you don't have kids and both spouses have careers, getting out of the marriage is relatively easy. On the other hand, you only get one life, don't waste it avoiding risks whose most catastrophic downsides are not that bad.
I have assumed you aren't marrying a black widow or having kids with an affinity for patricide/matricide. But worrying about the latter is like worrying about being hit by lightning while not batting an eyelash over driving a car regularly. Avoiding the former is a matter of due diligence.
After reviewing these comments, it seems the interesting aspect of Giles Bowkett's paragraph is the emphasis on networking your way to a person with a need. It's easy to get blinded by the easy access to openings posted on job boards to the existence of non-advertised positions and enterprises you may not be familiar with. Rather than "job-getting" skill I'd call it "opportunity-finding" skills. Getting past HR can be a bear.
Most programmers I know seem to respond to job searches
by learning new programming languages. The logic there is
pretty weak. "I can't get a job with a language I know, so
why don't I see instead if I can get a job with a language
I don't know." Learning new languages is a good thing, but
there's a time and a place for everything. It's never a
matter of your skills being stale; there are still COBOL
jobs out there. If you're good at programming, and you
can't get a job, the skill to improve is not your
programming skill but your job-getting skill. If you've got
a task that requires two skills, and you have one of those
skills down solid, but you suck at the other skill, the
thing to do is not spend even more time perfecting the
skill you already have down solid.
As someone looking into programming jobs after a long period of not doing too much programming, I'm interested in what people think about this sentiment.As for the other, I admit health care insurance has its own peculiarities that make it a distinct field of insurance. And, no, your last assertion is incorrect. I have the advantage of having actually worked in the group pricing department of a major health insurer, so I'm not just speculating here. In lieu of further banging my head against the wall, I'll point out that the syllabi for the SOA's actuarial exams are available to the general public - just look in the "education" section of their site.
The better comparison would be with Worker's Compensation insurance, where the loss control mechanisms are ongoing.
As far as what the policies would cost, I don't know. Even if routine medical care is fully covered, a lot of people won't take advantage of it for whatever reason. An insurer's actuarial models will build that expected frequency into the projected cost.
If it bothers you sufficiently, you may consider most health plans to be the sum of a "real insurance" policy and a routine health discount plan. There are health plans that truly avoid assuming substantial risk, although they do so by getting providers to assume the risk. Those plans do retain the risk of providers in their network going bankrupt where prepaid capitation would be lost.
Health insurance sold on a group basis is underwritten on a group basis. That does not have anything to do with whether it is "real insurance." Health insurance sold on an individual basis is underwritten on that basis, but rate differentials may be severely constrained by statute or regulation.
These do not affect whether financial risk is transferred. The routine care issue does impinge on a valid consideration of whether the transferred risk is "insurable", but since these are short-term contracts it is not fatal.
If you want to look for greed in healthcare, look at medical schools, hospitals, doctors, and pharmaceutical and medical device manufacturers. Insurance costs are a simple reflection of the incomes of those parties. State regulators (for small group and individuals) and shopping around by sophisticated consumers (large groups) assures that.
Every rational form of insurance relies on distributing risk over groups of independent risks to obtain the benefits of the central limit theorem. There are some very specialized policies, and the Lloyd's syndicate, but anyone wishing to avoid ruin will diversify their risk.
It can be very tricky to selectively expand parts of a subexpression to create a block and then return to the head and execute the block you've created. Without lexical scoping it's difficult to safely create CPS macros.
It's not clear whether an understanding of division is really required for Google's marketing or not.
In Connecticut, for example, the statutes say revenue from self-employment should offset unemployment benefits, but the state agency has chosen the highly creative interpretation of "revenue" to include potential capital gains your efforts represent, and the notional amount of salary you should be paying yourself for the work you do for your startup, including, say, writing a business plan.
It does seem like they are shooting themselves in the foot, but the unemployment "insurance" fund in CT is already living on debt.
* Yes, this sentence is false.