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.


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 …

Do "Task Hours" add anything in Scrum (Agile)?

What do task hours add to the overall process in scrum?This was a question that has arisen from all team members in both instances that I've helped teams switch over to scrum. The benefits of artifacts like the comparative story point estimation, the 2 week sprints, stand-ups and the end of sprint demo have been self evident to the team, but as one I think every team member has expressed dismay when it comes to task planning and estimating each task in hours. Left unchecked there is a natural tendency for people to actually begin to dread the start of each sprint purely due to the task planning session.In my current role we've been lucky to investigate this further as a team.The team sat down to discuss the problems it was experiencing with estimating tasks in hours and the following common themes appeared:It is hard: Maybe it shouldn't be, but time estimation is hard! Story points are comparative and abstracted making them easier to determine, but time estimate is gen…

Why do my Android Notification only appear in the status bar?

I'm definitely getting back into Android development, I'm remembering that feeling of 'Surely this should be easier than this!'. All I wanted to do was to schedule a local notification which behaved similar to a push notification pop-up. That is, as well as showing the small icon in the status bar I wanted it to pop up on screen to notify the end user. All seems fairly easily, I found this code for how to schedule a notification. That all worked perfectly, apart from the notification would only appear in the status bar. Searching around I found loads of different answers / solutions, mostly all saying the same thing:It only worked if you used 'NotificationCompat.Builder' in place of 'Notification.Builder', orYou had to set the priority to 'NotificationCompat.PRIORITY_HIGH'As usually happens, none of these solutions worked for me until I added in the missing piece of the jigsaw:- '.setDefaults(Notification.DEFAULT_ALL)'. For me this…