These days I’m spending time looking into testing in Clojure. I’ve been writing my share of test cases in PHP at work. There we have several tests “freezing” time or mocking services. Both practices are common and something worth learning for Clojure.
Read more...
I find work-related inspiration in many places, among others, colleagues meetups and conferences. But most inspiration comes while purposelessly roaming the internet. I’ve always been interested in more than writing the code for the software. Whether it be participating in meetings and discussions that would help me better understand the business. Gathering data to predict how a UI should be formed for optimal user experience. Learning how to avoid making poor software design decisions that would bring the nice people in operations in trouble. But also the softer things like how culture and circumstances affect us as developers and individuals.
Read more...It takes time to understand a problem, because before you can fully understand it, you need to also understand its context. As a code base grows, depending on how well the code is structured, the context in which you need to understand the problem can (and often will) grow.
Read more...Having been given a new area of responsibility as team lead inspired me to think about aspects of coding beyond just typing it.
Read more...When learning something new (in this case Laravel and it’s ORM Eloquent) it is always nice to be able to “look behind the curtains” to see what actually happens. This both helps you understand the internals of the things you are using and can sometimes make bug squashing a lot easier.
Read more...