The White iPhone 16

I just wanted to write a quick appreciation post for the white iPhone 16. It's a great size, it's super light, it feels great to hold, and it just looks god damn beautiful.

I had imagined there would be at least somewhat of a regret about going from a 15 Pro Max to "just" an iPhone 16. However, I can confirm that this is not the case. I do not regret this decision at all.

As an aside, I have this in the yellow (Star Fruit) silicone case most of the time, and it still looks great. But I do have to pop it out every now and then, because it is such a good looking phone.

Off to China

In just a few weeks time, I'll be heading off on on a work trip to China. It will be the first time I've ever been to Asia, and also the first time I've left my partner and my 3-month old child since she was born (apart from going to work), and I'll be away for around 10 days. It's going to be a very new experience for me on many fronts.

One benefit of it being a work trip, is that it's 100% company funded, and I get to travel around multiple locations in China. Two of them being Hangzhou and Shanghai, where my work has big offices, so I get to meet up with some colleagues that I haven't met in person, even after working together for many years. And the other being Guilin, where we are spending the weekend. We will be going to visit some incredible pillar-shaped mountains, which is where I've read, James Cameron filmed some of Avatar.

I'm going to try and focus on seeing colleagues, travelling to new places, and having new experiences. But I think the only thing stopping me from being attached to FaceTime for the trip will be my data allowance. (That's one thing I haven't sorted out yet.)

The only tricky part of the planning so far has been the Visa application, since I require a visa suitable for business trips. Turns out, as a British citizen/passport holder, and a first-time applier, I'm likely to only get a 2 year multi-entry visa. But that's fine. I'm hoping it also means I can try and get another (probably smaller) trip again in the future.

There's so many things I'm thinking about, because it's such a unique trip for me, and one I definitely want to make the most out of.

For example:

  • Do I take a real camera? Do I need to get something new and minimal that I can carry everywhere to stop my phone going flat?
  • How many clothes do I need to take? And what sort of bag can I carry it in?
  • Will I have time to do anything apart from working, eating, and socialising with colleagues?
  • What devices do I take? I have to take my Work Mac, but what about my personal Mac, iPad, etc?
  • How the hell can I cope with a 12-hour flight?

I Finally Have a Use for the Action Button

Last year I purchased an iPhone 15 Max, and for the first time, I was presented with a new customisable button on the side of my phone. For an entire year I struggled to find a purpose for it.

Do I keep it as a mute switch? I didn't really ever use the previous mute switch. Do I make it launch a fancy Shortcut? Maybe that could have been clever, but I've stopped using Shortcuts. Or how about I make it a launcher for something like the camera app? Well that sounded good, but it doesn't work on press, you need to hold it down, so it always felt slower than swiping left on the lock screen.

Well, I've now got an iPhone 16[1], and because of the new "Camera Control" button on the side of the device, I now have a way to launch (and control) the camera pretty quickly. So that removed one option in my head.

And then it came into my head, it should be to toggle the torch. I have a baby now, so I don't always want to turn the main lights on, so sometimes easier to just switch the torch on quickly.

Maybe that's a sign that sometimes too much customisability isn't always the easiest to deal with. Or maybe it's just me. Either way, it literally took me a year to find a use for the Action Button.


  1. Not Plus, not Pro, not Max, just 16. ↩︎

Maybe I’m Not a Pro Anymore →

Brendon Bigly, writing for MacStories:

Apple just wrapped up their September event revealing a bunch of updates to the Apple Watch, AirPods, and iPhone lineups, and I have only one major takeaway as a person who was absolutely, positively going to get the iPhone 16 Pro if it came in gold: I am seriously considering downgrading to the non-Pro iPhone 16 this time around.

A rather interesting take on what Pro means for the iPhone 16. I'm also having similar thoughts about whether I actually need the Pro model or not. My current device is the 15 Pro Max, and while I have my head set on moving back to the normal-sized iPhone, I am torn between 16 or 16 Pro.

I can live without the camera differences. But I don't know if I can live without ProMotion. Primarily because I didn't instantly notice the difference when I first got a device that supported it, so will I notice it when it's gone?

I’m Probably Going To Buy an iPhone 16

I've been pondering a switch to Android for a while now, and I've been especially tempted by various Nothing phone models. However, I have come to the realisation that I will likely be again purchasing the next iPhone.

There's many small reasons, but I think for this year I just want stability. I'm a recent father, and I don't have time to faff around with my devices as much anymore. It's also partly down to my partner also having an iPhone, so everything is just a bit easier if we're on the same ecosystem.

I haven't been keeping up to date with rumours, so I don't know exactly what model I'll be choosing. But I'm 90% sure I'll be going back to the "normal" size. There's a chance that I'll go to the base 16 model, as there could be a nice colour that tempts me. But I'm sure there will be some kind of camera appeal that keeps me on the Pro lineup.

Maybe I'll switch to Android in the future. But for now, I don't want to think about technology. For at least another year, I want it to just work.

My Digital Life After Having a Baby

If you didn't already know, little over a month ago I became a father for the first time.

It's incredible. And it's forever changed my life in more ways than I could ever have imagined. Especially regarding technology.

I was starting to think that I wasn't actually interested in any of it anymore. Because I started to just not have the urge to do anything, no reading blogs, no writing anything, no programming, nothing.

It was weird, since I don't feel that having a child has added that much stress to my life, and it's not like I'm so busy i have absolutely no free time anymore.

After some thinking, I realised that it's not that I'm not interesting it doing any of those things. I want to write on my blog, I want to keep up with other blogs, and I definitely want to keep programming in my spare time. Among a whole bunch of things I used to do day-to-day on my devices.

The problem is that I now need to optimise the technology I use, and the choices that I make, around a new reality. I don't have no time to do anything, I just have a little less time than before, which makes some tasks more cumbersome.

It adds a new level of friction that I wasn't used to before.

The biggest example is my phone. I currently use an iPhone 15 Pro Max. It's a great phone for watching videos, playing games, and for scrolling through social media. But if you've got a baby in one arm, it's near impossible to anything else one-handed.

The same also applies to my iPad to a lesser extent. I have the 12.9" iPad, so that's also not a one-hand device.

And as for my "real" computers, in my MacBook and gaming PC, these don't just require two hands. They require time. I'm not spending 60 seconds on my Mac writing a post for social media, I'm working on a project, going through my emails, writing a blog post, playing World of Warcraft, etc.

What I'm thinking now, is that instead of just letting my hobbies and digital life fade away, I should just adapt to my new situation.

The two device changes I think I will make in the close future will be to buy a smaller phone that I can use one-handed and do all the usual phone-stuff with. And also to buy a smaller iPad. I don't know if that means iPad Mini or the "normal" iPad. But if I'm already feeling friction with the big iPad, the desire for an "in-between" device will certainly grow. Especially as there will no doubt be things that I enjoy doing on a big phone that I won't be able to do anymore.

As for more decision changes, I'm sure a lot of it will be down to adapting my habits, but I think I also need to be more purposeful of the time I spend on my computers.

In a weird way, I think it will fun optimising my for new life.

Using Stow to Make Managing Your Dotfiles Easier

As someone who regularly switches between various macOS and Linux machines, keeping my dotfiles synced everywhere gets a bit annoying. Fortunately, I've recently come across a tool called Stow from GNU, which helps you manage your dotfiles.

Stow, combined with a git repository, makes managing and syncing dotfiles between devices much, much easier.

To install Stow, you'll likely find it in your package manager under "stow". For example, for macOS running Homebrew, you'd literally just need to run brew install stow.


As for using Stow, it's probably useful to first know how it works. That way you'll have a better picture of how it ties everything together.

Let's take this scenario - you have your Neovim configuration saved under ~/.config/nvim like normal.

If you want to synchronise this between devices, then maybe you could just turn that directory into a git repository itself.

But if you have a bunch of configs for tools, some in .config, others inside your home directory, and some just plain config files mixed in there, it can get a bit messy.

That's where Stow comes in. You can have a central place where you store all your configurations for various tools. And then you can then choose to "stow" (load into the relevant directory) the configuration for whichever tool you want.

This means you can have one git repository, with a collection of individually defined packages, which then can be synchronised to various devices. And then on each of these devices, you can choose a subset of these packages to use.

Let's go back to a real world scenario again. Let's say this is your home directory:

.
├── .config/
│   ├── nvim/
│   │   ├── init.lua
│   │   └── lua/
│   │       └── stuff.lua
│   └── tmux/
│       └── tmux.conf
└── .zshrc

You can see there are three different things being configured, Neovim, tmux, and zsh. With Stow, you could have these as three differently defined packages.

Each package in stow, is defined by it being a directory with its name being the package name. Inside the directory would be the folder structure as if it were in the home directory.

This would mean, the above configuration inside a central dotfiles directory, would look like this:

.
├── nvim/
│   └── .config/
│       └── nvim/
│           ├── init.lua
│           └── lua/
│               └── stuff.lua
├── tmux/
│   └── .config/
│       └── tmux/
│           └── tmux.conf
└── zsh/
    └── .zshrc

With that dotfile directory, to configure all of these packages in the local machine, you would just need to run this command in the directory:

stow nvim tmux zsh

That command would then load all of the packages, by creating a symbolic link from all the relevant files and folders into the correct place.

To get an example, here is a screenshot showing my .config directory with all the symbolic links, and my .dotfile directory.

Just as a tip, the default behaviour of the stow [package] command, is that it works when you are in a directory that is one level below your home directory.

You can read the full capabilities of the stow command via the man page, or via the documentation. However, if you want a simpler life, you can just do what I do, and create a directory for your dotfiles like this: ~/.dotfiles/.


Once you start building up your collection of config packages, and tracking the directory via git, it becomes really easy to move between machines.

All you would need to do is to pull the git repository, and then use stow to load whichever packages you wanted to load on that particular machine.

You could even have slightly different versions of a given configuration, and then load a specific version based on the machine you were on. Maybe you have something that fits your use case at work or home, or even a different platform such as Mac or Linux.

Once you start using it, it doesn't take long until you start to feel the benefits.

A Father

6 days ago, on the 4th of July, the best thing happened to me.

I became a father.

hello

Some Recent Bash Scripting Fun

I've been writing more and more bash scripts recently (GitHub repo). It started when I was playing around with a script called tmux-sessionizer from The Primeagen, that uses fzf to search for directories in a preset location, and then open the selected directory in a tmux session.

The first three I came up with were all mainly some sort of selector-style tools powered by fzf:

(they may seem like odd names, but I wanted to be able to use these scripts really quickly)

  • tg (right-top)- a customed version of tmux-sessionizer that lets you quickly fuzzy find a directory and then attach/reattach to a tmux session with it.
  • ala (left)- fuzzy finder for alacritty (my terminal choice) themes, which is then applied on selection.
  • fd (right-bottom) - fuzzy finder that searches the current directory for any subdirectories with a max depth of 3. And then changes into the selected directory.

I also made another one that replaces my existing alias for quickly committing and pushing my local changes with Git, and makes the flow a bit more interactive.

Previously I had an alias gacp, which basically meant (to me) "git add commit push", and did the following:

git add --all
git commit -m "$input"
git push

And I'd use it like this:

gacp "my wonderful code change"

But now with my (aptly) named tool, gt, I just need to type those two letters, and it then lets me quickly run through the process of pushing my latest changes.

First of all, it asks if I want to stage all my current changes (defaults to yes), then it asks what type of commit it is (using conventional commit style), asks for a commit message, and then if I want to push to my remote repo.

So a pretty simple process, but just a bit faster thanks to this little script.

As you can see, I'm clearly having a bit of fun writing these scripts, so don't be surprised when I start uploading even more.

Although my next script/tool will definitely have to be making blog posts easier to start writing. I have a half-baked bash script that creates a basic template, but I think I want to make one with a bit more power, that can be flexible for multiple types of posts. Let's see.