This isn’t a travel guide, it’s just my notes from 8 days we spent on the Yucatán peninsula in Mexico in January 2016. The first section is a day-by-day account of what we did, the second section has practical, topical notes such as working with Mexican currency, dealing with police, getting around, etc.
Thursday, 7 January 2016
We arrived in Cancún in the late afternoon, but the lines through security were long and we chose the slow line. Tip: see how many security officers handle each line and choose the line with the most officers.
Apple removed the OpenSSL header files in “El Capitan”, making it hard to build OpenSSL-dependent libraries without modifying your system a little bit.
Fortunately we have Homebrew ; if you don’t have it yet, go ahead and install it now . I’ll wait here.
Dan North gave a presentation a few years ago about some of the decisions a software architect or a developer might make.
At 46:50 he begins to talk about the DRY principle (“Don’t Repeat Yourself”). He makes it clear that he’s a fan of the Pragmatic Programmer, but this section of his talk is a warning about following one principle (DRY) without giving consideration to other competing principles. In this case, the opposite of DRY code is decoupled code, another desirable goal.
I’m trying to understand premature generalization. First, why is premature generalization a problem? Dave Smith :
One result of premature commitment to a generalization is that you’re supporting code that isn’t used. I’ve joined projects and found that 1/3rd of the code base wasn’t reachable, all because one or more programmers had tried to write class libraries that would solve all possible future needs. It is really, really tempting to give in to the misplaced belief that “… as long as I’m here, I might as well add the other methods that people might need at some point.”
I presented at our Salt Lake Perl Mongers about using Docker to isolate dependencies in your Perl applications.
SSH tunnels can provide secure connections through insecure or untrusted networks and may also be used to securely route through firewalls.
About This Guide
This guide began as a personal document to help me learn and remember how SSH tunnels work and has been several years incubating. If you find errors or think of additional examples that you believe would be helpful, I’d be delighted to know about them.
Terminology
Throughout this guide we use “SSH” to refer to the SSH protocol or the world of SSH things and use ssh to refer to the ssh(1) program itself. “We use ssh and sshd to make SSH connections.” The examples in this tutorial are based on OpenSSH 0.9.8 and later.
Some photos from Arches National Park:
And one of my siblings eating sand:
My name is Scott Wiersdorf; I hail from Salt Lake City but have lived in Pleasant Grove, Utah since y2k or so. I write software for a living and am EVP of Technology at OUD Management Partners, Inc. I like to ski, hike, backpack, read, and overthink things. My résumé is here.
This website is my personal blog. I have a family whom I love and admire, but I seldom mention them so they can define their own public lives. I’m at ease being inconsistent in my views and opinions over time.
I talked about event loops at OpenWest.
Euclid created this simple and beautiful proof of infinite prime numbers. I am writing this down as I understand it to make it more solid in my own mind. Caveat: I am not a mathematician and don’t use rigorous terms below.
Let S be the set of all prime numbers. Multiply all members of S to come up with a number N. N is not prime (being composed of all primes in S). But N+1 may be prime; if so, N+1 can be added to S.