Skip to main content

Review of 2018 / Looking forward to 2019

Wow - looking back over my posts, my last review of the year was in 2013. Interestingly it feels like I've just had a very similar year and I'm feeling excited about 2019, the same way that I was for 2014!

During the course of 2018 I've had 4 roles in 3 different companies - no wonder it feels like a long year!!! Over the past 5 years, the role I started back in 2013 had grown and changed beyond recognition through several acquisitions. Whilst I'd been looking around for a while, a role change at the beginning of the year highlighted that it was time to move on. Unbeknown to me, the company joined over the summer was undergoing some quite large organisational changes itself whilst I was working out my notice. As a result of those changes I joined a role that really didn't bare much resememblence to what I was expecting. As luck would have it, catching up with a former manager resulted in my current role, which I'm now 2 months into.

I've joined an European travel insurance company as their tech lead, to help them position the technical team and platform to take on the challenges as the company enters the next phase of it's life. Over the course of 2019, I'll hopefully be looking at a lot more Azure (basically everything across that platform) and .NET Core - possibly with a bit of Vue thrown in for good measure. If the year pans out as I hope, I'll be getting my hands dirty with production code a lot more again.

Whilst I haven't blogged anywhere as much as I had hoped, I've stayed pretty active in the developer community. At the start of the year I helped out at Codebar Brighton and did a day's codeathon for the Humanitarian Toolbox. I've also attended various monthly sessions at Worthing Digital, Brighton Alt.Net and Mobile Meetup. I was also lucky enough to again attend the free DDD Reading conference.

I also got my SAFe practitioner accrediation, which was really interesting and useful to see how it can help a company that needs to manage large number of developers in an enterprise environment. From my brief experience of the process, whilst I can see how it can help in certain situations, I have to say that I won't be too disappointed if I don't get to use it again.

So what do I hope 2019 will bring?

  • Azure: I hope that I'll finally get some production code into Azure and gain a lot more exposure to the platform. I am interested at looking into Azure Architecture accrediation, so watch this space.
  • Vue: I quite like React, but I think Vue is better placed in my current role. Learning both has just confirmed that I'm never going to be Angular's biggest fan!
  • HTML/CSS: I've not had much call in recent years to keep my HTML/CSS skills at a level that is needed for public facing websites, looking forward to changing this.
  • Blogging: I'm hoping that doing more coding will help get me back into blogging again. Page views for my blog are hovering around 1-2k per month, it would be good to get that up to 10k by the end of 2019.
  • Mobile: I don't think there will be much call for this in my current role, but would like to keep my hand in on both Android and iOS development, maybe this will be the year I get at least one of projects I have on the go into the App Store.

So roll on 2019, it will be interesting to see what the year review will be like?

Comments

Popular posts from this blog

Mocking HttpCookieCollection in HttpRequestBase

When unit testing ASP.NET MVC2 projects the issue of injecting HttpContext is quickly encountered.  There seem to be many different ways / recommendations for mocking HttpContextBase to improve the testability of controllers and their actions.  My investigations into that will probably be a separate blog post in the near future but for now I want to cover something that had me stuck for longer than it probably should have.  That is how to mock non abstract/interfaced classes within HttpRequestBase and HttpResponseBase – namely the HttpCookieCollection class.   The code sample below illustrates how it can be used within a mocked instance of HttpRequestBase.  Cookies can be added / modified within the unit test code prior to being passed into the code being tested.   After it’s been called, using a combination of MOQ’s Verify and NUnit’s Assert it is possible to check how many times the collection is accessed (but you have to include the set up calls) and that the relevant cookies have …

Problem installing AWS CLI

It never feels like a good start when you're trying to start out with something and the install fails with an obscure error! I was just trying to install the Amazon CLI following the instructions at https://aws.amazon.com/cli/ and ran into the following error when running 'pip install awscli': Collecting awscli Could not find a version that satisfies the requirement awscli (from versions: ) No matching distribution found for awscli I appeared to have a correct version of Python installed (v2.7) and checking "PIP -v" indicated that 9.0.1 was installed. That all seemed to tick the required boxes but digging around a little more I did see that some people had had issues with various versions of PIP so I found / ran the following to upgrade to the latest vesion: curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py python get-pip.py This installed v9.0.3 of PIP which burst into life when I re-ran 'pip install awscli' and everything seems to be ok. Like…

Injecting HttpContextBase into an MVC Controller

It is a shame that when the ASP.NET MVC framework was released they did not think to build IoC support into the infrastructure. All the major components of the MVC engine appear to magically inherit instances of HttpContext and it’s related objects – which can cause no end of problems if you are trying to utilise Unit Testing and IoC. Reading around various articles on the subject just to get around this one problem requires the implementation of several different concepts and you are still left with a work around. The code below, along with the other links referenced in this article is my stab at resolving the issue. There’s probably nothing new here, but it does attempt to relate all the information needed to do this for Castle Windsor. The overview is that all controllers will need to inherit from a base controller, which takes an instance of HttpContext into it’s constructor. It then overrides the property HttpContext in the main controller class, supplying it’s own version…