Skip to main content

Single computing device lifestyle

For as long as I can remember, I've used multiple computers. I would have a desktop PC at work and both a desktop and laptop (or 2) at home. I think the main reason for this multi-system lifestyle stemmed from my fondness of using Linux and wanting to try different Linux distributions. I could move between systems with relative ease and pickup working on one device where I finished on another. This has worked well for me in the past, but recently it's become more and more like hard work.

In the good/bad old days, web development was relatively simple and all you really needed was a good text editor. These days, things are a little more complicated and it takes time to install and maintain the tool chains that some modern web development techniques require. And having to manage these tool chains and build systems across multiple devices can be both time consuming and a pain in the arse.

Recently, I've decided to simplify my life and start using a single computer device. So, I ditched my desktop machines in favour of using my laptop, a Lenovo T470s. This lasted for precisely 1 week. The T470s, whilst being a lovely laptop, was beginning to show its age. It was usable, but moving from a 10th gen Intel desktop with a dedicated GPU to a 7th gen laptop, the difference in speed was noticeable -- even more so when hooked up to 2 external 1440p monitors.

To rectify this issue, I ordered myself a new laptop, a Lenovo T14s Gen 3. I've been using the T14s as my sole device for a couple of weeks now and I'm super happy with it. It's currently running Debian Bookworm and everything just works -- USB, Thunderbolt, Bluetooth, web cam, microphone, fingerprint reader, everything. TBH, it's probably the best laptop I've ever owned and it's a joy to use. But this post is not really about my new laptop, it's about the advantages of using a single computing device, and not spreading myself too thin over too many devices.

As mentioned early, the main advantage I have experienced is the amount of time I'm now saving by not having to maintain multiple tool chains and build systems across multiple devices. I simply take myself off to work in the morning with my laptop, hot-plug my monitors, keyboard and mouse into it and start work. At the end of the working day, I take myself home with my laptop, and if I want to continue working, I just open it up and start working. I don't have to concern myself with configuring any tools I might have set-up during the day, or even pulling down any Git repositories. Everything is just there, ready and waiting.

Anyone who has been using a single computing device for a while may be thinking, 'well duh!' But for someone like myself who has always used multiple devices, the experience so far has left me feeling somewhat liberated.

The only real negative that I can think of at the moment is that I now need to be more diligent about performing backups. Using multiple devices lends itself nicely to automatically creating backups as a byproduct. I've added an item on my todo list to perform a weekly backup. I'm thinking of using my old T470s as backup device, but it will be installed somewhere out of sight and out of mind as I don't want to accidentally slip back into using more than one device.

View as: JSON Markdown

If you enjoyed this post or found it useful, you can subscribe to my RSS feed.

Similar posts

  1. How to set-up WatchGuard VPN with IKEv2 under Debian and Fedora

    A blog post detailing how to set-up WatchGuard VPN with IKEv2 under both Debian and Fedora Linux. This guide works for me under Debian 12 (bookworm) and Fedora 40/41, but your mileage may vary depending on how your VPN service is configured.

    debian vpn watchguard ikev2 fedora ipsec
  2. My Debian 12 (bookworm) server set-up

    I've been running Debian on my servers for years. It's dependable. I guess my server set-up is pretty common, consisting of Apache, PHP and MariaDB, but I figure it is still worth sharing details of how I provision my servers.

    php composer mariadb apache debian linux node fish
  3. My Debian 12 (bookworm) desktop set-up

    Creating a good Debian desktop experience is not too difficult, thanks to the excellent work of the Debian developers, but I thought it might be interesting to share how I set-up my Debian systems.

    debian linux
  4. Calling Puppeteer via PHP

    A blog post detailing an issue where a Puppeteer screenshot script, triggered through a PHP application using CodeIgniter, stopped working due to Chromium not starting under the Apache www-data user on Debian.

    php javascript node debian apache
  5. Switching desktop Linux from Debian to Fedora

    Last week I switched the operating system on my daily driver (Lenovo ThinkPad T14s) from Debian 12 to Fedora 40. In this post I write a little about why I switched and how the switch went.

    debian linux fedora
  6. Firefox Nightly as a daily driver

    I believe that it's really important to support and use Firefox. Not only do I think that Mozilla understand/support user's privacy more than Google, but I also think it's important for the health of the web that more than one option exists when it comes to rendering engines. Also, it's a really good web browser.

    debian chrome firefox mozilla
  7. Redux

    As a web developer, I like to build and rebuild websites. My own website is no different.

    markdown fediverse mastodon codeigniter php bootstrap jquery debian
  8. How to create Bash aliases in Fedora

    Creating your own Bash aliases is a relatively easy process. That said, I recently switched my desktop linux distribution from Debian to Fedora and there are subtle differences.

    linux fedora debian bash