Wedding and Honeymoon Pics are up
We completely rearranged the online photo album and put up all the digital
wedding pics we've received so far as well as the honeymoon pics. As always,
the album is here.
[/Life/#wedding_honeymoon_pics.html]
Comments (0)
Resume updates and ideas
I've always kept a copy of my resume posted online.
It's just easier to point requesters at a URL link. I can also cut and paste
it quickly and the format I have it in prints well. I like this because I
don't have to maintain a separate copy in a word processor.
A couple of years ago I was asked to make extensive revisions to it to make
it more concise. Previously, I used a more detailed C.V. format. The downside
was that I lost of lot of what I think is relevant and interesting detail.
On the one hand, it's the kind of detail you might include in a cover letter
or talk about in an interview. But I feel like it's these details that
differentiate me.
So I came up with a fairly unique solution. If you glide the mouse over
the resume, some of the items become bold and the text changes to blue
indicating a clickable link. Click the link and a popup appears providing
context and further depth on that item. It's a compromise between the two
resume approaches and makes it more compelling -- in my opinion at least. :)
I do sometimes get questions about posting my resume so publically and
potentially offending my current employer. I don't think posting a resume
necessarily says I'm job hunting. In fact, I like to think my resume speaks
well of my current employer. And I'm proud of the work I've done and
continue to do in my career so this is my way expressing that.
[/Work/Future/#resumeupdt.html]
Comments (0)
Asking the wrong questions
is the leading cause of wrong answers." That's what my .sig says.
Here's a well-written page on researching and asking technical questions.
The insights esr provides can be applied in other ways as well.
Click here
for more.
[/Computers/Internet/#questions.html]
Comments (0)
TCP/IP class
Way back in 2001, Barry McCormick and I wrote up this document
and taught a two session class for NOLUG on
the basics of TCP/IP. Looking at my web stats lately and after doing some
googling about, I've found it's quite a popular download. Since my site has
been rearranged often, I'm just posting this so it can be found again easily.
While some of the material is slightly outdated, it's still a solid
introduction and Barry and I are pretty proud of the work we put into it.
[/Computers/Internet/#tcp_ip_class.html]
Comments (0)
Using OpenBSD CARP and pfsync for inexpensive firewall/router redundancy
Enterprise network admins are probably familiar with Cisco's HSRP
which allows for router redundancy and VRRP
for firewall redundancy. This article
describes a way to achieve the same thing using features in the
upcoming OpenBSD 3.5 release . Other commercial firewalls certainly
have similar capability. However, OpenBSD's feature set is becoming
rather compelling.
Smaller businesses can certainly find value in such an approach,
keeping their network available and secure at a fraction of the cost.
Evening paying an outside consultant for installation and ongoing
support would be cost effective. Deploy something like this and things remain
comfortable for your cisco-trained network admins.
All of this of course reminds me that I really need to schedule some
time to upgrade my own OpenBSD
firewall.
[/Computers/Internet/Security/#carp_and_pfsync.html]
Comments (1)
Patent Nuttiness
This is a truly
rediculous patent. Apparently a company called ideaflood.com has managed to patent
subdomains.
*boggle*
So if I decide to set up, say, Jennifer.scottharney.com, I'm supposed
to pay a licensing fee to this company. How did they get this patent
in the first place?
Christopher Falkowski, a legal specialist in these topic areas for Bloomfield
Hills, Mich.-based Rader, Fishman and Grauer (raderfishman.com) says a number
of key requirements must be met to obtain a patent, whether that patent is in
the area of Web hosting operations or any other technical field: The invention
must be new or novel. It must be non-obvious. The persons claiming the patent
must be the inventors. And the patent application must be filed within one
year of a public disclosure or sale.
The patent was apparently issued in 1999. One of the first relevant
RFC's I could find is RFC
805 dated 8 February, 1982. Here's the introductory text:
Introduction
A meeting was held on the 11th of January 1982 at USC Information
Sciences Institute to discuss addressing issues in computer mail.
The attendees are listed at the end of this memo. The major
conclusion reached at the meeting is to extend the
"username@hostname" mailbox format to "username@host.domain",
where the domain itself can be further structured.
Hmmm. Besides being an obvious idea, there's clearly prior art.
That's just one RFC out of many and I'm certain there are hundreds of
examples of this use of subdomain naming. Perhaps a search of
The internet archive will provide
some examples.
[/Computers/Internet/#patent_nuttiness.html]
Comments (0)
Gettin' Hitched
Well, I haven't posted in a while but I'm planning
to change that. The biggest news I have to report is that I'm getting
hitched to Jennifer this September. The wedding is going to kept real
small but, per family requests, I've started a separate site here. Out of town
guests, (ie. her family), should be able to find some useful info
there.
[/Life/#wedding.html]
Comments (1)
|