A software engineer building the web professionally for the last fifteen years, recently focused on backend challenges at Babbel.
Recently I had an interesting conversation with colleagues on the topic of writing tests for code. In particular, it was about tests for hotfixes that need to be deployed as soon as possible. In this post, I’ll leave the results of that conversation aside and focus on what it inspired me to think about. On the question “Why do I write tests for code?”
A week ago my friend Pablo and me released the very first episode of Code && Beyond. None of us had any experience in podcasting or ever worked with voice and audio. But we did that!
A (semi)weekly podcast with my friend Pablo and me, two software engineers with more than 35 years of professional experience combined. We talk about creativity, productivity, problem solving, tools, culture, and anything beyond, but still related to the daily life of a software developer.
Give it a listen at codeandbeyond.rocks or in your favorite podcast player.
All my projects are located at github.com/soulim.
Occasionally I post something on Twitter. Follow me at twitter.com/soulim.
Career path and everything related is available at linkedin.com/in/soulim.
In many cases the easiest way is to send an email at hello@sul.im.