In this episode, we talk about what a good backup strategy looks like and the different kinds of data you should be backing up.
Stay safe and think about your backup strategies.
Subscribe now:
In this episode, we talk about what a good backup strategy looks like and the different kinds of data you should be backing up.
Stay safe and think about your backup strategies.
Today we talk about logging. When to log, how to log, what to log – our thoughts on the subject.
In this episode, Donn and KG talk about the post Tim Bray recently wrote – Why Google did Android. They then touch on Chrome becoming a monopoly and tips on what folks can do to be a little more privacy conscious on the web.
We’ve all heard of the Y2K problem, but there’s also a similar coming up this 2038 for us programmers. In this episode we dive into the 2038 problem (… after of course talking about our opinions on new year resolutions).
Get 1% better every day folks… Listen here:
In this episode KG and Donn talk about KG’s recent jaunt with Docker. In the attempt to setup continuous deployment for his blog, KG explains his simple requirement and how it lands up requiring some basic Docker. Donn then closes it out with some interesting in-depth knowledge on how to use Docker
It finally happens! KG and Donn talk about Coroutines with two experts at Google Manuel & Sean. We’ve waited quite sometime on Fragmented to discuss this topic. We wanted to make sure Coroutines was mature enough to be compared with the contenders. Listen to find out more!
In this decompress episode, Donn and KG talk about how their 2019 went. It goes from Dagger talk to Kotlin talk to Kotlin Conf talk. Give it a listen and enjoy!
In this episode, Kaushik tries to talk through this question.
How do you know what to test when you don’t even know how to write the code that you need to test? This is a paradox that many developers find themselves in daily.
In this episode Donn talks about his strategy for dealing with unknowns in programming, namely around testing and how to figure out how to write tests for new code that might be difficult, unfamiliar or even legacy code.
