Month: July 2017

Fedora 26 Update

Fedora 26 has been release about a month and a half ago.  But I didn’t have the time to update my laptop until today.  There was also nothing particularly exciting for me in this release, so there was no rush.

Here’s what I had to do today to update my laptop from Fedora 25 to Fedora 26:

# Let's get into root to save a few keystrokes
sudo su -
# Install all updates for Fedora 25
dnf update
# Install dnf system upgrade plugin
dnf install dnf-plugin-system-upgrade
# Download upgrade packages for Fedora 26
dnf system-upgrade download --refresh --releasever=26
# Reboot and install Fedora 26
dnf system-upgrade reboot

If you need more help, have a look at DNF system upgrade wiki page.

The whole process took less an hour, but your mileage may vary.  For me, the download itself was the slowest part.  I had to pull down about 2.5 GBytes worth of packages, and given my office connection, it took about 35-40 minutes.

The installation itself took about 10-15 minutes, for which, I think, the solid-state disk (SSD) helped a lot.

One more reboot later, everything was up and running.  Of all the changes pushed into this version, I think, the upgrade to PHP 7.1 is the one that affects me the most.

Fire and Motion

Joel Spolsky wrote “Fire and Motion” blog post back in 2002, but it is as relevant today as it was 15 years ago. It’s a good read on the subject of both personal and organizational productivity.

What drives me crazy is that ever since my first job I’ve realized that as a developer, I usually average about two or three hours a day of productive coding. When I had a summer internship at Microsoft, a fellow intern told me he was actually only going into work from 12 to 5 every day. Five hours, minus lunch, and his team loved him because he still managed to get a lot more done than average. I’ve found the same thing to be true. I feel a little bit guilty when I see how hard everybody else seems to be working, and I get about two or three quality hours in a day, and still I’ve always been one of the most productive members of the team. That’s probably why when Peopleware and XP insist on eliminating overtime and working strictly 40 hour weeks, they do so secure in the knowledge that this won’t reduce a team’s output.