This is my year for an iPhone update, and I received the new phone yesterday. Upgrading from my iPhone 12 Pro Max was more straightforward than I feared, and definitely more seamless than last time. I used Quick Start to transfer, and things worked as expected… mostly.
My service is with Verizon, and the new iPhone was purchased without any carrier affiliation. I was using the standard old-fashined SIM in the iPhone 12 Pro Max.
- Right before starting the process, I did a fresh iCloud back-up.
- I started up the new phone and selected Quick Start.
- I chose the direct transfer between devices. This did not take nearly as long as the warned estimation time.
- I followed the prompts and most things transferred seamlessly. I did not select carrier activation during this parocess.
- It provided me the option of transferring over my Apple Watch connection. I left the selection as-is. I did not unpair from the old phone or anything unintuitive as was required in the past.
- I use Microsoft Authenticator. My accounts did not transfer, but I realized I was not using iCloud back-up for Authenticator. I turned this on in the app on the old phone, and got the accounts to show up on the new one. However, for most of the identities I had registered, I had to re-estabilish the device to MFA for them. For Microsoft identities, this involved visiting https://mysignins.microsoft.com/security-info for each and generating the QR code dance.
- I also had to re-establish corporate management of my device, which involves Microsoft Intune and Defender installation. Attempting to re-enter the password to corporate email account is one way to make sure this is all getting kicked off.
- I had to restablish my Testflights by launching the Testflight app and re-installing. They did not find their way back to their locations in Springboard.
- Developer profile policies had to re-downloaded and re-trusted.
- Finally, I wanted to transfer the number to the new phone, which involves eSIM, now. This involved going to the Verizon portal and going through their “activate your own phone on an existing number” flow. In Verizon’s the instructions it led me to enter the id of the new phone’s second IMEI (which is apparently the second SIM identifier - “IMEI2” - in the Settings -> General -> About). Note, their documentation says the first IMEI is for an inserted SIM card. iPhone 14 Pro only has eSIM, but it shows IMEI and IMEI2; I provided IMEI2 to Verizon and got a green checkbox.
- I confirmed the transfer on the Verizon site, and it sat for a minute and eventually failed with an error saying to call their support line. It had at least half-way worked, however, as my old phone no longer got cellular singal. However, the new phone didn’t work, so I started the support call on another phone (oops).
- While waiting, I poked on the new phone, and eventually saw a top-level prompt in Settings that there was an activating step waiting. I noticed this as an operator was finally coming on the line; I pressed the confirm button in Settings, and the phone went live almost immediately. The support person had me perform a test call, but all was fine.
When reading this it may sound like a lot, but this entire process took probably 2 hours.
For my birthday this year, I was treated to a new Apple Studio Display. I’ve always been envious of Apple-branded monitors and have wanted one at least since I first saw the 30” Cinema HD display. I got the height-adjustable stand option and I don’t regret it a bit; the movement is very smooth, and the craftsmanship of the piece is great.
One thing of mention, however, is my experience with the built-in webcam. It has received a lot of bad press, with its image quality being mediocre, at best, especially in low-light situations. I should note that this is not my work webcam (which I use constantly through each day). I primary use it for calls to family, and often when my kids will come into and out of the call. For this reason, the Center Stage feature of the camera works very well, dynamically expanding and contracting the shot as people come in and out of range.
I’ve used it quite a bit, and I’ve found the picture quality acceptable, the audio quality much better than expected, and the overall experience very nice. I’ll always wish for better video quality, but I’m very happy with the camera’s currently level of performance - enough so that I’ve exclusively used the Mac for FaceTiming over the iPad Pro I have positioned immediately to the right of the screen.
First, I tried the Keychron Q1. I got one with a knob, which I like to use to control volume on my Mac, and which I dislike since the knob is in a key-shaped hole in the top case.
When I am programming (especially on Windows), I find I’m a heavy user of Home/End keys, and I find the traditional tenkeyless 85% keyboard more comfortable. Enter the Keychron Q3. No knob on this one.
I’m eager to experiment with a split keyboard for the first time in many years, now that Keychron has an Alice layout keyboard with function keys. It also has a knob with a proper circular case hole.
My switches sweet spot is Gazzew Boba U4T switches. I prefer lighter springs. I also love tall key caps, and find the Drop MT3 keycaps to be the perfect shape. They come in ABS and in PBT, but I vastly prefer rougher feel of the PBT. The 9009 and the 2048 are on my Q3 and Q1, respectively.
I’ve always had a love of tactile keyboards. For the past six or seven years I have loved using a WASD Code 87-key keyboard with Cherry MX Brown switches. Despite also having an example of the same keyboard with Cherry Clear switches, I clearly prefer the lighter spring weight of the Cherry Browns. This was enough for me, until two years ago when I was able to order an aluminum outer case for the same keyboard. I replaced the ABS plastic case with the much-heavier aluminum, and immediately preferred the added heft. Even though my beloved Model M keyboards were made of plastic, I always preferred their heft. They don’t move around on the desk, and they just feel solid.
Building and customizing keyboards has become quite a popular hobby in the past few years, and it seemed to me to be mostly focusing on unique key caps and lighting. This didn’t appeal to me, because half of my love of the Code is, while their keys are backlit, it is an extremely clean, utilitarian design.
Enter hot-swappable (no soldering required) switches. With the right keyboard, I can now tinker with how the switches themselves feel and sound, without the trouble of soldering.
This will be fun.
A good official tutorial exists
As prep for a learning presentation at work on the topic of KQL, I set out to turn a quick set of “primer” notes into a more thought-out blog post, and then hopefully a better presentation. Turns out, I quickly found a far better introduction to the language. This docs.microsoft.com tutorial is wonderful; it is simple and straightforward, and I used it for my talk.
Learn how to dig
So, rather than specifically a technical introduction, what is it that I am trying to share about KQL? Kusto is such an amazingly performant system, that using it can actually be fun.
What I want to convey in 15 minutes or less is how to discover what data you have, and how to conveniently dig. I have met a lot of engineers whose systems publish to a KQL system. They’ve had access to the data for years, and don’t know how to discover what’s there.
The noise of that sea of poorly conceived and messy telemetry can be intimidating. Don’t let it be.
So, my old KQL primer has become the following “things to learn”. When I share these, I always hope it sparks a little curiosity. That’s all.
Learn the following concepts, as quickly as possible.
-
Browse tables, looking at a few random records.
Perhaps union all your tables together:
union traces, exceptions, ... |
-
Filter on timestamps. Most KQL UIs will allow you to paste the text of a timestamp and it will wrap it in a datetime() declaration.
| where timestamp > ago(1d)
| where timestamp > [PASTE TIME] and timestamp < [PASTE TIME]```
| where timestamp between (datetime(2022-01-12 19:54:00) .. datetime(2022-01-12 20:10:54)))
-
Search for strings. Get hooked on Kusto’s amazing indexing.
// no substring matches
StormEvents
| where * has "caro"
// includes substring matches
StormEvents
| where * contains "caro"
-
Create your own columns, on the fly. Compute new values, or pull data from a column with a complex data object out to its own column.
StormEvents
| extend Duration = EndTime - StartTime
Covid19_Bing
| where Id == "/US/North Carolina"
| extend ConfirmedValue = Confirmed.Value,
ActiveValue = Active.Value,
DeathsValue = Deaths.Value,
RecoveredValue = Recovered.Value
-
Remove columns you don’t need.
| project Id, ReportDate, ConfirmedValue, ActiveValue, DeathsValue, RecoveredValue
-
Group results and run functions over the set:
Covid19_Bing
| where Id == "/US/North Carolina"
| extend ConfirmedValue = Confirmed.Value, ActiveValue = toint(Active.Value),
DeathsValue = Deaths.Value, RecoveredValue = Recovered.Value
| project Id, ReportDate, ConfirmedValue, ActiveValue,
DeathsValue, RecoveredValue
| summarize count(), toint(avg(ActiveValue)) by bin(ReportDate, 31d)
Note, I’m assuming most queries will be using the sample data from the tutorial listed above, but my one criticism of the data from that tutorial is that it is not typical system telemetry. I’ll give examples for the following when I find a good sample dataset to use.
-
Get values out of JSON columns.
-
Join against other records.
So, with some free holiday hours, I’ve found playing with Jekyll to be more fun than expected. I guess I shouldn’t be surprised.
I wanted to do one of two things: Either start competely from scratch with a bare-bones GitHub Pages blog repo, or fork from Barry Clark’s jekyll-now repo. I tried both.
With the bare-bones repo, with no prior knowledge of Jekyll at all, it was very straightforward how to get a page to be served, but not how to create a blog of many files, all in a time series.
While the forked repo strategy was extremely simple to get started, I did not find it to be tinker-friendly without any knowledge of Jekyll. I can’t keep away from tinkering at least a little bit with a theme.
Eventually, it became apparent to me I should just learn what Jekyll is doing, and it turns out there is a wonderful Step by Step tutorial on the Jekyll site. There are ten steps, but they are pretty simple, and they each explain the logic of the components of Jekyll. I followed the tutorial on Windows, and pretty much ended up with a complete (albeit unstyled) site, running locally. Grab some existing CSS from a few blogs, and a tiny bit of tinkering later I have something a little closer to what I want.
In spare moments I’ve been looking for a quick blogging solution, and now I have one.
GitHub Pages is a wonderful free resource for all users of GitHub, both free and paid. Plus, it’s extremely easy to get started with it. You can start from scratch, or fork a repo to get a headstart.
- Get a GitHub account, if you don’t already have one.
- Fork Barry Clark’s jekyll-now repo.
- Rename your fork’s repository to
<yourgithubname>.github.io.
- Done!
What you end up with is a static site. This basically means there is no database needed to run things. GitHub provides Jekyll (the code that generates the static pages) as a service. All of my content are Markdown text files, which are versioned with Git.
If you are interested in the same, please check out Barry Clark’s extremely helpful repo and explanations:
What’s next?
- Private repo: I don’t believe you can take a forked repo private, so may do a tiny amount of work to make this blog’s repo private. (Note, I believe GitHub Pages is only supported in private repos wih paid GitHub accounts.) I may prefer the repo to remain public.
- Style: I’d like to style things a little. I’ve already added an excerpt separator to the site’s
_config.yml, but I haven’t bothered to look at themes.
- Custom domain: I am using a custom domain for this site. Getting this to work was mostly simple, but I had more hiccups than I expected.
- Run Jekyll locally: I need to run the site locally.
- Drafts: I need a drafts strategy, which is probably this.
What’s long-term?