I’m in Ireland for the holidays making the most of my time off and the awesome hospitality at my girlfriends home.
Next year I am planning to get away at least once for a spot of snowboarding, buy a tv, take first steps into the world
of I.T. Architecture, save up loads for a house and possibly brew my own beer. Whether I complete all of that is another
story.
See you all in the new year!
We have a crazy microwave at home that seems to count in the hundreds?! Not regular time but in hundreds. Cool you may
think, the microwave is compliant with metric time! But no. Only the first hundred is observed after that it reverts to
regular sixty second time.
Picture the scenario: You’re working on a high profile account work millions of Pounds in charge of a team of skilled
developers all working to create the client’s next generation system. You have to interface with different teams
throughout the project as is the nature with any large delivery project. Teams such as Business Analyst team, Rules
team, Business Process Management team and a CRM team. All teams are working harmoniously with each other. Sure they
have issues and blockers and sometimes your code needs a rethink but nothing out of the ordinary considering the project
is of a fair size.
I wanted to share with everyone the importance of the V model approach to testing. I’ve seen a lot of places (and
people) who don’t understand this approach so this is my way of explaining it.
I’m thinking about changing the name of my blog. Big move - maybe? But I’m pretty sure I can do that with the Blogger
engine. I guess the only thing to worry about is updating people’s links. But no one reads this blog anyway so what’s
the problem?