Showing posts from December, 2017

2018 Goals

The following are some professional goals I have for 2018. I'm hesitant to call them New Years Resolutions because these goals have emerged over the course of 2017 and are not a spur of the moment list that I've come up with on the 1st of January. That and I have never liked the concept of New Years Resolutions they seem flimsy, unplanned and all too often they seem to be forgotten by the end of January. So that said this year I aim to: Blog More: In 2017 I posted 9 blogs, not including this one. So I'd like to get at least 10. I'll give myself bonus points if I can average out at 1 a month.  Speak More: in 2017 I spoke at my first conference, DDD Sydney. I'd ideally like to increase that but at least speak a 1 and give several user group talks. That leads to... Submit More CFPs: Last year I only submitted 1. Without giving it much consideration a minimum of 5 seems like a good minimum for this goal.  Keep Coding: This one is a little less S.M.A.R.T. but I re

How bad posture contributed to me loosing a rib.

I was recently given a really strong reminder on the importance of posture. We all know it's important, maybe it might cause your back/shoulder/arm/etc to hurt if you don't do it properly but we put off thinking about it because it's too hard or not that important. The following is a short account of how I was reminded,0 over the course of multiple surgeries and time off work that used up all my sick and annual leave with still more time off unpaid, just how important good posture is. My reminder came in the form of a 15 cm subclavian blood clot in the left side of my chest. A combination of bad bone architecture, bad posture, compressing my chest cavity, and a little bad luck limited the blood flow through the subclavian vein (running between the collar bone and the first rib) causing a blood clot. I reported prominent veins in my chest, some swelling in my left arm and some minor soreness under my arm to my GP and she sent me for x-rays and an ultra sound. The ultra s

The greatest teacher, failure is.

There is a line in the most recent Star Wars film, The Last Jedi, from Yoda. The greatest teacher, failure is. This line resonated with me in relation to software development. Recently at work we've been having some discussions about challenging our preconceptions about how we do things. Now consider the line from the movie, sometimes we do things a certain way because we know  that it's the best way to do things and probably we're right. How do we know? Is it just some innate thing that everyone  knows? Or is it because someone told us that this is the way things are? Lets look at some things about software development that we know  to be true. TDD is good and makes more maintainable code. Global variables lead to un-maintainable code. The language that you don't like is bad. The language that you do like is good. Now when did you last time that you challenged these ideas? When was the last time that you were able to, knowing that you would probably fail?

React makes OCP so easy it's a joke

Composing components in React means that following the Open Closed Principle (the O in SOLID) is so easy that it's laughable. By composing, or decomposing, React components together new functionality can be added and functionality can be removed without making any changes to the underlying components. Want to make sure that you dont show a profile page unless someone has been logged in? Wrap your profile page in a RedirectToLoginIfUnauthorised component, that checks for the user and redirects to login if they have not yet logged in. As a bonus when you split and compose your functionality like this you end up with smaller components, that do less. So by following the Open Closed Principle in this way you get the Single Responsibility Principle for free. Clean Code keeps on delivering.

Why are you estimating?

In a previous job I had a quote stuck up behind my desk that I would point to when a manager asked me for an estimate.  I cant remember the exact wording but the gist of it was something like: Before asking for an estimate first ask yourself what decisions the estimate will be informing.  I loved this quote because it points at one of the biggest problems that I think the software development industry has with estimates, and one of the reasons that they are, so often, so wrong. Too often we estimate work in a vacuum without adequate knowledge as to why the estimate is being asked for, or how it's going to be used.  There are many different, and valid reasons to estimate work, and different situations call for different techniques. For some of these cases the trivariate estimate method that I suggested in  a previous blog  is a great answer that will provide low level detail about the estimate and allow good decisions to be made, for other cases it is a massive waste of ti