My Goals for 2022

It’s that time of year. It’s time to look back on 2021 and consider how I did against my goals. And, of course, time to set new goals for the new year. 

Life never returned to normal in 2021. In some ways, it was just a continuation of 2020, the year of the pandemic. I spent the year working from home, which has become the new normal. I traveled to New York City twice, but it was for work. It’s not something I’m excited about doing again. The city was full of fearful zombies that wore masks outdoors and took them off in bars and restaurants.

Working from home has many advantages, though. For example, I only had to fuel up my car four times last year, as I no longer use my car for commuting. Thus, I’ve been thinking of selling it. I’ve also been very healthy throughout the year. The vaccine keeps the effects of covid away, and avoiding people, in general, keeps the colds away. So that’s been nice.

The stock market had a great year. Even bitcoin had a good year, rallying to new all-time highs before falling back to $47,000. But that’s still a huge increase over the $29,000 it was at the start of the year. So I really have to wonder if the gains can continue yet another year in 2022.

Last year I set 10 personal goals. Here’s how I did on each of them.

✅ Write 4 longer short stories. I achieved this by mid-year and tried to finish a fifth one. Strangely, I still haven’t finished the fifth one, and now I’m facing the choice of wrapping it up or extending it into a novel.

❌ Complete six short online courses and two longer online courses. Early in the year, this was going well, and I finished five short courses. As I got involved in other priorities at work and home, I spent less time on self-education. This was unfortunate, as I truly wanted to learn more about blockchain and crypto technologies. 

❌ Make new friends. I didn’t have a plan for this. Thus, it’s not surprising I didn’t make new friends. Staying home all the time, I’m not meeting anyone outside. And the relationships I’ve made with people online I would not elevate to the level of “friend.”

✅ Catch up on periodicals. I almost didn’t make it. I finally caught up on December 30th. As this won’t be a goal in the future, and I’ll significantly reduce the number of periodicals I subscribe to, I should have time to work on other things.

✅ Read 25 books. This goal is another one I barely achieved, finishing the 25th book at the end of December.

✅ Maintain my exercise habit, a healthy diet, and lose more weight. I succeed at this. I didn’t lose much weight, but I did lose some. Also, I stayed healthy throughout the year. Thanks to the pandemic, I attribute much of me staying healthy to working from home and avoiding people.

✅ Gain 15% on my portfolio. It was another great year for investing. Both the stock market and cryptocurrencies did very well. So well, in fact, that I fear 2022 may be a down year.

❌ Sell, donate, or dispose of three shelves’ worth of old stuff. It was too easy to leave things on the shelves. As a result, I didn’t achieve my goal of reducing clutter.

❌ Take two vacation trips. Thanks to the never-ending pandemic, I never thought seriously about taking trips or cruises. Even with the vaccines and boosters, it just doesn’t seem appealing. I thought I might take a road trip somewhere, but that didn’t happen either. Ultimately, I took vacation days here and there to relax at home.

✅ Achieve gainful employment. I landed an excellent job in February, and I’ve been there ever since. It was the ideal outcome. I work on an interesting, award-winning application. I also enjoy my coworkers; they’re great. And finally, I’m getting the experience of managing a globally distributed remote team.

So those were my 10 personal goals for 2021. I succeeded on 60% of them, typical of the past few years. Maybe one was partially successful, but that would only make it 65%. I want to do better. This exercise is about more than just hitting the goals, though. It’s about having goals, and watching them throughout the year. If you don’t set objectives, you’re not going to get there.

For 2022, I have a new set of goals.

Complete three home improvement projects. I have some specific projects in mind. I’ve been putting them off, so I aim to get them done this year.

Get back to taking vacations. It’s been two years without one, so, one way or another, I need to find a way to resume taking vacations.

Close unused accounts. Over time I’ve accumulated credit cards and things I don’t use anymore. I want to get rid of these things.

Simplify life. There are some things I can do without. For example, I can sell the car I rarely use anymore and get rid of some of the clutter around the house. It also includes automating more bill payments, saving some tedious work.

Improve bookkeeping. With the various crypto transactions I have and other investments, I need to improve my records.

Reduce expenses. I have some specific items in mind here to reduce some of my monthly expenditures.

Gain 15% on my portfolio. This one is very straightforward, although it may be a challenge. After several great years, the stock market may not perform as well this year. In addition, rising interest rates may impact stock valuations. However, inflation may benefit some investments.

Consolidate accounts. I should transfer and consolidate some accounts that have little activity.

Medical goals. This includes various vaccination goals. It also means achieving a weight target through a combination of watching my diet and continuing to exercise. 

Continue education. I have a series of courses I intend to take. I also want to practice some technical skills through a set of small projects. Finally, I plan on creating a crypto project and some NFTs.

Make new friends. My plan this year is to leverage half a dozen systems to create an equal number of strategies to make new friends. The goal is to make three new friends by the end of the year.

Improve writing skills and make stories. This goal has several components, the first of which is reading 25 books. I also want to edit several of the short stories I’ve written in the past year and get one published. Another goal is to write a short nonfiction book and outline a novel. Actually, there are several sub-goals under this goal, and it will be challenging to do them all.

All told, that’s 12 major goals for the year, most of them with several sub-goals. However, I’ve already made some progress on them, so the year is starting well. Again, these are my personal goals; I have not included my work-related goals here.

Don’t run with scissors.

Exercise extreme caution when removing data.

One must be very careful when deleting data. It’s far too easy to delete the wrong data by mistake. This kind of error can lead to extensive system downtimes and upset clients.

Before removing any data, query the data set to be deleted and examine it closely. Sometimes this simple action can reveal data elements that you should not remove. For more massive data sets, sample the data multiple times. Also, one can summarize the data to be deleted and look at counts and totals.

Also, make sure you have backups. It can be extremely unfortunate to delete the wrong data accidentally and then learn, too late, that your backups are not functioning correctly.

Even highly experienced people make mistakes. Don’t get cocky!

Some bugs are caused by bad assumptions.

These assumptions can cause widespread problems.

When you fix a bug that was based on a bad assumption, look for other areas of the code where those bad assumptions where used. Chances are good that there are additional bugs caused by the assumptions, bugs you haven’t found yet.

You may find many other bugs that have gone unnoticed as a result.

Always question your assumptions. It’s very easy to get the assumptions wrong, as they are often communicated to you through several people, each of which may accidentally alter it slightly.

Make you sure you document your assumptions in a shared knowledge base. An internal wiki like Confluence or other similar products is good for this.

Find the first error.

A large series of errors is usually triggered by a single error.

When problems occur and you have a long stream of errors, try to find the first error. Most of the time, everything after that is a side effect. Like a chain of dominoes, the first error causes all the others to occur.

Sometimes that first error is hidden, or lost in other noise in the log. It’s not always obvious, but definitely dig for it.

Try to solve the root cause instead of treating the side effects.

Write a test for every fault you find.

It’s a simple way to avoid repeating mistakes.

You get this for free if you follow the highly recommended practice of test-driven development.

If your code base doesn’t have that kind of coverage, always be sure that there is a test to cover fault, bug, mistake, error and unexpected result that you encounter.

There’s nothing worse than having bugs come back later. When you repeat the same mistake twice, did you learn nothing the first time? Avoid this.

Don’t count on others to test.

Do your job and be responsible.

Test everything you write and review. All of the code you work on, whether you are the primary developer, the pairing partner, or the code reviewer, you need to test. Be responsible for all the code you are participate in.

It’s extremely bad behavior to depend on others to test. This usually results in certain parts of the code not being tested, and bugs introduced into the production code base. And then you’re no longer delivering working software. And if your’e not going to deliver working software, then why are you here?

It’s your job to ensure the quality of your code. Own it.

Testing can find bugs, but it can’t prove the absence of bugs.

It can certainly find bugs, but it is not proof that all is well.

Getting all green lights on a test suite does not necessarily mean that everything is okay. It is quite possible for bugs to still exist in a system, even when the code coverage is quite extensive.

Still, it is worth trying to cover all the known cases. More coverage and test cases is better than less.

You just have to remain vigilant. Don’t put all your faith in the testing machine.

Never ignore an error.

You can’t simply pretend it didn’t happen.

Silent failures will screw you over. They will lead to corrupt data in the system, and it will be incredibly hard to track down the source of the corruption. It can also lead to huge financial losses as well.

If you can’t handle the error, signal the failure up to the calling method. The buck has to stop somewhere. Pretending things will be okay is a major rookie mistake.

Comments should discuss the current functionality.

Don’t let your comments ramble on about the past or future.

Don’t have comments describing what a function used to do. That information is in the version control. Instead, the comments should only discuss why the current functionality is the way it is.

Similarly, don’t speculate on the future. You don’t know what the future business requirements will be. (cf. YAGNI)

When you update your code, update the comments as well. Don’t turn the comments into lies.

Don’t use comments as version control.

Instead, use version control software, like git.

Some developers leave blocks of commented-out code. Maybe that’s the previous version of the code, or maybe it’s the future version. In worse cases, multiple versions are commented out. This confuses the reader greatly.

Blocks of commented-out code are confusing, misleading, and trouble. Someone will uncomment the code and reintroduce it at the wrong time. It will lead to bugs and faults.

If you don’t need code anymore, delete it. Deleted code has fewer bugs.

And if you really need to look back at prior versions, they are available in the git history.