What happens when coding stick meets coding_pad? It’s been well over 25 years that I wrote any assembler code. But I ran across this pad of coding sheets in a closet and I had this urge to use it. Of course I don’t have a mainframe to test it, but it can’t be wrong. Can it?Continue reading “Hello World in 370 Assembler”
What good is a coding stick without a coding pad? It’s hard for many to conceive of a time when computers were programmed by people with only pencils and paper, sitting at mostly empty desks with no distractions, other than the window and the clock on the wall. So how did that work?Continue reading “Coding Pad”
Punched cards have been around for far longer than computers have. The earliest form that I am aware of is the Jacquard Machine (circa 1800) to control a loom. Charles Babbage incorporated the idea into his Analytical Engine (circa 1837). Herman Hollerith designed tabulating machines around the concept and saved the 1890 US Census. His design and company evolved to become the IBM Corporation. This is the card of which I speak…Continue reading “Punch Card”
I needed to represent a Finite State Machine (FSM) for my Smoker Controller project. I could have gone with the pencil and paper route but what I learned in dot: command line utility for drawing graphs was that there are better tools. Since this project was documented in markdown from the start I looked for a way to do it all in markdown. It turns out there is a plugin called
mermaid that does everything
dot does without the compile step. But with a different syntax. 🙁 Many markdown processors have this plugin pre-installed. 🙂 I am using Joplin and it works just fine.
I wanted to represent a Finite State Machine (FSM) for my sump pump monitor. Grabbing my coding stick, I create the FSM on paper in my project journal. Then I take a photo of this and I’m done.
But not really done because the photo is 3.3 MB. I download it from Google Photos and open it in my Macbook using Preview. I select the portion of the page with the selection tool and copy this part of the image to the clipboard and then I use Preview’s “New from Clipboard” command to create a PNG image file. This file is still 1.7MB.Continue reading “dot: Command Line Drawing Tool”
After July 2019, Google Photos will no longer sync with Google Drive. Whether or not this is a good thing depends on specific use cases. Regardless, it is happening and this impacts the way that I use Photos. Generally when I take photos on my Pixel 3 phone, I just let the system handle things. The phone syncs with Google Photos in the cloud. Google Photos syncs with Google Drive and Apple’s Time Machine backs up my Google Drive onto a local disk drive. I have been comfortable with this. I am not a heavy curator of my photos. I have some albums in Google Photos but generally I want my photos organized by creation date. This is important because the files that Google syncs to my Google Drive do not include the album folders or meta data. I’m ok with this.Continue reading “Dealing with Google Takeout in Mac OS”
Rummaging through some old files, I ran into an artifact originating from that time before computers, although this was still in use long after computers became available. Such is the nature of progressive automation that we resist it for long after it first becomes feasible. Eventually the old ways are tossed aside, leaving piles of obsolete artifacts. For some reason I kept one.
The artifact is called a keysort card, also called the McBee Keysort. Its purpose was to record data in such a way that statistical reports could be produced that summarized data across hundreds or thousands of these cards. All of the work to do this was performed manually.
After upgrading my Nexus 7 to Loliipop (5.0) I find that it is unusable due to lagging response times. I tried deleting the cache and other remedies I found online but nothing helped. It’s just too slow. I want to go back to KitKat (4.4.4). I found a few tutorials about downgrading that differ in a few details. Some are geared to Windows users, some are for Macs. For a number of reasons I want to do this on my Mac Mini. Continue reading “Downgrading the Nexus 7”
I had installed the Android File Transfer app in order to make it easy to load music onto my Android phone. I didn’t realize that this app doesn’t behave like a typical Mac app. It includes an agent helper app, a daemon really, that gets started at login and monitors for Android USB connected devices. I was unaware of this for some time and generally it does not cause problems. However when I wanted to reflash my Nexus 7 tablet I ran into problems with the File Transfer Agent competing with the Android Platform Tools ADB program for control of the device.
My preference for utilities on my Mac is for them to not run until I activate them explicitly. Yes it looks swell to have a program pop up when I plug in the USB device, but I would prefer to manually launch it. I don’t like magic… Continue reading “Android File Transfer – Magic Begone!”
Periodically I check out the Apache error and access logs in order to find things that I can fix or improve with a little work. Today I noticed a few errors for bad URLs coming from unfamiliar IP addresses. The error I got is:
(36)File name too long: [client xx.xx.xx.xx:xxxxx] AH00036: access to ….
Looking at the filename, it is way too long but it is also very peculiar. It starts off with a valid WordPress folder name but appends a long string of folder names where the folder names are prefixed with an underscore and suffixed with a comma. I checked this against the actual folders and it matches existing paths in my WordPress instance. The garbled path ends in an actual file name. To make it even weirder, this garbled path name has a plus sign followed by another garbled path name, multiple times. All together it’s about 800 characters long. WTF?… Continue reading “Gems from the error logs…”