Skip to main content

Review of Bose QC35 Headphones

Working in software development, a decent pair of headphones is a must. I've lost count of all the pairs that I've owned over the years! I've had some really good wired pairs but they've tended to die an early death when kicking my chair back to scoot across the office to speak with a colleague and forgetting I have them on my head or round my neck. I did try wireless headphones once before, a pair of Sony's but the limited range, background noise, poor battery life and tendency to suffer from interference sadly had them quickly relegated to the cupboard. After trying a pair of QC-25's in the office and being impressed by their sound cancelling functionality I decided to splash out on the (at the time) newly released pair of QC-35's.

So I've had them for a while now and have been meaning to write a review, which fits in nicely with a new year's resolution to update my blog a little more regularly than I've managed over the past couple of years. In a nutshell I love them and whilst I hope that they survive many more years yet, I would replace them with another pair at the drop of a hat if anything was to happen to them. Yes they are expensive, insanely expensive for a pair of headphones but if you use something every day it's probably worth splashing out on getting something amazing.

  • Sound Quality: There is almost no background noise at all and I've yet to suffer any interference from other sources. I'm really happy with the overall sound quality too. Whilst I've not done any technical tests they sound as good or better than any other headphones I've owned.
  • Comfort: For me they've got this spot on, they neither over grip your head nor move around because they're too loose. Most of the time you can almost forget you're wearing them. I wear glasses and some headphones just never fit right or squeeze the glasses into your head and in the worst case start to hurt after an hour or so. I've worn my QC-35's all day and not suffered this problem or got too hot (another common problem of over ear headphones).
  • Wireless Range: I've read several other people saying how amazed they are with this. For Bluetooth the range is amazing, I can walk around our open plan office with no problems. Like wise I can walk around most of my house too, even going between floors. Depending on how many walls / floors the signal has to go through I can get about a 8-10 meter range.
  • Noise Cancelling: This can be so good it's a bit worrying when someone makes you jump as they want to speak to you. We've had building work going on next door to the office and I've only become aware of it as I've taken my headphones off. In fact, the noise was so loud at that point I wondered how any of my team were managing to concentrate / work. For this reason alone, if you need to concentrate in your day job I would suggest you invest in your career by buying a set!
  • Battery life: Never been a problem. I do hook them up to charge on a regular basis but I've never had a point where I've not been able to use them because they've been out of charge / on charge. The battery life is just at the right level that you never need to think about it.
  • Value for money: They are expensive, there's no getting away from that fact. But as I said earlier, if I need to replace them, I would straight away. It's probably fair to say I can't hear a difference between these and a much cheaper (£50-£100) pair of wired headphones, but these are wireless and sound cancelling. They also aid focusing on tasks whilst at work, which for me makes them a worth while investment.

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…

Problem installing AWS CLI

It never feels like a good start when you're trying to start out with something and the install fails with an obscure error! I was just trying to install the Amazon CLI following the instructions at https://aws.amazon.com/cli/ and ran into the following error when running 'pip install awscli': Collecting awscli Could not find a version that satisfies the requirement awscli (from versions: ) No matching distribution found for awscli I appeared to have a correct version of Python installed (v2.7) and checking "PIP -v" indicated that 9.0.1 was installed. That all seemed to tick the required boxes but digging around a little more I did see that some people had had issues with various versions of PIP so I found / ran the following to upgrade to the latest vesion: curl https://bootstrap.pypa.io/get-pip.py -o get-pip.py python get-pip.py This installed v9.0.3 of PIP which burst into life when I re-ran 'pip install awscli' and everything seems to be ok. Like…