Just too weird not to say something:
A cloned dog Mormon mink-lined handcuffs tantalizing mystery.
Yeah. When I served a mission, just about every male missionary talked about this old story (over a decade after the fact).
Half-baked opinions, served lukewarm.
Just too weird not to say something:
A cloned dog Mormon mink-lined handcuffs tantalizing mystery.
Yeah. When I served a mission, just about every male missionary talked about this old story (over a decade after the fact).
Just too weird not to say something:
A cloned dog Mormon mink-lined handcuffs tantalizing mystery.
Yeah. When I served a mission, just about every male missionary talked about this old story (over a decade after the fact).
OK, folks, I’ve been taking some flak at work for opposing hydrogen-powered cars. For a thorough look at why hydrogen is currently an awful choice to drive your car around, I refer you to here:
http://mb-soft.com/public2/hydrogen.html
To sum up:
OK, folks, I’ve been taking some flak at work for opposing hydrogen-powered cars. For a thorough look at why hydrogen is currently an awful choice to drive your car around, I refer you to here:
http://mb-soft.com/public2/hydrogen.html
To sum up:
My brother, Jay Barnson, made the front page of Slashdot today. That means that I may be shutting down other services — including this personal web site — if traffic gets too high.
My brother, Jay Barnson, made the front page of Slashdot today. That means that I may be shutting down other services — including this personal web site — if traffic gets too high.
Anyway, I’m really excited on his behalf. The Slashdot article is Why Game Developers Go Rogue, while the original article on The Escapist is Going Rogue. Check it out!
OK, I am a big fan of stating flat-out what it is you’re saying. I am not a fan of innuendo. So when I recently watched “A Video Portrait Of Barack Hussein Obama“, I was incensed at the baseless use of innuendo, error, and mis-statement.
OK, I am a big fan of stating flat-out what it is you’re saying. I am not a fan of innuendo. So when I recently watched “A Video Portrait Of Barack Hussein Obama“, I was incensed at the baseless use of innuendo, error, and mis-statement.
This video offends me. It’s a racist, anti-Muslim, mean-spirited attack that cannot stand unanswered.
Let’s take a break here. Let’s spend the next several minutes analyzing Reverend Wright, and try to attribute all of his negative attributes — including “rude” — to Obama.
Have some popcorn.
Have a cookie.
And after all this, I learn that this video has already been repeatedly debunked and shown for the fraud it is. Perhaps I should not have dignified it with a response.
It is videos like these that make me question my membership in the Grand Old Party. I am ashamed to share a party with such an example of patent bigotry as this extremist Christian hate-monger. Ultimately, I am just as believing of the claims of this video as I am of the claim of its producer, aired twice during the segment.
“I am Lorne Baxter. And I invented the Internet.”
Yes, yes, Jason Mitchell, absolutely, I’m sure you did. Your name is Lorne Baxter. You invented the Internet. When someone starts off a production with two lies, how much more should you believe?
I was recently hired for a lateral move within OmniMegaCorp to another department with slightly different duties. I’m really excited about this move, because I get to get more involved with an area where I think computing is going: grid or “cluster” virtualized computing.
I was recently hired for a lateral move within OmniMegaCorp to another department with slightly different duties. I’m really excited about this move, because I get to get more involved with an area where I think computing is going: grid or “cluster” virtualized computing. These fault-tolerant, highly-reliable systems bring some amazing benefits for computing in environments that don’t demand the very highest performance from bare-metal machines. That said, they still offer substantial performance for very large infrastructure projects that tolerate latency well, and the systems-management and uptime benefits alone are enough for many to be willing to sacrifice a little performance for immense reliability.
As part of my transfer — which will involve sitting at the same desk I’ve been at for nearly half a decade — I was asked to write a job description of what I do in order to aid my current management in finding a replacement. I thought it might be entertaining for you, too.
Duck Soup Wrote: > 1. Projects that you are currently working on or soon to be involved with > 2. Functions that you are the primary contact for > 3. Days and duty at our failover site
To be honest, other that deployments, I have very few “projects” since so much of my work is standard duties and firefighting. That’s one of the things I look forward to in this move: more time to oversee projects from beginning to end, rather than being so reactive all the time.
Projects: * Linux/Solaris deployment wave 2. Given that our mass-deployment product doesn’t seem to be working on these subnets for Linux systems, this can be very on-site time-consuming. Check w/E. Honda for exact times. Main jobs are configuring the DRACs, ensuring network port requests go through, DNS coordination, making sure power/network is set up, assigning/labeling machines, installing base OS. * Ongoing migration of various Phase 1 and legacy machines to Xen/VMWare and alternative operating systems.
Standard duties: * Failover payment site backup rotation and maintenance (~2-3 hours per week), usually Thursday mornings. Roger Giggley and I shared this duty before, and they are production systems. I volunteered to do it each Thursday because it’s on my way to work, and quite a bit out of his way. * Backup monitoring, maintenance, and rotations: 10+ hours/week. About 3-5 hours actually rotating tapes. * Restores. This requires an on-site person to swap in tapes much of the time. 2-10 hours per week (depends where we are in the build cycle). * One-time backups. Often requires short-term ejects. Averages just a few hours per week, around 2-3 hours. * Service request queue. Rest of the week, performing miscellaneous on-site Linux/Solaris/HP-UX/AIX troubleshooting and maintenance. (~20 hours/week) * Attend Friday morning coordination meeting @ 10:00 AM US/Mountain. Provide reports and status updates for coordination with Logistics, IT, and Space/Power. Also report on downtime, if any. (~1 hour/week) * Provide support on general Linux/UNIX questions to peers/managers/directors in other development areas (~1 hour/week) * Provide on-site support for remote members of my team and other UNIX, storage, and backup teams who have encountered difficulty administering systems remotely (up to 10 hours/week) * Provide on-site support for other teams that require UNIX expertise, though not necessarily intervention (2-3 hours/week). * Handle auditing duties gracefully with external auditors. (a couple times a year) * Interface with vendors for hardware replacements and repair. (mostly OtherBigVendorCompetitor for backup systems and NAS)
Duties recently removed: * NAS administration (went to storage team) * SAN administration (went to storage team)
Useful skills for replacement: * Thorough understanding of Netbackup, robotic tape libraries, and fibre-channel architecture. * Linux, AIX, HP-UX, and Solaris administration abilities (though maybe the Linux stuff could be shuffled off to the new Linux team) * Demonstrate ability to automate processes with at least one scripting language (Perl and Posix Shell or Bash a plus) * Show familiarity with kernel rebuilding, performance tuning, and basic performance troubleshooting (familiar with “top”, “free”, “iostat”, “find”, etc.) * Be able to write an init script from scratch, including case() statements to handle at least stop/start requirement on Linux/Solaris. * Be familiar with at least one UNIX rapid deployment system (AIX: NIM, Solaris: Jumpstart, Linux: Kickstart, HP-UX: Ignite) * Familiarity with Xen, VMWare, and other virtualization technologies. * Self-directed with ability to work under severe time pressure and while juggling many equally-important high-priority items. * Able to communicate effectively via electronic mail, instant messenger, and phone. * Must be willing to carry mobile phone 24/7 and be available for on-call duties on occasional weekends. * Must be able to lift seventy pounds. * Willing to work strange hours occasionally to handle joint issues with staff in India.
So what does your job look like?
Matt’s top reasons to wear an undershirt:
* If I’m wearing a polyester/acrylic shirt, I’m actually much cooler wearing a cotton undershirt than not.
* I’m cooler wearing a T-shirt than going without a shirt at all. The cotton Tee wicks away perspiration without letting it drip down my butt-crack.
Matt’s top reasons to wear an undershirt:
* If I’m wearing a polyester/acrylic shirt, I’m actually much cooler wearing a cotton undershirt than not. * I’m cooler wearing a T-shirt than going without a shirt at all. The cotton Tee wicks away perspiration without letting it drip down my butt-crack. * I have kind of large, long nipples for a guy, and I really, really hate “poppers”! (That is, poppers on ME, I think they are fantastic on women) * I can throw away cheap T-shirts with yellow pit stains rather than my favorite shirts which end up with yellow pit stains if I don’t wear an undershirt. * I can do double-duty on a favorite shirt before washing it ‘cuz the undershirt stinks instead of the nice shirt. Laundering a shirt less also prolongs shirt longevity. * Collared shirts without undershirts look tacky… particularly if you are prone to Poppers, as mentioned above. * My nipples chafe if I sweat much and don’t wear an undershirt. * I sweat… a LOT, even just sitting in this chair right now. If you don’t sweat much, dude, you don’t know what it’s like. A sweat-soaked shirt is unattractive.
There you have it: reasons to wear an undershirt. I stay away from the wife-beaters (also called tank-tops) because they don’t solve the pit-stains problem.
What about you? Undershirt-wearer or undershirt-hater?
Pete Ashdown, owner of Xmission Internet Services in Salt Lake City, former senatorial candidate, and all-around good guy, penned a piece in response to recent efforts to expand oil extraction in the US. Here’s an excerpt:
Pete Ashdown, owner of Xmission Internet Services in Salt Lake City, former senatorial candidate, and all-around good guy, penned a piece in response to recent efforts to expand oil extraction in the US. Here’s an excerpt:
Carter proposed that U.S. automakers attain a whopping 48-mile-per-gallon fuel efficiency by 1995. He demanded that we curtail imported oil by imposing fees. Finally, Carter proposed windfall taxes on oil companies to fund alternative energy and a goal of generating 20 percent of our power from solar by 2000. What happened? It would be nice to see an explanation from Hatch, since he was a three-year senator in 1979. His explanation not forthcoming, my presumption is Carter’s visionary energy goals were tossed on the trash heap, along with the solar panels he’d installed on the White House, when Ronald Reagan moved in. America then increased dependency on foreign oil and forfeited automobile innovation to Japan. Middle East oil-rich dictatorships went on to become even wealthier and more entrenched… A small patch of Alaskan wilderness, coastal drilling, oil-shale magic, nuclear power subsidies, less regulation on fabulously wealthy companies – these will make us energy independent and gasoline inexpensive again? … This country retooled its entire industrial sector nearly overnight in order to fight World War II. America fulfilled President Kennedy’s challenge to land on the moon in under a decade. Yet become energy independent with renewable technology in the same amount of time? Sorry, we’ll leave that kind of innovation to advanced countries like Brazil, Denmark, Iceland and Sweden. Solving our energy problems by loosing the reins on the oil, gas and coal companies is a deal that requires us to forget 30 years of history. This bargain ignores the hidden health costs of polluted air and water and insists that consumption of energy is not correlated to the price. In spite of their feel-good commercials, these companies are not here to solve our energy and pollution problems. They’re here to make a profit.
Unlike Ashdown, I believe nuclear power to be a viable, effective, clean method of power production with minimal environmental side-effects. I think we need to be spending more money developing nuclear power.
But like Ashdown, I believe allowing oil companies free reign on protected reserves is not a long-term solution. Demand for oil is outstripping supply. We live in the age of Peak Oil, and we must create new technologies based upon renewable — or at least extremely-abundant — resources to power our needs for the twenty-second century and beyond.
Additional US oil exploration is a Band-Aid on the severed artery of oil independence.
So this morning, I commented to a co-worker that managers should be less interested in obeisance and kowtowing from their charges, and more interested in listening and coordinating.
“That’s right,” says Dave, “they should just stop, collaborate, and listen“.
So this morning, I commented to a co-worker that managers should be less interested in obeisance and kowtowing from their charges, and more interested in listening and coordinating.
“That’s right,” says Dave, “they should just stop, collaborate, and listen“.
You know, I remember as a kid that I used to be bored on Saturdays. As an adult, my entire Saturday is booked a week in advance, and virtually nothing for me personally.
Not whinin’, just remarking.
You know, I remember as a kid that I used to be bored on Saturdays. As an adult, my entire Saturday is booked a week in advance, and virtually nothing for me personally.
Not whinin’, just remarking.
I’ve been involved in a few discussions online lately, wherein I found myself in the odd position of attempting to explain actual Latter-day Saint doctrine to a member of the LDS church who refused to believe me, the scriptures, historical leaders, or affirmations by present leaders.
I’ve been involved in a few discussions online lately, wherein I found myself in the odd position of attempting to explain actual Latter-day Saint doctrine to a member of the LDS church who refused to believe me, the scriptures, historical leaders, or affirmations by present leaders.
The topic in question this time was Creationism. The LDS position is that there was no death in the world before the Fall of mankind, the Fall brought about physical (and spiritual death), and the Atonement can return mankind to the exalted state in which he existed prior to the Fall. You would find very few Sunday School, Priesthood, or Relief Society classes in which that doctrine would be disputed.
However, such a doctrine, at the very least, precludes abiogenetic evolution of humankind, and possibly animals. Periodically, LDS leaders have reaffirmed the Divine creation of mankind in a way that precludes the “theory” of evolution. Right around every ten years since 1909 they’ve released another statement that they have no opposition to “true” science, but where a scientific theory appears to contradict revelation from God, one should trust the revelation over the flawed scientific theory.
Online LDS apologists cannot be convinced of this fact of LDS doctrine that would be readily affirmed in any classroom in LDS meetinghouses on a Sunday, and which has the repeated endorsement of the highest leaders of their church. The apologists would have one believe these statements don’t actually mean what they clearly state. While doing some hunting for some way to reason with the unreasonable, I came across a wonderful clarification from a fellow named “Cinepro” that helpfully nailed down the definition of “doctrine” according to online LDS apologists.
(From http://blog.mediumcouncil.org/?p=22 )
- You are bound to believe the things required by the temple recommend questions (if you want to go to the temple).
- You cannot public disagree with any doctrine held by a current apostle.
- New “doctrines” do not have to be reconcilable to old “doctrines”.
- Old doctrines taught by apostles that have not be renounced or contradicted by later apostles may well have expired without further action.
- There is an “unwritten order of things” both doctrinal and procedural that you may be held to.
- The current brethren may be “speaking as men” but you can take no action on this fact. This only applies to dead apostles.
- The scriptures are not necessarily a doctrinal bind since non scriptural commentary on the scriptures by later brethren my change or obsolete the scripture.
Nailed it!