What did I learn today?

  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....

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...

 Currently I'm reading a book called The Pragmatic Programmer by David Thomas and Andrew Hunt (20th Anniversary Edition). It's great to read at the start of my career as it shows me what I'm aiming for and why I need to keep learning.  The three things I've learnt from Chapter 1 are: My career is my own. I have the power to make it as personally satisfying and rewarding as I can.  Quality matters, keep on top of it as you go. This includes documentation, build it as you go along. It'll slow you down today, but speed you up next time you look at your code. Keep learning. Read about new technologies, developments and tools. Try things out. Knowledge can quickly become stale. Chapter 2 link here

Recently I read a book called  The Nature of Software Development  by   Ron Jeffries .   As a newbie developer, I had little knowledge of what it meant to be "agile" at work, and I assumed most coders weren't performing cartwheels in their lunch breaks. I was lucky, this book was simply written by a man with a vast amount of experience in the topic. I really enjoyed reading it, and found it surprisingly relatable, given I don't have industry experience. Here are the three main things I learnt from my read: 1.  Why do we need agile? In life, deadlines will never be met with a perfect product with everything you want. Ever. This is no fun for anyone. 2. So, what would happen if we ship a basic model of a product as soon as possible? Firstly, the product user will have something that they may like a little long before they expected it - yay for them. Secondly, they might have feedback on the product - perhaps it already does everything they need, so no more u...