A practical method for maintaining context across sessions, validating understanding, and turning AI collaboration into well-documented, testable code.
Recently I had the opportunity to run a retrospective ceremony focused on Roles and Expectations. I've used a combination of a couple of known techniques (credits to FunRetrospectives) and this post is to share the format I've used and how things went in general.
In this article, I’d like to explore a couple of implementations of sorting algorithms. However, I’d like to do so driven by unit tests. The examples are written in Go but don't worry if you never worked with Go before. The emphasis here is on the journey and the joy of building solutions guided by tests!
In this post, I'd like to discuss how Marshalling/Unmarshalling process is usually applied in Go programs. I'll give some examples of how it is used in practice with some code examples (i.e. data parsing) and then expand on other usages when we have the need for transforming data across different domains.
In this post, I'd like to share alternative approaches for dealing with conditional rendering in React. I will try to list out the pros and cons about 3 different approaches (doesn't mean couldn't be more!) and hopefully this can be useful for you someday.
Quick write-up about handling multiple .gitconfig files (personal and work-related configs)
As I became to customise my settings more and more, having to set up a new environment wasn't an exciting thing to do anymore. I not only have to remember to install all of these things that I need, but it became also tedious and demanded a large cognitive effort. Also, I got frustrated many times because I thought I was all set up until I realised I forgot to install a particular tool. This post shares some things I've learned when comes to automating my environment setup.
My personal exposure with TDD over the years.
The structure of this blog
Introduction about who I am, my background and the values I try to stand by.
