What does it mean to “grow up” to the next level of how we work? How do we take hacking to find a solution, any solution, and turn it into a purposeful, logical craft? It’s a question I’ve been trying to approach for the last year. So, when you ask me what I’m doing these […]
In past posts on this blog, and conversations with mentors, colleagues and friends — we have lamented the difficulty of the learning path for the intermediate coder. The posts I’ve been writing about recommended book readings are part of a step forward. But if one is not careful, they become an academic exercise. It’s in […]
This week, we leave Fowler’s Refactoring behind in favor of embarking on a journey exploring design patterns. As I understand it, when writing code, there are certain ways of structuring a program or application as a whole that are patterns on which we can base the design of code. This is a topic that has […]
Continuing our journey through Fowler’s refactoring book for this week, we covered a lot of ground which mostly concentrates on the role of testing (Chapter 5) and selected refactoring that seemed most relevant. They did a nice job attacking some of the common problem areas I have (including complex conditionals, too-complicated functions and data structures).
I’ve been in very much a learning space at work, even moreso than usual (writing my first test-driven and object-oriented Ruby code these days), and I am thankful to be in a place where I can learn and grow. As I approach my learning with a redoubled effort, it feels like some sort of balance […]
I finally no longer feel strange when someone calls me a programmer — I have learned to own it. It’s taken me the better part of five years to feel that way, but here we are. At the end of 2011, I wrote a post lamenting my code quality, and I still feel that way, […]