DEV Community

Cover image for 30-day Learning Challenge: Day 4— In and out of tech
Kervyn
Kervyn

Posted on

30-day Learning Challenge: Day 4— In and out of tech

Welcome back to the learning challenge that I’ve set out for myself, where I aim to document something new that I’ve learnt every single day for 30 days!

For today, I continued reading the nutrition-related book featured in Day 3’s article! The insights gleaned have been incredibly interesting, and are concepts that I have not come across before!

Learnings (Nutrition)

For instance, one of the concepts mentioned at the beginning of the book was explaining why humans, like you and I fail so consistently when it comes to following a diet. In a nutshell, according to the author, it relates to how we are biologically programmed to act and seek out food when we are starved, leading to us spiralling out of control of our diet the moment we eventually succumb to the deprivation of our “sinful”, favourite foods.

It has been an amazing read so far, and I can’t wait to continue with the book to see what else I can learn in the upcoming pages.

Transitioning to the software engineer in me, I learnt even more today about how to write higher quality and sustainable code.

Learnings (SWE)

From planning your architecture in advance, to understanding how to segment and compartmentalize large amounts of code into isolated containers/Lambdas (in AWS context), these are skills that will be continuously sharpened throughout my journey as a software engineer and I am no doubt excited to learn more!

A famous line I’ve heard from my previous tech leads, as well as from other senior software engineers, is that “if you fail to plan, you plan to fail”!

And I can’t tell you how much I agree with this.

Spending time to plan your code ahead of time, instead of straight deep-diving into writing code for your task/feature will save you immense of time down the line, as well as adjust your mindset to fit business requirements suited for that feature. Who knows, through this thought process and careful planning, you might even discover feature flaws/gaps in the requirements that you can highlight/discuss with your colleagues/peers!

As usual, do join me on this journey as well, and begin documenting your daily attempts at learning something new everyday. Trust me, you’ll shock yourself when you look back at how far you’ve come!

Do leave a comment down below or simply get in touch with me through my email if you wish to discuss about anything related to any of my previous articles!

Top comments (0)