Rig Intelligence

// About the site

A software engineer's experience coding in the oil field. *Tips, tricks and other things that seem interesting {to me}.

Posts I like

More liked posts

Might have some interesting implications and would be closer to putting the iPhone in the ‘Ruggedized’ category.

Waterproof iPhone details ‘leaked’.
Website TodaysiPhone has revealed details from a source ‘well-placed in one of the UK’s top independent phone retailers’, who claims that both the next generation of iPhone and Samsung Galaxy S devices will have a waterproof coating from company HzO.

The Liquipel coating covers both inside and outside the phones to make it water repellent, making them less susceptible to liquid/moisture damage.
He stated “both will have had liquipel treatment as they’ll be altering the wording on insurance.”

While the source was not revealed, the website claims the person was correct about the launch dates of both the white iPhone 4 and the iPhone 4S.
8 Bit Future covered a similar technology last month called Liquipel, check out that story here.

Might have some interesting implications and would be closer to putting the iPhone in the ‘Ruggedized’ category.

Waterproof iPhone details ‘leaked’.

Website TodaysiPhone has revealed details from a source ‘well-placed in one of the UK’s top independent phone retailers’, who claims that both the next generation of iPhone and Samsung Galaxy S devices will have a waterproof coating from company HzO.

The Liquipel coating covers both inside and outside the phones to make it water repellent, making them less susceptible to liquid/moisture damage.

He stated “both will have had liquipel treatment as they’ll be altering the wording on insurance.”

While the source was not revealed, the website claims the person was correct about the launch dates of both the white iPhone 4 and the iPhone 4S.

8 Bit Future covered a similar technology last month called Liquipel, check out that story here.

Is RFID the Next Big Thing {let’s hope so}

“When predicting technology trends, Bill Buxton, Principal Researcher at Microsoft Research and author of Sketching User Experiences may have said it best: “If history is any indication, we should assume that any technology that is going to have a significant impact over the next 10 years is already 10 years old!” This theory holds true for several technologies. For example, the first mobile telephone call was made in 1946, many years before the first commercial cellular network was launched in 1979. GPS was in use for nearly 30 years in government and military programs before it became a must have for personal vehicle navigation. And, the formation of the Internet as we know it began in the 1980s, but wasn’t truly incorporated into virtually every aspect of modern human life until a decade later. Applying this premise to radio frequency identification (RFID) seems to hold true as well. The technology itself was well over 10 years old in 2004 when retail giants began pushing it as a means of driving efficiencies into their supply chains. While these initial retail programs didn’t succeed according to plan, and mass adoption didn’t happen the way many analysts predicted, these initiatives did kick off a high level of interest from retailers, product manufacturers and many other industries and markets focused on improving their business and service processes. Between 2004 and now, something else happened that makes one ask if RFID is ready to have that significant impact Buxton mentions.”

Reshaping the Way We Think about RFID | ThingMagic’s RFID Blog - Radio Frequency Identification Company and Industry News

(via smarterplanet)

Two Domains, One Google Apps

Since almost the beginning, Google Apps has worked like this:

  • Every account has one domain name (let’s call it yourdomain.com) that users use to log into their mail/calendars/etc, which Google calls the primary domain name. You set this up when creating your Google Apps account, and for all intents and purposes it can never be changed.

  • Accounts can also have one or more domain aliases. Let’s say in addition to yourdomain.com you also have yourdomain.net, and you want emails sent to david@yourdomain.net to end up in the same mailbox as those sent to david@yourdomain.com. You’d log into your Google Apps control panel and add yourdomain.net as a domain alias for yourdomain.com, and voila, it works (well, as soon as you’ve completed the absurdly complicated ownership verification and MX record setup steps).

But let’s say you (or your business) has a third domain name, kittensareawesome.com, and you want to set up the email account david@kittensareawesome.com, but you don’t want emails sent to that address to go to the same place as david@yourdomain.com — in other words, you want mailboxes on kittensareawesome.com to be entirely separate from the ones on yourdomain.com or yourdomain.net.

For most of its history, Google Apps had no way of letting you do this without creating a second, separate Google Apps account for kittensareawesome.com. But today I discovered that is no longer the case: Google now lets you add additional domains to a single Google Apps account.

In a minute I’ll explain why you might want to do this, but first, here’s a guided tour of how to add an additional, non-alias domain to your account:

  1. Log into your Google Apps control panel.

    This is always located at http://google.com/a/YOURDOMAIN.COM. You’ll need to log in with the username and password you created when you initially set up Google Apps; this will usually be the same as your first/primary Gmail mailbox, and in fact you can usually get to this page more easily by logging into your Google Apps Gmail and clicking on ‘Manage My Domain’.

  2. Click on Domain Settings.

  3. Then click on the tab labeled Domain names.

  4. Click on the link labeled Add a domain or domain alias.

  5. Finally, on the next screen, check the second-from-top radio button, labeled Add another domain.

Then you click the button labeled Continue and verify domain ownership, which takes you through the same annoying steps you have to follow any time you ask Google to do anything with a domain name that’s not google.com.

Once you’ve verified ownership and set up MX records (or had a friendly nerd in your office do it), you should be able to come back to the control panel and add users to either yourdomain.com or kittensareawesome.com. (Or, in my case, demaree.me or practical.cc.)

To add a new mailbox on the new, second domain, go into your Organization & users tab and create a new user. You’ll now see a handy drop-down menu letting you choose which domain the new user should belong to:

Why did I need this?

Years ago when I started doing freelance work, my main personal domain name was practicalmadness.com and — being 24 years old and brilliant — I decided it would be sensible to set up my business on the far-too-similar, not-remotely-professional practicalmadness.net domain, and created a Google Apps account for it.

Not long after that I came to my senses and changed my business domain to the shorter, simpler practical.cc. But by then I had plenty of mail (and inertia) built up in the old practicalmadness.net account, and at that time Google was somewhat stingy about letting users create multiple Apps accounts. So for years I’ve had to keep that domain going — and have kept paying for renewals every year — just because it was attached to my old freelancing business’s email account.

I started looking into this today because practicalmadness.net comes up for renewal in about 2 weeks, and this year I decided to let it lapse. But I still use practical.cc for a number of things, so I wanted that to remain active.

A quick side note before I continue: one thing I learned after Adobe acquired Typekit — and turned our typekit.com Google email accounts into adobe.com Exchange ones — is that Google does not care if the primary domain on a Google Apps account stops working. Even though Google is no longer receiving mail at typekit.com, we can still log into those Apps accounts to search our mail archives or use non-Mail services such as Google Docs.

So if I didn’t mind having a second Apps account, or the cognitive dissonance of logging into it with an email address that no longer works, I could have simply let the domain lapse. practical.cc was set up as an alias and would have continued to function even after practicalmadness.net went away.

But now that I know I can manage all my domain names from a single Google account, that’s the way I want it.

Caveat nerdor

The first small complication: the domain I wanted to add to my Google Apps account at demaree.me was already associated with my other Apps account at practicalmadness.net. Google won’t let you add a domain to two accounts at once. Here’s what I did:

  1. I logged into the practicalmadness.net control panel and deleted practical.cc as an alias domain.
  2. Then I switched to the demaree.me admin and went through the steps to add practical.cc as an additional, non-alias domain (as described above).
  3. Finally, I then immediately added a new david@practical.cc mailbox on the demaree.me account.

Google says domain changes can take up to 30 minutes to take effect, but in my case they were virtually instant, and I immediately started receiving emails in the new Gmail account.

A couple of big caveats to doing what I did:

  • The new account is a totally new, empty Gmail account. None of my filters, labels, settings, or messages made the transition to the new mailbox.

    When I set out to make this change, I’d originally planned to implement some complicated migration plan, in which I used GData or IMAP to copy all the mail from the old mailbox to the new one. But my experience with the typekit.com mail made me realize: I don’t need to. All the old mail will remain in the old practicalmadness.net account (which remains active, even though it no longer receives new messages), and I can always log in if I need to retrieve something from my archives. If it turns out I need to move over something important, I can figure that out later.

  • If you receive a high volume of mail on an address you want to move between Google accounts, I might recommend against doing this switcheroo during business hours. Or, if you pay for a Google Apps business/enterprise account, I recommend contacting Google’s customer support to ask if they can help you do it safely.

    I say this because I quite frankly have no idea what may have happened to any messages received during the 60-or-so seconds between when I removed my domain in one place and added it in another. That address receives a low volume of mail so in my case it was harmless, but it may not be harmless for you. Caveat nerdor.

Now that all that’s done, I’m pretty happy to have one fewer Google Apps account in my life, and now I’m looking to see if I can eliminate some other ones.

Questions? Hit me up on Twitter at @ddemaree or email me at david@demaree.me.

theBestTypeOfAdvertising

Enjoying one of the finer dining destinations in Midland, TX (not saying a ton understandably), I’ve noticed that dessert marketing is comparable to building enterprise software. Here at the Italian Village, the most popular dessert by far is the bananas foster; and the delicious banana/ice cream combo is great, however the fact that it’s made at the table draws unrivaled attention to the dish from all of the patrons, and therefore becomes the de facto dessert choice.

This decision mechanism is very similar to building enterprise software for large companies… They all have specific software needs that can help build efficiencies and safety, however in conceptual form software development holds little appeal. But if software is built in front of these companies (al la banana foster) they have a completely different reaction. I’m usually not a fan of building projects on spec, however to gain the best reception in the oil field, these execs prefer to buy products that are already in working form.

So love it or hate it, making software ‘at the table’ is one of the best ways to get software accepted in this industry.

Product Review: Tom Bihn iPad 2 Bag

I’ve been trying out the Tom Bihn iPad 2 messenger bag for the past few months and wanted to give some feedback on it. There are countless tablet carrying cases out there and I’ve tried a few, however the Bihn case has been the best one I’ve seen so far.

Pros:

1. High quality material

2. Lightweight

3. Fits my iPad, wallet, keys, etc.

4. Great selection of colors

5. Stain resistant

Cons:

1. Co-workers may make remarks about your ‘purse’

So as long as you’re confident in your masculinity and need a more efficient way to carry your iPad, I think the Tom Bihn messenger bag is a great way to tote your tablet.

Loading next page

Hang on tight while we grab the next page