Ever wondered why there are so many different names for the objects that mimic behaviour of the 'real' objects in a system - mocks, stubs, fakes, doubles...I can't help looking at the tables of definitions on this page and think why bother!Why have all these mocking frameworks gone and raised the bar of understanding for people who don't like TDD or who don't currently do TDD. To me everything is a mock if it's not the real thing - pure and simple. So when I write tests I call everything a 'Mock' so the tests are easy to read & understand by...
Tuesday, 29 September 2009
Monday, 28 September 2009
If you're doing distributed systems development your systems will be coupled together - period! You can't get away from this statement it's a fact of life. Now how much you're coupled is another question.After the revelation I had last week that most REST systems aren't REST at all and are in fact just over-elaborated RPC (oh look we've reinvented CORBA again!) - link. I've come to the conclusion that REST systems aren't easy to implement and anyone who tells me otherwise doesn't know anything about distributed systems!If REST systems were as easy...
Friday, 25 September 2009
How often do you hear:'Why do I need to write tests when I've got a perfectly good test harness?'Now I hear this often and I'm not surprised anymore when I hear it, it's a sign of a dis-functional team where team members don't value the team they only value their output.I've highlighted the words that give it away:'Why do I need to write tests when I've got a perfectly good test harness...'There is no 'I' in 'TEAM'!Anyone who insists test harnesses are just as good as automated tests is plain wrong.They're selfish developers who only care about...
Wednesday, 23 September 2009
I work freelance and like most freelancers I change job relatively frequently so therefore I do a lot of interviews. One thing I've noticed when being the interviewee is the amount companies lie!One of the common technical lies I hear is 'We use TDD, all code is under test and we run automated builds...'I use to take this at face value - being a trusting fellow and not wanting to judge someone to quickly ;)So if I want to know how much truth is in the statement I could follow up by asking about mocking frameworks, BDD & Dan North etc...But...
Monday, 21 September 2009
I was researching RESTful APIs today, it's couple of months since I worked on a RESTful project and I'm thinking of doing a small project with a RESTful API.I discovered this link and found out that all my previous RESTful APIs aren't really RESTful ;)So after discussing this on Yahoo groups I feel like I know nothing about REST now :(Feeling stoopid now...Awkward Co...
Saturday, 19 September 2009
Friday, 18 September 2009
This is a question that keeps coming up and I know if you're practicing it's a no brainer but I keep getting asked this by devs (I'm no testing God!).The long answer is to read this book and pay attention when talking about 'inserting a seam'.The short answer is carry on reading...Now several people (read Jimmy Bogard) have already answered this but here is my take on this looking at my current client, they have a lots of deeply nested static dependencies - these are implicit dependencies and what you really want to is explicit dependencies because...
Thursday, 17 September 2009
Ever had a situation where you're OLTP requirements are impeded by your OLAP implementation, well to put it another way - have you ever come across an auditing solution that causes transactions to timeout when you're trying to save data into your production database.Well the answer for me is far to often for my liking and this is an example of 'synchronous auditing' and I believe this is an anti-pattern in the making. I'm firmly in the camp that believes auditing should be done asynchronously by a different (application) process. The reasons why...
Okay it's nothing new and not even original but I wouldn't to get down my currently preferred implementation of the repository pattern. I suppose this was prompted by a blog by Jimmy Bogard and Oren's statement a couple of months ago the repository pattern may be near then end of it's life.I still think in the .Net world they have great relevance as most .Net devs can't organise code for toffee and when you try and introduce layering into an application the use of an explicit repository layer is the first layer they seem to understand.So here is...
Long time since I've posted anything but I came across an interesting problem the other day whilst I was working - 'How can I audit changes to specific entities when using nHibernate?'There are several implementation out there already (see Oren's & others posts) but of ones I've seen they are to low level for my liking - they push the auditing of changes into the NH infrastructure away from the Service implementing the business behaviour. I want my service to control and define what is audited I don't want everything audited in the same manner....
Subscribe to:
Posts (Atom)
