Skip to main content

Three things I learnt from Animal Crossing

Like many people during lockdown, I ordered a copy of Animal Crossing New Horizons. I also want to escape my real life chores by ... performing daily chores in cuter format?

Several months later, I'm no longer playing daily, but each time I do return my experience is a calm, joyful one. Here are the three things I learnt from the game:

1. Don't compare yourself to others. Yes some people have the most gorgeous islands. Some people also have far more free time. Some are more talented. Copy ideas you like, because why not? It's just for you and your friends to enjoy.

2. There's such joy in creativity - try out a little bit, don't jump in attempting to make everything exactly how you planned it from day 1. Perfectionism is the enemy of creativity.

3. If you're playing a game and feel stress more than enjoyment - it's time to take a break. Remember it's only a game, rotten turnips have no negative impact on your real life. This game in particular rewards daily play, or even multiple times per day play, which can be a lot to fit into your lifestyle. I got overwhelmed trying to essentially max out the game - earn all the money on the stalk market, be best friends with all my villagers, have all the furniture and clothes, catch all the possible fish and bugs. When I noticed I was feeling stressed about how to fit the max playtime into my available daily hours I knew I needed a break.

Now I return to this game to play with friends which is the most rewarding for me. If you do play it, hope it brings you joy too!

Comments

Post a Comment

Popular posts from this blog

Three things I learnt from The Pragmatic Programmer - Chapter 2

  Chapter 1 link here I'm currently reading  a book called  The Pragmatic Programmer  by David Thomas and Andrew Hunt. The first chapter is an easy read, all common sense. The second chapter starts introducing code and is a little more technical. Here are three things I learnt from the second chapter: 1. Every design principle is there to make your code easier to change (ETC). If you're not sure what code design principles to follow and when, use ETC as a guide. 2. Eliminate effects between unrelated things. (Increase orthogonality - parts of code that don't rely on each other). Keep code decoupled, avoid global variables, avoid similar functions, be careful of third part toolkits. 3. Get good at estimating. Every time you have a task, estimate how long it will take. Think about each little step in the task before you provide an answer. When you finish the task write down how long it took, and if you can, why your estimate was wrong. You'll learn to spot patterns....
2 comments
Read more

Three things I learnt from The Pragmatic Programmer - Chapters 5 and 6

Link to previous chapter here. Here are the three things I learnt from these chapters: 1. I'm at the start of my journey and it's totally okay not to understand everything. I do not have to force myself to read things that make no sense to me yet. At some point I'd love to come back to this book and see what I can learn here as I'm sure its good.  2. Elixr, a functional language, has a pipeline operator that takes the value on its left and insert it as the first parameter of the function on the right. It's a more readable way of transforming data. Thinking of code as a series of nested transformations helps make functions shorter. 3. Be careful with inheritance. It can get messy if not all of a parent's methods are suitable for the child, or if the parent's code will ever be edited. Try things like traits/mixins/delegation/interfaces instead.
Post a Comment
Read more