Morning Code Sip

MCS 0024: 6 Impossible Things, Habit Stacking, Failures Should be Actionable

Today, I propose the 3 following articles to start your day.

6 Impossible Things

This great talk, by Kevlin Henney, dives into six specific impossible things that shape the limits of what we can develop, all the way from the smallest detail of integer representation to the minefield of task estimation and prioritisation, via the uncertainty of distributed systems and the limits of computability.
Once we know our limits, we can work within them to create solutions rather than problems.

Habit Stacking and Minimum Viable Progress

Currently, with this series, I am trying to create an habit for myself.
More than sharing what I found interesting online, it helps me struture my digital watch, and hopefully, i will be able to do the same with other aspects of my life.
If you want to do something similar, this article may give you some key points on how to do it.

Test Failures Should Be Actionable

This article contains a huge piece of advice, that can make us gain a lot of time, as we all have encountered errors with poor quality messages, that forces us to take the time replicate them (when it is possible).
And all that time could have been avoided by a better error message. It is true in your client code, as in your test code.


I hope you enjoyed those articles as much as your morning bevrage, and that they gave you some interesting knowledge.
Personnally, I read them while drinking my first cup of coffee of the day ☕

Have a splendid day, and see you in the next Morning Code Sip articles. 😀

Laisser un commentaire