Do I mind that we took the same Cherry Blossom walk yesterday that we did last year, and I re-took the same photos? No, not at all. It was sunny and beautiful and the exact right place to be.
Alright, next time I'll mix it up. Next Cherry Blossom Walk's theme: What the Flowers See. There, that should be a different perspective.
I saw this TED talk on Camels, and in honor of my Mother-in-Law (who has quite the camel collection!), figured I should watch it. In short, it's fantastic. Here, take a few minutes to watch it and then read my comments below:
Well done, right?
First off, talk about excellent storytelling. Injecting pre-recorded audio clips into what feels like a casual talk is really powerful. The voice of the scientist is literally heard, even though the talk is being given by a historian.
And the overall thesis: that new information should result in a new world view is something we simply don't embrace often enough. I'm all for having bedrock principles and such, but when you learn something, it can and should change you. This is a core scientific idea that's often hard to appreciate. Yes, we know X is true. And we have to operate as though X is true. But, we also have to accept that more data may show that in fact, X isn't true. Frustrating, but the alternative has you twisted in knots and at odds with the truth.
Deep stuff, and all from a camel! Oh TED, you simple never disappoint.
So let's review last night's Gravelley Point fishing adventure:
So yeah, it was a success.
Note to self: thar be plenty of catfish in the Potomac! One only needs to show up with chicken livers and the patience to wait for a bite, and you should be good to go. Or at least that's what my Dad (who actually caught fish) tells me.
Here's an outdoor hack I'm going to have to try in the field: creating rings from split branches. I know, that hardly sounds exciting. But as this video shows, you can do quite a few things with these small hoops. Specifically, it shows them being used to: (1) to keep a plastic bag's mouth open, (2) to assemble a tripod and (3) to hang the open bag from the tripod. Here's a screencap of the tripod setup:
While not a true field test, I did pick up some branches at the end of my trail run and today fiddled around with making some rings. I was actually able split the branches using the P-51 can opener that lives on my keychain:
However, I failed to actually construct the rings: I think the wood I picked up was just too dead and dried out to be pliable enough to for the job. Still, with practice, I could see this working.
Here, watch the video below. It's far from exciting stuff, but it's the kind of complete demonstration that's actually useful for learning a new skill.
I'm typing this post as another whirl-wind trip to Boston comes to a close. We started the trip by picking up Gavriella early from her play-group and taking her to Jump On In, an indoor bouncy house extravaganza. She wasn't immediately in love with this. When asked what she wanted to try first, she explained she'd like to put her shoes back on and leave.
But after a bit of cajoling and demonstration by Shira and Myself, she finally warmed up to the place and ended up having a ball. After two hours of jumping, we were all completely exhausted. We hit Jump On In on Friday morning, before school had let out, so it was almost completely empty. We nearly had the place to our self, which made getting Gavriella warmed up to the surroundings even easier.
After lunch, we picked up Tzipora and ran some errands. And being Uncles and Aunts, we had no qualms about stopping at the froyo place to have a treat. Gavriella enjoyed her watermelon yogurt and Tzipora devoured her strawberry.
One of the main reasons for the trip: it was the Twins' 7th birthday on Friday night. We celebrated with cake, balloons and themed napkins (My Little Pony for Chana, Thomas for Dovid). It's hard to believe that the little tykes are 7 years old. That's like little people! I can still remember sitting next to them in the NICU, two little bundles barely bigger than a handful (exhibit A, exhibit B). Actually, come to think of it, they're still a handful.
We passed an enjoyable Shabbat playing with Legos (the kids are really getting the hang of following the instructions) and taking a 4 mile(!) hike to Brookline Reservoir. We decided to name the destination 'Thirsty Pond' as the kids were absolutely parched when they arrived. The reservoir has a nice running path around it and apparently allows fishing. Also, to our surprise, there were wild turkeys wandering around. Though, there wasn't a great place for the kids to play there (I mean, they're fine with playing inches from the edge of the water, us, not so much) so I doubt we'll be returning anytime soon. The kids passed Reservoir T-Station on the way which has some large rocks practically screaming out for kids to play lava games on. So they did. This definitely helped make the hike a success. They were also a perfect spot for a cookie break. Our little hikers continue to march pretty much wherever we ask them. As long as we can put up with their constant pleas for snacks, we're all good.
Shira and I started this morning with breakfast at Tresca's Eating Place. If you ever want to take a trip back in time to when breakfast was a simpler affair, this is the place to go. No pesky gluten free or heart-healthy menu options. I got egg and cheese on a bagel, and there was no discussion of what artesian bagel I wanted, or how aged the cheese should be. It was a good 'ol plain bagel, with good 'ol American cheese, with a good 'ol egg on top. What's to discuss? (And for the record, it tasted awesome). Oh, and it's cash only, too. This was a nice contrast to the dinner the night before at Zhu. We tried this Asian Vegan restaurant for the first time and were quite impressed. We'll absolutely have to go back to try more items on the menu, as the Mushroom Seitan and General Tzo's were both quite delectable.
This morning we awoke to a feels like of 19°F. So yeah, an outdoor activity was pretty much out of the question. While searching for an indoor activity we learned that there's a Legoland Discovery Center in town and the kids had never been. Having had a positive experience in Legoland in Florida we thought we'd give the Boston version a try. Yelp reported that folks generally had a good time, though some thought it was a bit small for the hefty sized entrance fee. Given our need for a fresh indoor activity, and having just played Legos the day before, we thought we'd give it a try.
Yelp was right, the place isn't huge. Somehow Legoland manages to fit an introductory movie, two small'ish amusement park rides, a 4D movie, a Lego Boston Miniland, various Lego building stations and a kids play area in one large upper story building of what amounts to an outdoor mall. All 4 kids enjoyed the space immensely. Chana and Dovid loved the rides and 4D movie, Tzipora and I enjoyed building and racing cars, and Gavriella enjoyed hugging the (to her) giant Lego characters. Shira and I enjoyed the closed in play area, where all 4 kids could climb and run with wild abandon. Gavriella, to her credit, managed to climb to the tippy top of one of the structures in the play area and just hung out there enjoying the view. When she was ready to come down, Chana helped her make the trek back to ground level.
Shira tells me that she was especially impressed with the staff at Legoland, something we couldn't really say about the Florida version. So, in the end, was it worth the small fortune to get in? Given the kids' ages and the weather outside, heck yeah. For what we spent, we could have probably gone on Craigslist and bought a lifetime supply of Legos, but what the heck, the kids loved the experience.
And then it was off to the airport for us, where our plane was delayed just long enough for us to get lunch.
\ A few nights ago I was talking with my Dad about backup strategies and hit me: I don't have a method in place for backing up photos on my Linux box. On Windows, I use both Carbonite and Google Photo. But on Linux, I've got nothing. Well that's not good. I needed a simple solution, and I needed one fast.
I know that there are number of fancy sync options for Linux, but what I really wanted was something Unix'y. In fact, what I really wanted was rsync pushing to Google Drive. And turns out, you can get essentially this using rclone. I grabbed the binary (a yum install would have been sweet, but doesn't appear to be available) and typed:
rclone config
I answered a few questions, and authenticated my Google Drive account using OAuth. And then syncing was as simple as running the command:
rclone sync ~/Pictures personal_gdrive:Backups/Pictures
The command churned away, and 27 Gigs later, finished. I put the above command in cron and now I've got my backup solution in place.
rclone is definitely going into the toolbox for future use as it elegantly bridges the modern cloud with the old school Unix world.
So they're calling for snow tomorrow. Whatever. I'm with the trees on this one: it's time for Spring!
Shira scored tickets to last night's Bulls vs. Wizards game. I'm not a follower of pro-sports, but I'm always glad to hit up a live event. And I've got to say, I was really impressed with last night's game. No doubt the ridiculously close seats helped. I mean, I know on paper these guys are big, but up close, they're absolutely huge. And yet, they can move with incredible grace and precision. There were definitely sequences where it seemed that the players managed to hang in mid air for an unnaturally long time. All in all, very impressive.
A few photos of the action are below. I missed the tip-off, but in my defense I had this going on in front of me, which served as, uh a, distraction.
Fun times, and it was great to see the home team victory!
Don't get me wrong, I love me an impressive upcycle, where someone takes trash and turns it into a magnificent object. But that's just not me. Me, I'm strictly opportunistic (read: lazy). I see an interesting container, I'll toss it in the dishwasher. Maybe I'll find a use for it, maybe it'll end up in the recycle bin. No biggie.
My latest reuse hack: with a minute or two of TLC, turn the plastic mesh bags that clementines come in, into little drawstring bags. The process is embarrassingly simple:
That is: cleanly cut one end of the bag, ziptie the other end, cleanly cut it, thread a shoe lace through the first opening. And you're done.
The result looks like, well, a mesh bag:
I wish these bags weren't made from plastic mesh, as I bet old school string would be quite strong. But still, the bags are surprisingly useful. They are lightweight, pack down to nothing, allow the contents to "breathe" and best of all, if one gets damaged or generally nasty, it can be recycled like it was going to be in the first place. Zero guilt.
Pop Quiz: What do Issac Newton, Buzz Aldrin and My Dad all have in common? They all solved math problems, at one time or another, using the same device: the mighty slide rule. After watching this video I realized I've never done a post on the slide rule, and as an aficionado of all things simultaneously basic and techy, I needed to correct that.
The technology really does go back hundreds of years, with Issac Newton clearly describing a device which anyone doing math in the 1960's or before would appreciate:
Mr. Newton, with the help of logarithms graduated upon scales by placing them parallel at equal distances or with the help of concentric circles graduated in the same way, finds the roots of equations. Three rules suffice for cubics, four for biquadratics. In the arrangement of these rulers, all the respective coefficients lie in the same straight line. From a point of which line, as far removed from the first rule as the graduated scales are from one another, in turn, a straight line is drawn over them, so as to agree with the conditions conforming with the nature of the equations; in one of
And here's an actual shot of Buzz Aldrin in space with a slide ruler floating in the background:
One can imagine that nearly every major undertaking involving complex math utilized the slide rule in one way or another. Consider this description of the building of the Golden Gate Bridge:
Charles Ellis and Leon Moisseiff calculated forces for the Golden Gate Bridge with only a circular slide rule and a manual adding machine. They worked for months -- by hand -- sometimes solving equations with more than thirty unknowns.
Those guys weren't messing around.
My favorite slide rule store does happen to come from the space program, specifically from the Apollo 13 mission:
Perhaps the most impressive use of the slide rule was during the Apollo 13 crisis. Engineers had to recalculate data to guide the crew safely back to Earth—and they had to do it quickly. Richard Ogle describes how it went down:
""NASA had at its disposal whole banks of sophisticated computers, of course, but these were not programmed to do the basic calculations [Commander Jim Lovell] needed. So the engineers reverted to that most mundane pre-pocket calculator workhorse, the slide rule. Had the engineers at Mission Control been forced to do the necessary calculations on paper, Apollo 13 might well have missed the trajectory needed to bring it back to earth altogether. Instead the slide rule, designed specifically to exploit human beings’ highly developed visual acuity, allowed them to perform a set of complicated calculations in seconds.""
OK, we all get that the slide rule is an amazing device. But how do you truly grok it? You could pick one up on eBay for under $10 or so and work towards mastering it. Or, you could install the App on your phone for free, and start playing with it right now. But, as they say, if you truly want to understand something, teach it. And I know of no more recalcitrant a student than the computer. So I decided to program a slide rule.
Here's my solution:
(struct scale (symbol location abs-fn scale-fn) #:prefab)
(define C (scale 'C 'slide
(lambda (s)
(log s))
(lambda (a)
(exp a))))
(define D (scale 'D 'body
(lambda (s)
(log s))
(lambda (a)
(exp a))))
(define CI (scale 'CI 'slide
(lambda (s)
(log (/ s (/ 1 s))))
(lambda (a)
(/ 1 (exp a)))))
(define DI (scale 'CI 'body
(lambda (s)
(log (/ s (/ 1 s))))
(lambda (a)
(/ 1 (exp a)))))
(define A (scale 'A 'body
(lambda (s)
(log (expt s (/ 1 2))))
(lambda (a)
(expt (exp a) 2))))
(define B (scale 'B 'slide
(lambda (s)
(log (expt s (/ 1 2))))
(lambda (a)
(expt (exp a) 2))))
(define R (scale 'R 'slide
(lambda (s)
(log (expt s 2)))
(lambda (a)
(sqrt (exp a)))))
(define K (scale 'K 'body
(lambda (s)
(log (expt s (/ 1 3))))
(lambda (a)
(expt (exp a) 3))))
(define (make-slide-rule)
(let ((offset 0))
(lambda (action . args)
(define (align s1 v1 s2 v2)
(cond ((and (eq? (scale-location s1) 'body)
(eq? (scale-location s2) 'slide))
(set! offset
(- ((scale-abs-fn s1) v1)
((scale-abs-fn s2) v2)))
offset)
((and (eq? (scale-location s1) 'slide)
(eq? (scale-location s2) 'body))
(align s2 v2 s1 v1))
(else
(error (format "Must align body to slide, not ~a to ~a"
(scale-location s1) (scale-location s2))))))
(define (read s1 v1 s2)
(cond ((and (eq? (scale-location s1) 'body)
(eq? (scale-location s2) 'slide))
((scale-scale-fn s2) (- ((scale-abs-fn s1) v1) offset)))
((and (eq? (scale-location s1) 'slide)
(eq? (scale-location s2) 'body))
((scale-scale-fn s2) (+ ((scale-abs-fn s1) v1) offset)))
(else
(error (format "Must read from slide to body, or body to slide. Not ~a to ~a"
(scale-location s1) (scale-location s2))))))
(case action
((align)
(apply align args))
((offset) offset)
((read)
(apply read args))
(else
(error (format "Unknown slide rule command: ~a" action)))))))
I found this page especially useful in developing my implementation.
What I learned from this little coding exercise was that there's really only two operations that you can perform with a slide rule: slide it and read it. So I implemented those two operations: align and read. For example, to perform basic multiplication, you align the C and D scales, and then read the value off the D scale relative to the C scale. Or, in code:
(define sr (make-slide-rule)) (sr 'align C 1 D 5) (sr 'read C 3 D) ;; => 15
And here's an example of computing X3 using the K scale:
(define sr (make-slide-rule)) (sr 'align C 1 D 1) (sr 'read C 3 K) ;; => 9
I definitely appreciate that by implementing more advanced scales, you could knock out some pretty hairy math with relative ease.
Don't get me wrong, I love me a calculator (even with its flaws) and gladly perform even the most basic mathematics on it. But from a design and hacking perspective, you really can't beat the mighty slide rule. It's definitely worth taking the time to understand how it works and why it was such an effective tool for so long.
My parents are golfers. Me, not so much. Actually, make that not at all. Years and years ago my parents tried to help interest me in the sport but it didn't take. I think I played a grand total of one par 3 course. Yet when I realized that we were merely minutes from the East Potomac Golf Course, and that the course was not only open to the public, but quite affordable, I suggested to my parents that I play a round with them. I figured I'd hit a few balls, and if nothing else, get a nice walk in while I watched them show off their skills.
And this week the stars aligned: my parents were in town, the weather was perfect and I could book a 1:06pm tee time. And so I did.
We arrived at the Golf Course 45 minutes early in the hope that I could hit a few balls on the driving range. Our plan came together nicely. My Mom gave me about 10 minutes worth golf lessons, the three of us hit a bucket of balls and off we went.
We played the White Course, which consists of 9 holes. And I've got to say, when we started that first hole and I couldn't even see the flag at the other end, I was a bit intimidated. Actually, make that very intimidated. My brain tried to process what I was seeing: 141 yards away was a tiny little cup that I was expected to get a tiny little ball into.
Still, I followed my Mom's advice (keep that back swing short!; keep that left arm straight!; relax!) and what do you know, I actually managed to do OK. In fact, I left the course feeling quite proud of myself. I'd spent most, though not all, of the time on the actual fairway, didn't hurl a club, didn't throw a temper tantrum and managed to eek out a few beginner's luck shots. I did get in that nice walk as well as the joy of sharing a game with parents that they love.
Good times!
This DIY digital microscope project looked like a no-brainer to experiment with. So, I did. What makes the project work is the lens from a cheapy keychain laser pointer. I picked one up at CVS (the Laser Chase II) for under $3.00:
I took a needle nose pliars to it and ripped it shreds. When I was done, I had the tiny lens extracted. As suggested here, I mounted the lens by fitting it into a bobby pin and taping the bobby pin to the phone. Here was my setup, minus a tripod:
Yes, I'm using a bit Play-Doh to keep the flashlight upright in that plastic cup. And yes, I used the packaging of the laser pointer to make a slide and base for my samples. Hey, use what you've got, right?
And the results? Well, I certainly got up-close photos. I'm not sure I really captured anything that remarkable, but I'll have to keep an eye out for some more interesting specimens. The photos below are of a snippet of leaf and my saliva. As quick experiments go, I've got to say, this is a fun one. For $3.00 and 20 minutes of your time, it's hard to beat.
What the video that inspired this all:
As a make-a-website-mobile-friendly project was winding down, I decided to pop over to Google's Mobile Friendly Test Tool to confirm what Firefox's Responsive Design Mode and my actual cell phone showed me: the site was ready for mobile use.
And of course, Google's Tool gave my work a big 'ol F-. It explained to me that the site was most certainly not mobile friendly and showed a screenshot as the evidence.
In Google's defense, the screenshot did show a pathetic mobile experience, as it showed the desktop site crammed into a tiny window; not at all what I intended.
And so began the anger and denial. The anger came from the Tool's lack of specific detail. How hard would it be to show me exactly what files Google was accessing and exactly what CSS was being applied? All I could find were links to general mobile design guidelines, not helpful.
The denial was just the classic developer response. Surely the tool was grabbing an outdated version of the page. I changed the HTML on the front page and hit refresh. D'oh, it showed the most recent change.
Surely the tool was refusing to pick up mobile.css. I hit refresh on the tool again and, D'oh, I watched in the access logs as it downloaded mobile.css.
Surely the tool was ignoring my @media screen directive within mobile.css. I added the rule:
body {
borer: 4px dashed purple;
}
and hit refresh. D'oh, the tool gladly reran the test, showed me the ugly purple border *and* failed my work.
My phone and Firefox were showing the right version, but Google wasn't. What about another site? I bounced over to MobileTest.me and tried the site there. It showed up just like I wanted it to.
So odd, it was definitely Google's fault.
And then I looked at my specific CSS. The original site was coded years ago, back when the best practices of CSS were still in flux. The result was that I had to do some pretty creative things in mobile.css to undo the craziness in style.css. One unusual line of code was this guy:
body {
...
min-width: unset;
...
}
I changed that to:
body {
...
min-width: 100%;
...
}
And Bam!, Google's Mobile Tool showed me a nearly perfectly rendered mobile site. There was some funkiness in the header of the site, where the logo was getting overlapped with the site's tag line. But still, it was a huge improvement. I looked for more suspsicious CSS and made this change:
#title {
...
position: unset;
...
}
to
#title {
...
position: static;
...
}
And, problem solved!
So apparently Google's CSS handling is just a bit more restrictive than my mobile phone and Firefox's. Definitely something to keep in mind when trying to please Google's Mobile Friendly Tool and more importantly, the Googlebot, which no doubt uses the same logic.
I was chatting with my Dad last night and the topic of calculators came up. My Dad, a Biology Professor for many years, had strong feelings about these magical little devices and how they impacted his students. The problem, he explained, is that the calculator always gives you an answer. And because the answer is on a calculator (or in an Excel Spreadsheet, or part of a Matlab Prompt session, or echo'd next to an R prompt) it has the bias of appearing as truth. The result: his students would blindly hand in answers that with even a little thought showed them to be ridiculous.
So what's the solution, I pressed back?
Simple, he explained: before you starting using the calculator figure out a guess as to what you believe the solution should be.
If the solution and your guess match, awesome!
If the solution and your guess don't match, that's just as important: why not? Was an assumption of yours off? Or, did you merely type in an extra zero when keying in your inputs?
Solid advice Dad, and one I'll be using from now on.
I'm a big proponent of allowing everyone, including kids, to have an online presence. Blogging, Facebook, Twitter; give me a few minutes and I'll be glad to step on my soapbox and preach as to their value. But Snapchat? Well, not so much.
Snapchat as I first experienced over a year ago is an app custom built to frustrate parents. For those who need a refresher, Snapchat is the app that allows you to send a message (typically a photo) and it gets automatically "deleted" after the receiver has viewed it for a few seconds. Deleted is in quotes because this is the web and computers and such, and nothing should ever be considered deleted.
In other words, it's practically inviting you to undress, take photos of yourself, send them to your friends.
OK, perhaps not. But that's what the doomsday fear is. And I can't blame parents who worry about what kind of mischief their kids are going to get into with an app that appears to provide a behavioral free pass.
From my perspective, Snapchat's lack of history means that you lose all the archival benefit of web publishing. Those photos you snapped of your buddies at the football game all disappear with Snapchat. But wouldn't it be cool to see those photos 30 years from now? Trust me kids, it would be.
But enough Snapchat hate, thanks to this article: Why Your Kids Love Snapchat, and Why You Should Let Them I'm willing to re-think the service.
The premise of the article is that many of the negative unintended consequences of typical social networks are avoided with Snapchat. Consider the evils of the Like button:
Most visual platforms put feedback from peers at the center of the experience. Life on Instagram, for example, is as much about the rush of scoring likes as sharing something creative with peers. Many users view likes as a barometer of popularity and even self-worth, with some even deleting posts that haven’t drawn enough attention. For tweens and young teenagers, the yearning is so powerful that many post content designed only to collect likes (the popular “rate for a like” post, for instance, offers to rate friends on a scale in exchange for a like). They may follow “Instagram stars” with hundreds of thousands of followers, observing what appear to be perfect lives that are, in reality, perfectly curated.
I suppose it boils down to this: what if you just want a way to chat with your friends? You're not interested in recording every moment for posterity, or leaving a digital footprint to impress colleges, or leading a revolution. You just what to say Hey. Well, it's hard to argue with the crude effectiveness of Snapchat.
Read the article and snap on!
I don't know much about law, but I know this: You're innocent until proven guilty. At least I've watched enough TV dramas to think I know this. So here's the question: where was this statement originally codified? Surely it's in the Constitution or some other founding document; right?
I got curious enough to look, and it turns out, it's not:
The Anglo-American reverence for the maxim does pose an interesting conundrum: it cannot be found in Magna Carta, the English Bill of Rights of 1689, the Declaration of Independence, or in the Constitution of the United States; and not, I might add, in the works of the great English jurists, Bracton, Coke, and Blackstone.
The principle isn't officially codified until 1895, when the Supreme Court made it official. The short version of the story is this:
We can know exactly when the maxim formally entered American law: through a Supreme Court decision of 1894, Coffin vs. U.S. A lower court had refused to instruct the jury that "The law presumes that persons charged with crime are innocent until they are proven by competent evidence to be guilty". The appeal to the Supreme Court was based in part on the lower court's refusal.
By the way, they won the appeal. The Coffin decision contains a historical attempt to map out the history of innocent until proven guilty and goes as far back as Deuteronomy. The recounting would make a Talmudic scholar proud.
It's remarkable to think that an absolute bedrock principle of American law was only codified nearly 120 years after the country's founding.
Next thing you're going to tell me that that Under G-d wasn't added to the Pledge until the 1950's.
This map elegantly explains why nobody around here gets Trump:
And within those splotches of purple, Arlington is extra purple:
Seriously, the guy won our state but came in a distant 3rd place locally.
Who's up for a field trip to Buchanan County where Trump earned nearly 70% of the vote?!
Of course, Buchanan's 70% of the vote only netted Trump 1,586 votes, whereas his poor turnout in Arlington earned him 3,698 votes. Tricky, eh?
Still, around here you're probably going to have better luck getting support for a gun store than you are getting support for Trump. We just don't get it.
Arlingtonians are freaking out. There's talk of a gun store opening up in the community and people have gone downright apoplectic. Over 2000 of my neighbors have called on the building and gun store owner to cease and desist. I think they're wrong to do so, and more importantly, my guess is that they think they're wrong, too.
Allow me to explain.
Imagine for a second that you get a call from your Aunt Louise down in Real Virginia. She's absolutely furious. She explains: "they want to open up a Planned Parenthood next to a children's school. How can they be so brazen as to put this factory of death next to our children?! The people who run this Planned Parenthood don't share the same values as the community, the building owner should refuse to provide them with a lease!"
You take a deep breath and try to calm good old Aunt Louise down. First off, you explain she doesn't really know what goes on at Planned Parenthood, she only knows to repeat the same talking points as her uninformed friends. In fact, you wouldn't be surprised if given time, the community would embrace the Planned Parenthood. Besides, it's effectively a business: if people don't go to Planned Parenthood, it will close up on its own. Supply and demand is the ultimate equalizer.
You'd agree with her that the optics of having a Planned Parenthood next to a school was unfortunate, but abortions don't just jump off the shelf, do they? People who want to find Planned Parenthood's services will find them. Those that want to walk on by, will do just that.
When that line of reasoning gets you nowhere, you'd try a different tact: operating a Planned Parenthood is completely legal. In fact, the person that's being disruptive is Aunt Louise and her friends; they're the ones that are putting a stumbling block in front of a perfectly valid business.
Aunt Louise, you'd gently say, you're being prejudice; as in you've pre-judged this business and the people that work there. Perhaps the doctors and staff at the Planned Parenthood are jerks, or worse. However, it's far more likely they're just like you and your friends, they're your neighbors after all. And besides, you might a learn a thing or two about hot button issues by talking to people who share a different view, rather than listening to the same voices. By being closed minded, you're hurting your community and passing on a chance to grow as a person.
When none of that worked, you'd pull out the ultimate card: America. Aunt Louise, you'd explain, we live in this remarkable country where individuals live side by side with those who dress, look, believe, speak, pray, eat, love, work and do just about everything else differently. As Americans we firmly hold our own beliefs, yet just as importantly, leave space for others to hold theirs. Every day we live the motto: E pluribus unum, Out of many, one. Every once in awhile our community gets tested: do we truly believe in allowing the many to thrive? It's tempting to go the easy route and reject what we're not comfortable with. But that's not America. American needs the many. If this establishment isn't breaking the law, then you need to let them be. Hold fast to your beliefs, and at the same time, fight to allow others to do the same. It's the American thing to do.
Do you think Aunt Louise is convinced? Probably not. But replace Planned Parenthood with Gun Store and you see, it's not such a crazy argument to suggest that a business, even one you're not comfortable with, should be aloud to set up shop in Arlington.
Do it for America.