2020 Portfolio Review

Last year my main brokerage account had a total return of 8.97% (6.75% capital gain, 2.22% income). As usual I will compare to VOO, Vanguard's S&P 500 ETF, which returned 17.98% (16.19% capital gain, 1.79% income).  So I lagged the market by 9.01% which is a substantial amount especially considering that almost half of my portfolio was invested in VOO.

The main reason for my underperformance was that the steady dividend paying stocks that I prefer were out of favor (at least in a relative sense) last year.  At the beginning of the year I had 29.45% of my portfolio in individual stocks and 11.49% in ETFs (other than VOO).  The individual stocks returned 2.49% (-.53% capital gain, 3.02% income) accounting for 4.56% of under performance and the ETFs returned -6.15% (-9.49% capital gain, 3.34% income) accounting for another 2.77% of underperformance.  

A secondary reason for my underperformance was that I was not fully invested.  I started the year with 12.23% in cash (the remaining 46.83% was in VOO). During the year I invested 1.75% of this cash.  The remaining 10.49% in cash only returned about .51% in interest accounting for 1.83% of underperformance.

On March 18 I bought Fortis (FTS) a Canadian utility and added to VPU, Vanguard's utility ETF.  This was good timing as the market bottom (with respect to VOO) was on March 23.  However I would have done better buying VOO which returned about 60% from March 18 as opposed to about 33% for FTS and about 19% for VPU.  Still because of the good timing this portion of my portfolio outperformed by .16%.  This all adds up to 9% of underperformance in reasonable agreement with the actual 9.01%.

Only 2 of my individual stocks (BLK and TGT) beat the market by more than 10%.  Another 4 (BBL, CAT, NSC and UNH) were within 10% of the market return.  The remaining 15 (ALL, BNS, CM, ED, CVS, XOM, INTC, IBM, JPM, MET, PEG, SOUHY, TD, WFC and WBK) trailed by more than 10%. And all of my ETFs (except VOO) trailed VOO over the whole year by more than 10%.

When I started doing these reviews I only had one brokerage account which was funded with the IBM stock I had acquired over many years through their employee stock purchase program and which my new employer required me to mostly sell. I also owned some stock received by gift or inheritance in certificate or book entry form. Starting in 2018 I moved some of this stock as well as some cash and my Value Line mutual fund into a second brokerage account. In 2020 this motley collection returned 13.07%.     

Try, Try Again

As I have mentioned a couple of times, in 2010 I bought a cheap Dell Inspiron laptop computer. It has held up pretty well with a lot of use. However a couple of years ago it developed an annoying issue. The automatic Windows 10 update process started to fail repeatedly with an obscure error message about data corruption. I tried various purported remedies that I found with internet searches but none of them fixed the problem. I had basically given up and was resigned to living with an increasingly obsolete operating system (like with my still older Dell Inspiron desktop running Windows Vista).  However to my surprise on or about December 30, 2020 the update succeeded so the machine is now running the newest (20H2) version of Windows 10.

Upgrading to a new version of Windows 10 apparently wipes out the update history so I am unsure exactly when the problem started or how many failed attempts there were (it seemed like dozens at least). This wikipedia article has a table showing the Windows 10 version history. Based on this my best guess is that my machine was previously running Version 1803 of Windows 10 which was released April 30, 2018. The next version 1809 was released November 13, 2018 but apparently didn't get installed on my machine. The end of support for 1803 was November 12, 2019 leading to nagging messages from the Windows's updater about moving to a supported version of the operating system. However as noted above repeated attempts to do so always failed with an obscure error message. Whatever the problem was persisted through versions 1809, 1903, 1909 and 2004 as they became available. But it seems to have gone away with version 20H2 which first became available October 20, 2020.  New versions aren't installed immediately on all machines (my other laptop is still on 2004) but apparently installation was attempted on December 30 and succeeded.

So far (with limited use) I haven't encountered any problems with 20H2 so hopefully there was no actual data corruption issue and Microsoft just had some bug in their update process that went away when 20H2 was released. This problem wasn't the biggest deal in the world as I could still use the machine (which was gradually becoming functionally obsolete anyway) but it is still a rather sobering example of how hard it can be for the average person to effectively deal with this sort of obscure computer issue.  

Blog List Update

 Kevin Drum has left Mother Jones and is now blogging at his own site so I have updated my blog list link appropriately. I could never get the previous link to work correctly, it would go to the top Mother Jones page rather than Drum's blog specifically. Fortunately this is not an issue at his new site. The link to Steve Sailer's blog had the same problem, going to a general Unz Review page. I tried again to fix this with partial success, now the link to Sailer's most recent post works correctly but not the link to the entire blog. 

I also added the lefty "Lawyers, Guns & Money" blog to my list. I wouldn't say the analysis is generally very impressive but it does provide a view into what a segment of the left is currently thinking about politics. Also they have several active posters so they do generate a lot of content.