Why am I blogging?

In short, Steve Yegge said I should.

 Steve made a lot of points in the above post that made me think it would really help me gather my thoughts.  Lessons I have learned in my IT career so far, ideals to strive for, tools I like, tools I dislike etc etc are all thoughts running through my mind.  I think that documenting these thoughts will force me to scrutinise why I feel the way I do about something.

 A great project manager here at the FT forces us to scrutinise our thoughts/suggestions when we express an opinion that is more feeling than fact with a well timed "Why?".  I'm hoping to apply this same technique on my myself with blogging!

 Whether or not I will get these benefits of course remains to be seen. 

 I have to say I was hesitant before starting this, but my doubts were all countered on Steve's post which (along with all his posts) I would thoroughly recommend reading.  In fact if my posts are 1/10th as informed, interesting and well written I'll be very happy indeed.

Comments

Post a Comment

Popular posts from this blog

How to test for connection leaks

Connection leaks are easy to introduce, hard to spot, can go undetected for a long time and have disastrous consequences. It's not enough to fix a connection leak or code against them, you must write tests that would fail in their presence.  Here I will discuss a number of techniques that could apply to many different languages and frameworks.  I have also provided some concrete examples on github which make use of Dropwizard , JerseyClient and WireMock . What is a connection leak? Each time system A talks to system B over a protocol like http, it requires a TCP/IP connection to send and receive data.  Connections can be re-used for different requests, via a connection pool, or a new connection can be established for each request.  Once system A has finished with the connection, it needs to either return the connection to the pool, or close it.  If this doesn't happen you have a connection leak.   Given a connection leak, everythin...
Read more

Nagios vs Sensu vs Icinga2

Choosing a suitable monitoring framework for your system is important.  If you get it wrong you might find yourself having to re-write your checks and setup something different (most likely) at great cost.  Recently I looked into a few monitoring frameworks for a system and came to a few conclusions which I'll share below. Background The System At the time of this investigation, the system (which has a microservices architecture) was in the process of being "productionised".  It had no monitoring in place and had never been supported in production.  The plan was to introduce monitoring so that it could be supported and monitored 24x7 with the hope of achieving minimal downtime. Warning - I am biased Before we get started, I have to acknowledge a few biases I have.  I have worked with nagios in the past and found it to be  bit of a pain.  However, this was probably due to the fact we created our checks in puppet which added an extra layer o...
Read more

Lessons learned from a connection leak in production

We recently encountered a connection leak with one of our services in production.  Here's what happened, what we did and the lessons learned... Tests and Monitoring detected the issue (silently) Our automated tests (which run in production for this service) started failing soon after the incident occurred.  We didn't immediately realise since they just went red on the dashboard and we just carried on about our business.  Our monitoring detected the issue immediately and also went red but crucially didn't email us due to an environment specific config issue. The alarm is raised A tester on the team realises that the tests had been failing for some time (some time being 4 hours... eek!) and gets us to start investigating. Myself and another dev quickly looked into what was going on with our poorly  dropwizard  app.  We could see from the monitoring dashboard that the application's health check page was in error.  Viewing the page showed us tha...
Read more