The work you do while you procrastinate is probably the work you should be doing for the rest of your life.
Jessica Hische
The work you do while you procrastinate is probably the work you should be doing for the rest of your life.
Jessica Hische
The Literary Hub's daily newsletter and Austin Kleon's weekly newsletter are delights to receive.
I decided at one point in my life that I never wanted to be anything that would not allow me to be anything else I wanted to be … I ended up being nothing that I can currently identify, which I suppose means I got my wish.
from Laura Warholic by Alexander Theroux
Last night, I purchased and installed from the Mac App Store the program Network Logger Pro ($9.99).
Despite my belief that the Airport Time Capsule is not the problem with our connectivity, I still had to consider the possibility that it might be. So I started researching wifi problems with Airport Time Capsules. I compiled a small checklist of wifi settings to try in the Airport Utility (such as changing ipv6 to "link-local only").
I also discovered that the ATCs have a lifespan of 3-5 years -- not only for the hard drive, but also for the wifi components. Apparently, they get hot and wear down over years of being on all the time. So the ATC could be part of the problem after all. That is disappointing, but good to know. Time to start pricing another external drive and a new wifi router.
But let's take the ATC out of the equation: if I was relying just on the Frontier modem, would I still experience network outages?
So I started looking for programs or terminal commands I could use to create a log file to show that the outages are coming from the modem, not the ATC. It was during this research that I discovered Network Logger Pro.
Therein followed a series of brainwaves.
It takes a while for me to put things together...
I installed Network Logger Pro, which has graphs and stuff I can't begin to decipher.
<img src="http://tempblogfood.files.wordpress.com/2019/08/2e4c1-network-logger-pro.jpg" alt="" />
Now that my iMac is slurping data directly from the modem, Network Logger Pro records in its log the network up- and downtimes. Yes indeed, connected directly via Ethernet to the modem, I can see that I'm getting outages of several minutes at a time.
<img src="http://tempblogfood.files.wordpress.com/2019/08/2c5fd-log.jpg" alt="" />
So now I can call the tech guy, show him this log, and make the case that we should try a new modem. Once we're sure the modem and line are working well on my iMac, then we can tackle any wifi problems the ATC may have.
Update: the Internet went down as I tried to post this from home. So I'm posting this from work.
For Lent, I gave up listening to podcasts and adopted Mark Forster's Fast FVP at work.
Fast FVP worked great and accommodated a couple of enormous changes that occurred to me at my workplace.
A pile o' podcasts also silted up such that I could spend the next 50 days listening to them all. But I did get back to listening to audiobooks and other long-form items and webinar recordings I'd put off for "later."
Accd to the calendar I'm referencing, Eastertide runs from April 1-May 20. So here's what I'd like to do:
We've had very patchy Frontier DSL connectivity for over a week now.
It's uncanny that the DSL can work so flawlessly, so invisibly, that we take it for granted. But when connections are dropped and apps that normally update instantly instead stall out, then frustration rises.
I should say that everyone I've dealt with -- Frontier's telephone customer support and technicians -- have been polite, respectful, and seem knowledgeable as they work through their troubleshooting steps.
Here's what has happened since that first call:
The connection is still patchy, unfortunately. When the connection is up, the speed is acceptable. But the connection is not stable; we're losing connectivity a couple of times an hour -- sometimes a brief hiccup, other times for 20 minutes -- which renders the download speed (we're provisioned for 3 mbps) a moot point.
Today's technician really thought the problem was the Time Capsule. I pushed back on that. Why would it suddenly go wonky after three years of no problems?
Our set up is this:
I prefer having a wired connection to the modem so I can verify whether the patchy connectivity is coming from the wifi or the modem. If Liz's iPad loses connectivity, I can verify via Speedtest whether I've also lost connectivity. If I have, the problem is the signal from the modem, not the Time Capsule.
Liz and I are both getting our internet via the Time Capsule (she via wireless, me via wired), so it could be the weak link. But I'm more suspicious of the Frontier modem. We're an Apple household and I'm frankly loathe to believe this problem lies with the Time Capsule.
Connectivity is better today than yesterday, but not as stable as it was two weeks ago. We will give it a day or two under the normal stresses of email, transactions, streaming video, downloading, etc.
Until I can take my connectivity for granted again, I will likely roam the Frontier for some time to come.
We saw a trailer for an R-rated movie, and one of the rating justifications was for "pervasive language."
"So that means it's a 'talkie'?" my friend said.
Apparently this odd wording has been remarked on since 2005 or so, but I had not noticed it till then.
Following is a paragraph from a 2009 MovieChopShop post on the MPAA's vernacular:
And we all know about their little one-fuck, two-fuck rules that bump a PG-13 straight up to an R. But why does Reservoir Dogs have “strong language” while The Departed has “pervasive language,” and Pulp Fiction has “pervasive strong language,” when they really all seem like they might as well be about the same?
The Merriam-Webster site says pervasive can be neutral ("a pervasive sense of calm") but "is most often used of things we don't really want spreading throughout all parts of something," such as "a pervasive stench."
The M-W site ends with a shoutout to the MPAA:
... Beginning in the early 1990s, the MPAA started giving the R rating to movies with "pervasive language." Most movies have language throughout, of course. The MPAA is using the phrase "pervasive language" to refer to the frequent use of a particular kind of language: profanity.
Strong language? Profane language? Bankrupt language for an obsolete and purposeless ratings system?
Build a man a fire, he stays warm for an hour. Set a man on fire, he stays warm for the rest of his life.
The Internet
I complained I had no starter fluid, till I met a man who had no chain saw.
At my day job, there's an email I need to send every week. Same subject, same message. The recipients stay mostly the same, though sometimes there are changes in the lineup.
I don't want to have to manually create this email every week. I want the computer to do what computers are supposed to do: remember and do stuff for me so I don't have to remember and do it.
We use Outlook 2016 on Windows 10. Outlook lets you create recurring appointments, recurring reminders, and recurring tasks -- but not recurring emails. Fair enough. The other recurrences only bother you, but sending recurring emails can bother lots of other people.
Because our workstations are locked down, I cannot easily install any macro or automation software that could help me with this situation.
So here are two solutions I cooked up using just the tools available to me from Windows 10.
The first one made me feel like the Professor on Gilligan's Island creating a catapult from bamboo and coconuts. The second one is plainer but gets the job done.
Neither of these are exhaustively tested or vetted procedures, so use at your own risk.
Create a contact group in Outlook containing the message's recipients. Let's call it Recurring email group.
If the recipients list changes in future, then you only need to add or drop names in this group and nowhere else. The email template we create next will still work fine.
Microsoft describes the procedure in more detail, but here's the short version.
By default, templates are saved to C:UsersusernameAppDataRoamingMicrosoftTemplates.
You can specify a different path but it's easier to just accept the default; if you specify a different path, make a note to yourself of the file's location because you will need the file path in the next step.
I couldn't believe this is what I had to resort to, but it was. God bless batch files. Still incredibly useful little tools.
@echo off
cd C:UsersusernameAppDataRoamingMicrosoftTemplates
start "C:Program Files (x86)Microsoft OfficerootOffice16OUTLOOK.EXE" "Recurring email template.oft"
There are many ways you could write the batch file; for example, I could have entered qualified paths to both the .exe and the .otl. In this case, I did what made sense to me to do.
Save the batch file to a folder on your hard disk. An obvious place is your C:Usersusername directory, but anywhere will do. Again, remember where you saved it because you need it for the next step.
Before you go any further, double-click the batch file and make sure it works as intended (a new email is created with the contents of the template file).
Here's where our elaborate little Rube Goldberg contraption1 comes together.
<ol>
<li>The trigger is the time you want to send the email, such as every Friday at 11 a.m.</li>
<li>The action is to run the batch file. Navigate to the batch file and select it.</li>
</ol></li>
You can search Google or YouTube for more help on the Windows Task Scheduler.
Now, every Friday at 11 am, the Task Scheduler will fire off the batch file, which calls Outlook to open the template file, and a new email will open up -- ready to go -- for you to review and send.
There are lots of moving parts to this contraption. Glitches happen and a component may not fire off correctly.
So, set a reminder in your calendar for an hour or so after the email is supposed to be created, something obvious like "WAS THE EMAIL CREATED??".
It was when these two obvious ways did not work that I hit on the batch file method.
The second solution is more manual, but also less prone to gremlins in the system. Outlook task and calendar reminders always perform solidly.
We just spent hours to save minutes. You're welcome.
I have been posting a business/productivity/mastermindish type article every Sunday on LinkedIn for a few weeks now.
Usually, I take a post or part of a post I've published here first, revise it, clean it up, and post it.
The "Columbo" post is from an idea I read somewhere on Mark Forster's site, though I cannot now find the reference. I put a structure around it, added the Columbo references, a dash of 3 Principles, and there it was.
I had wanted to present this video compilation of Columbo's "just one more thing" tactic, but the studios restricted the video's playback to YouTube only. Shame.
So the only video I could really link to that worked with my article was the following short (under 10 seconds) video illustrating what you need to do when you hear that "just one more thing" gremlin in your ear.
[youtube=://www.youtube.com/watch?v=yM8ixOCpdxw&w=640&h=480]