Tech Work

„Hacking debt“ – never stop tinkering

John D. Cook wrote an interesting brain teaser about „hacking debt“. Not to be mistaken for „technical debt“. He means that as a programmer you should make room for tinkering, learning and fiddling with new technology.

I fully agree with this notion and try to find ways in which we can integrate that into the daily or weekly routines. Any best practices that you know of (and no, please no 20% google time stuff…)?