Joho the Blogmisc Archives - Joho the Blog

August 4, 2018

Unlocking picture frames in Keynote 8

In 2015, I posted about a way to unlock the picture frames that for some reason ship with Keynote but are not accessible within Keynote. They’re there but they don’t show up on the pull down, so you can’t use them.

In 2018, with Keynote at version 8 + change, the same technique works. With the same warnings. So, if you want to give yourself considerably more than the 14 frames that the menu shows you, go here, follow the instructions carefully, and most important: do not blame me. (The replacement file I link to still seems to work.)

1 Comment »

July 20, 2018

Thomas Edison’s endorsement of MIT

Someone alert MIT’s recruitment office: Thomas Alva Edison was a fan.

Here’s a 1916 letter from a father asking Edison’s advice about where to send his son who is “not a very studious boy” but is “mechanically inclined”:

Letter to Edison with his recommendation of MIT

Edison’s handwritten response says, as best I can make out:

My advice is to send him to the Mass Institute of Technology – Boston of all the young men out of college which I have employed those from the Mass Tech were far superior to all others.”

Source: “Letter from Harry C Shaaber to Thomas Alva Edison, October 30th, 1916,” Edison Papers Digital Edition, accessed July 20, 2018, http://edison.rutgers.edu/digital/document/E1632AD./a>. The ever-vigilant Lewis Brett Smiler sent it to me.

2 Comments »

May 8, 2018

Net Neutrality red alert

The Senate is voting on Net Neutrality.

Last chance before we throw the Republicans out of office.

1 Comment »

April 4, 2018

A history of Internet addresses

For something I’m writing, I wanted to show what an Internet address was like before the World Wide Web introduced the http:// and the www., but after the DNS — domain name service — had been introduced. So I asked my friend Scott Bradner who has been involved in Internet governance for a very long while. He recently retired after fifty years at Harvard University where he managed networks, was chief security officer, and did so much more.

Scott is a generous teacher, so he answered far more fully than I’d hoped. Here, with his permission, is his response:


 

not such an easy answer – some facts
the ARPANET moved from NCP to TCP/IP on 1 Jan 1983
before then the Network Control Protocol used network addresses that looked like: 9 (the address for the PDP-10 at Harvard)
after 1 jan 1983 the addresses looked like 128.103.1.1 (also the address for the PDP-10 at Harvard)
and that is what the addresses look like to this day (IPv6 addresses look different)
before the DNS was deployed people used a “hosts.txt” file to map a human friendly hame into a network address
so the hosts.txt file pre 1/1/83 had the following entry for harvard
Harv10 9
and the entries in hosts.txt file for harvard after 1/1/83 was
Harv10 128.103.1.1
Harvard 128.103.1.1
and later (still before DNS was deployed) another line was added:
harvard.harvard.edu      128.103.1.1
the user would type something like “ftp harv10” and the system would look up the name in hosts.txt to get the address
all DNS did was to turn the hosts.txt file (which was maintained centrally and was, by definition, out of
date by the time you finished downloading it) into a distributed set of servers/databases – each of which could
be kept up to date on its own and since that database was queried in real time, the response would be up to date
but even with the hosts.txt or DNS you could & still can use the underlying network address itself
e.g.: ftp 128.103.8.36 (my personal computer at the Harvard Psychology Department)

Comments Off on A history of Internet addresses

November 25, 2017

Milkweed’s skeleton

Here are two photos of a milkweed plant taken within seconds of each other, at early dusk, using my Pixel mobile phone. One is with the flash and the other is without.

milk weed without flash

milk weed with flash

 

I think it broke my Pixel’s lighting algorithm.

1 Comment »

July 12, 2017

Net neutrality still matters. A lot.

Net neutrality regulates the organizations that provide access to the Internet — to our Internet — to make sure that they do not play favorites.

Net neutrality is not a layer on top of the Internet. It is not a regulation place on the Internet. It is the Internet, as Doc Searls and I explained way back when in a post called World of Ends.

Tell the FCC that this matters to you.

Comments Off on Net neutrality still matters. A lot.

June 3, 2017

1.5 random thoughts

1. Life Pro tip: Aim at what you hit.

2. A metaphor that may come in handy someday: As undignified as a child climbing a slide.

1 Comment »

April 6, 2017

Not everything broken is in beta


CC-BY Kevin Gessner https://www.flickr.com/
photos/kevingessner/3379877300

A White House official has blamed the bumpiness of the ride so far on the White House being in “beta.” This has provoked Jennifer Pahlka — the founder and Executive Director of Code for America and a US Deputy Chief Technology under President Obama — to respond with heartfelt despair, worried that the tools she and her cohort brought to the Obama White House are now being used against all that that cohort accomplished.

It pains me to think that Pahlka, who is a hero of mine, has any regrets or fears about the after-effects what she has done for this country. For the foreseeable future, I think she need not worry about how the Trump administration is using the tools and mindset her cohort introduced to the White House. “This new administration lacks the understanding, competency, and value system to use those tools.”This new administration lacks the understanding, competency, and value system to use those tools.

Here’s the passage she cites from a New Yorker article
:

But, on Friday morning, Mike Allen, Axios’s editor-in-chief, reported that one of the officials in the meeting “views the Trump White House in terms that could be applied to the iterative process of designing software. It’s a beta White House.”

Allen went on, “The senior official . . . said the White House was operating on similar principles to the Trump campaign: ‘We rode something until it didn’t work any more,’ the official said. ‘We recognized it didn’t work, we changed it, we adjusted it and then we kind of got better . . . [T]his was much more entrepreneurial.’ In the White House, he said, ‘we’re going to keep adjusting until we get it right.’ ”
— John Cassidy, “The Keystone Kops in the White House” The New Yorker

“Beta” means “We rode something until it didn’t work any more”?? No, this official is describing what happens when you wake up one day and find out that your DVD burner is no longer supported by the latest upgrade to your operating system. That’s the opposite of “beta.”

The White House isn’t in beta. It’s in freefall.

Nevertheless, this passage bothers Jen because she and her colleagues used to say the same things about making incremental improvements when they were in the White House working to fix Healthcare.gov, the student loan process, and so much more. She writes:

Trump’s team is using the language of agile development to describe how they will strand millions of Americans without healthcare and ban Muslims from entering the country….

What are agile methods without the moral core of the movement for 21st century government, a commitment to users, aka the American people? My heart hurts so much I’m not sure my head is working quite right, and I don’t know if this bizarre application of agile methodologies is a farce or frighteningly effective.

Yes, agile programming can be used for evil purposes, but I don’t think Jen’s cohort should feel they carelessly left a weapon lying around the White House. The Trump administration lacks agile programming’s implicit understanding of how the future works, its theory or change, and its implied values. That’s why, at least so far, “the Trump White House is so non-agile that it’s not even the opposite of agile”the Trump White House is so non-agile that it’s not even the opposite of agile.

Agile software development is characterized by at least two relevant ideas: First, big projects can be chopped into smaller units that can be developed independently and often simultaneously. Second, agile projects are iterative, proceeding by small steps forward, with occasional small steps backwards. Both of these points stand in opposition to the prior “waterfall” approach?—?so-called because he project diagram looks like a series of cascading waterfalls?—?in which the steps for the entire project are carefully mapped out in advance.

To paint the differences too starkly, waterfall development is about command and control. Somebody maps out the flow, dates are assigned to the major phases, and managers make sure the project is “on track.” An agile project is instead about trust and collaboration. It breaks the software product into functional units — modules — each with an owner. The owner is trusted to build a module that takes in data in an agreed-upon format, operates on it, and outputs the result in an agreed-upon format. These independent module developers have to work closely with all the others who are relying upon their work, whether a module figures out what permissions a user has, determines if an arrow has hit its target in a game, or confirms that landing gear have been fully extended.

Agile development therefore cedes control from the Big Boss to the people most directly responsible for what they’re building. It needs a team — more exactly, a collaborative community?—?in which each person:

  • Understands precisely she needs to do

  • Understands how what she produces will serve everyone else’s input and output requirements

  • Can be trusted to get the job done well?—?which means getting it right for everyone else

  • Is in close communication with everyone relying upon her module and upon which hers relies

  • Understands the overall goal of the project

As far as anyone can tell from the outside, exactly none of this applies to the current White House.

Second, agile development is iterative?—?a series of small changes because it assumes that you cannot fully predict how exactly the end product will work, or even what exact functionality it’s going to provide. That is, agile development assumes that life, the universe, and all that are so complex that precisely planning a project from beginning to end requires an act of arrogance that borders on stupidity. And measuring the success of a project by its micro-adherence to a fixed schedule in a world that is changing around it rewards stubbornness over serving end-users as well as possible.

Now, Donald Trump’s preference for deal-making over policy
aligns with iteration’s acceptance that “the future is not the next card in the deck but is what we make of our hand”the future is not the next card in the deck but is what we make of our hand. But Trump’s style of deal-making is based on the superior skill of the individual (Donald), a ruthless commitment to “winning,” and is all about one big step?—?the end result?—?not a series of small changes. Ultimatums of the sort that Trump issued once he saw he was losing the health care battle are the opposite of the incrementalism of iteration. An iterative approach is exemplified by the Democrats’ approach: Let’s tinker with Obamacare to fix what needs fixing.

So, Trump’s White House is anything but agile.

But neither is it proceeding through a waterfall approach, for that requires a commitment to an end result, a rational and realistic understanding of the steps necessary to get there, and well-coordinated managers who are all on the same page. The Trump White House does have a commitment to end results, expressed as mob-inciting campaign promises that are often at the sweet spot where delusion and heartlessness intersect on the Venn diagram of policy-making. Beyond that, this White House exhibits none of the processes, commitments, or accountability that are the hallmark of waterfall development.

Jen’s cohort left tools the White House can’t use because it lacks agile development’s understanding of how change happens and agile’s fundamental trust in its community of practitioners. In short, Jen’s cohort brought a community to a knife fight.

Posted also at Medium.

1 Comment »

March 25, 2017

How a little bit of data ruined my morning run

Since I was 21 years old, I’ve gone through long stretches where I have “run” outside for exercise — in quotation marks because I am passed by people who are running so slowly that I feel bad for them until I remember that they passed me. I’ve gone years running infrequently, and then other years I’ll run 3-6 days a week. But three things have been consistent throughout this: I don’t like running, I always run the same set route, and I have always run for distance, not for time: I set a course and don’t care how quickly I complete it.

That’s almost true. I care enough that I time my runs, but I don’t try to run faster in order to beat yesterday’s time. It’s just a little bit of long-term quantified knowledge that gives me a rough indication of what sort of shape I’m in as a jogger.

Beyond that smidge of data, I have gone out of my way to be data-free about my route. I don’t know how long it is. I therefore don’t know how long it takes me to run a mile. I therefore don’t know where the halfway point is, or the quarter markers. (My route’s a loop, so the halfway point is not obvious.)

Until today.

My Pebble smartwatch is declining, so I looked for a running app on my phone. The one I rather randomly chose gathers info beyond the duration of the run, but I just wasn’t thinking well about it when I plugged in my my headset, picked some upbeat music, and set off this morning.

“You’ve run one mile,” said the woman’s voice in my ear when I was a block away from the pond. I cannot unhear where the first mile marker is. And because I didn’t want to stop to fiddle with the app, I also know where the second mile marker is. And I know my home is 0.03 miles short of being the third mile marker. I also know how fast I run.

I don’t want to know any of this, although the distance and my speed are both a little better than I would have guessed. So, yay for being marginally less pathetic than I’d thought?

The real problem is knowing where those mile markers are.

I’ve tried lots of other sorts of exercise, and I haven’t stuck with any of them. They’re too boring, they take too long to get to, or — this is the crucial one — they involve counting. How many laps? How many reps? Am I at the twenty minute mark yet? It’s not the numbers that bother me. It’s knowing that there’s some knowable quantity I have to complete in order to be done. Doing a countable exercise is like watching a clock tick. You want to slow down time? Pay attention to it.

Running wasn’t like that. Now it will be. I’ll know when I’m at the one-third mark, and, more to the point, I’ll know when I haven’t even reached the one-third part. This little bit of data turns the entire run into a set of tasks that must be accomplished in sequence — a set of tasks that at any moment during the run I know have not yet fully accomplished.

For the past forty-five years, I’ve managed to run with some regularity by running through space. Now I’m running through time, and that takes much longer.

4 Comments »

February 1, 2017

How to fix the WordFence wordfence-waf.php problem

My site has been down while I’ve tried to figure out (i.e., google someone else’s solution) to a crash caused by WordFence, an excellent utility that, ironically, protects your WordPress blog from various maladies.

The problem is severe: Users of your blog see naught but an error message of this form:

Fatal error: Unknown: Failed opening required ‘/home/dezi3014/public_html/wordfence-waf.php’ (include_path=’…/usr/lib/php /usr/local/lib/php’) in Unknown on line 0

The exact path will vary, but the meaning is the same. It is looking for a file that doesn’t exist. You’ll see the same message when you try to open your WordPress site as administrator. You’ll see it even when you manually uninstall WordPress by logging into your host and deleting the wordfence folder from the wp-content/plugins folder

If you look inside the wordfence-waf.php file (which is in whatever folder you’ve installed WordPress into), it warns you that “Before removing this file, please verify the PHP ini setting `auto_prepend_file` does not point to this.”

Helpful, except my php.ini file doesn’t have any reference to this. (I use MediaTemple.com as my host.) Some easy googling disclosed that the command to look for the file may not be in php.ini, but may be in .htaccess or .user.ini instead. And now you have to find those files.

At least for me, the .user.ini file is in the main folder into which you’ve installed WordPress. In fact, the only line in that file was the one that has the “auto_prepend_file” command. Remove that line and you have your site back.

I assume all of this is too obvious to write about for technically competent people. This post is for the rest of us.

4 Comments »

Next Page »