Category: JavaScript

  • Body Beast Bulk – 1.1.2020 – 4.4.2020

    Introduction

    I did another round of Body Beast, Bulk version. It’s a body building routine that lasts about 3 months. I did the Lean version last year before my 40th birthday. This year, I wanted to see how lean I can get. I also found out from last year I had lost 9 lbs from simply not eating as much (basically skipping breakfast) and doing a little cardio for fun. Sadly my measurements showed that I had about the same amount of body fat, meaning a lot of my weight was muscle. Still, clothes did feel better and doing cardio things for fun was easier too.

    (more…)
  • Write Unbreakable Python

    Write Unbreakable Python

    In this article, I’ll show you how to write Python with no runtime exceptions. This’ll get you partway to writing code that never breaks and mostly does what it’s supposed to do. We’ll do this by learning how to apply functional programming to Python. We’ll cover:

    • ensure functions always work by learning Pure Functions
    • avoid runtime errors by return Maybes
    • avoid runtime errors in deeply nested data using Lenses
    • avoid runtime errors by return Results
    • creating pure programs from pure functions by Pipeline Programming
    (more…)
  • React Redux Thunk vs Elm

    React Redux Thunk vs Elm

    Introduction

    It’s a bit easier to learn Elm if you compare it to things you know. If you know React and Redux, then comparing them can help a lot to understand Elm concepts. I’ve built the same application in React Redux Thunk and Elm so we can compare them together. The end result is a table of things you can paginate through. Comparing these 2 applications is apples to apples. They’re identical to the end user. Yet the technologies behind them are apples to oranges. Seeing those deviations using familiar tech in the same application can help your understanding.

    (more…)
  • Maybe a Default Good Idea

    Maybe a Default Good Idea

    Introduction

    You’ve learned that using Maybe‘s allows you to get rid of null pointer exceptions (i.e. “undefined is not a function”). However, now your application fails and gives no indication as to why. At least errors would leave a stack trace that may provide a hint as to where the problem originated. How does this happen and what should you be doing instead?

    (more…)