3 Comments

Hi, I'd love to hear/read more about TDD

And i think when deferring decisions about object creation in your last para is so simple, realistic and important. While creating a class is straightforward, coming up with the right API is challenging, especially when the core complexity lies in the algorithm. I prefer addressing the most risky elements first, then turning to the enjoyable task of crafting a succinct and effective API and often its not easy. Requires a different mindset from the one used in algorithm problem-solving, aiming to develop an API that is simple, clear, and user-friendly.

Maybe its easy for a like a stack, but it generally holds true.

Expand full comment

I like these little thoughts that open your eyes to a completely different perspective. Shuffling the order of decisions, creating the object as late as possible, experimenting with the algorithm just inside the tests — really cool exercise, thanks a lot!

Expand full comment

It's early Friday evening here and it's been a long week... but the exercise in here is almost making me want to go back to my computer and play around 😂

Where to start a project using TDD has been a bit of a head scratcher and this article/example is giving me a lot more confidence in just jumping in. Thank you!

Expand full comment