Skip to main content

Saying yes to one thing is saying no to something else!

The one bit of advice I wish I'd received much earlier in my career is:

Saying yes to one thing means that you are always saying no to something else!

It seems pretty obvious when you think about it, as time is finite. So every little task you take on, is consuming a part of that finite resource. When you're starting out, you're probably 'time rich / cash poor' which is probably the worst combination as it almost always rewards taking too much on. You've got more time and you're still learning, so over committing a little won't hurt surely? The worst possible thing then probably happens, you're rewarded for your efforts with promotion and salary increases.....and the beginnings of a bad habit is quickly formed / re-enforced.

In the beginning you are probably saying no to your leisure time:- I really want to get this done and I'd only be sitting at home and it's only this once / small thing. Slowly, as your career develops, you'll most likely end up with more things than can be done in the hours available (often all the hours in the day, not just work hours). If you're in this situation and that urgent, important work comes along (it always does), then of course you'll need to / should do it. But the next question, after saying 'yes', is 'What other task can be delayed to make space for this urgent work?' Sometimes just asking this question might highlight that that 'important' task isn't quite as urgent as it first seemed in relation to everything else you're currently committed to. Either way, the outcome should be you feeling confident you're still able to deliver on your commitments without sacrificing your social life / health.

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 …

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…

Unit Testing Workflow Code Activities - Part 1

When I first started looking into Windows Workflow one of the first things that I liked about it was how it separated responsibilities. The workflow was responsible for handling the procedural logic with all it's conditional statements, etc. Whilst individual code activities could be written to handle the business logic processing; created in small easily re-usable components. To try and realise my original perception this series of blog posts will cover the unit testing of bespoke code activities; broken down into: Part One: Unit testing a code activity with a (generic) cast return type (this post)Part Two: Unit testing a code activity that assigns it's (multiple) output to "OutArguments" (Not yet written)So to make a start consider the following really basic code activity; it expects an InArgument<string> of "Input" and returns a string containing the processed output; in this case a reverse copy of the value held in "Input".namespace Ex…