Pages

Subscribe Twitter

Saturday, 4 February 2017

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.

Sunday, 29 January 2017

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', or
  • You 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 fixed the problem, the scheduled notification began to pop up on the desktop as expected! Looking into the Android documentation for this method nothing seemed to make sense as to why it would change the behaviour of the notification. As the documentation made reference to default sounds I replaced the call ".setDefaults(...)" with ".setSound(...)" and tried again. Again, the notification behaved as desired and appeared as a pop-up. Not making calls to either of these methods resulted in the notification reverted back the undesired behaviour of only appearing in the status bar. Adding either or both of these calls back in caused the desired behaviour. I'm still not completely sure why at the moment, but adding a sound to the scheduled notification sorted the problem out for me.

These 'pop-up' notifications are called “Heads-up” notifications and were introduced with Lollipop (v5.0).

Saturday, 14 January 2017

Links for starting out in Android development

A recent discussion at work made me realise that over the past few years learning Android development I've managed to build a short but very useful list of links for starting out. Not a really detailed post this time around, but hopefully these links help at least one person, let me know!

  • Development environment: We started out using Eclipse, but now feel that there is only one IDE to learn, Android Studio 2.x
  • How to documentation: This has always been a big struggle, much of the information that you can find is quickly out of date and potentially incorrect. Luckily a team of volunteers have set up the Codepath Android Cliff-notes as a Github wiki. This team have also recognised the difficulty faced by many starting out with Android development and have put together a list of articles tackling everything to do with Android development and are maintaining that list to ensure it is regularly reviewed / updated to keep it relevant and useful. I really wish I'd found this when I first started out.
  • Training videos: At my company we all have Pluralsight subscriptions (well recommended). I can recommend the course by Sriyank Siddhartha. Again, everything ages with Android really badly so these articles were useful around 2016/7.
  • More detailed videos: The Android development team at Google put together a great YouTube channel. These videos are usually really in depth but require a little more than entry level knowledge to get the most from. Either good to watch to get a feel for what's available or coming back to when you need to tackle a particular problem.

That's all, enjoy learning Android!

Tuesday, 15 March 2016

How to stand out in a phone interview

I can still remember my first phone interview for a job. I had no idea what to expect so really wasn't looking forward to it, but it can't have gone too badly because I got the job. Now that I've been lucky enough to progress in my career to positions where I'm conducting the other side of the phone interview I've been quite surprised how little it takes to stand out from the crowd:

1. Be Prepared
When booking the interview, consider how much time you'll need to get to where you can comfortably take the call. When the interviewer phones you'll want to be nice and relaxed and able to take the call within a couple of rings. If you're struggling to find your phone, not drop any paper work or find a place out of the wind / pull over in your car you will already be putting yourself on the back foot.

2. Smile when you speak
Don't sound like you've just been called at 6am on your day off! When you answer the call make sure you sound happy and show that you are looking forward to speaking with the interviewer. They may have lined up several phone interviews that day and if you're the only one that sounded happy / pleased to speak with the interviewer; guess who they are going to remember!

3. Show that you were expecting the call
At the very least you should try to say "Hello, {{your name}}", even better say "Hello, {{your name}}. Is that {{interviewer's name}}. It's good to remember that the interviewer has been given your number from the recruiter and is probably hoping they've got the right number (it does happen) or they've entered it correctly (also can happen). By doing this small thing you are both helping the interviewer and showing that you were expecting their call. You're also helping to sell yourself from the outset in showing that you would be a great representative for the company if you were to be successful.

4. Expect a bad mobile signal
Technology is great, but chances are the phone company will wait until just before your interview to take the nearest mobile transmitter out of service. If the signal is bad, don't try to make do during the call, acknowledge the problem to the interviewer; ideally offer an alternative number (land line / skype) to use instead or just to try reconnecting the call (it's amazing the number of times that cures the issue). If you are answering a question with a long answer, make sure you give chances for the interviewer to confirm that they are still on the call.


And there you have it, just 4 really simple points to standing out in a phone interview; but please remember that sometimes you can do this and more and still it just won't be your day!

Sunday, 13 March 2016

Interviews: Sometime it just won't be your day!

Sometimes, no matter how much you prepare, you're just going to have a bad interview! I just wish someone had given me that nugget of advice when I was starting out.

If you're into fitness, as you're probably painfully aware, some days you can be really looking forward to a run / swim / workout. But when you start you just can't get into it! In these situations people generally have no problem classing it as an off day and moving on. But almost everyone expects to always be on their 'A' game when going for an interview. Obviously comparing going to the gym to an interview, the external pressures are completely different:

  • Maybe you really need the money,
  • Interviews are thin on the ground
  • or you just really want the job!
However just like going for that run / swim / workout, no matter how much you want it - some days it's just not going to go your way! The best thing you can do is look to see what you can learn from the experience and move on. Just like keep fit sessions, you'll probably ace the next one and wonder why you were so worried.

Saturday, 20 February 2016

Is your company investing in you and your career?

In my previous articles I have written about are you investing in your own career and starting out in software development. But there is another important question, is your company investing in you and your career?

In my current role, I am lucky to work for a great company that values it's teams / employees and have been able to implement / roll out the following for my development and test teams:

  • For the development team, individual PluralSight subscriptions. The test team use Ministry of Testing amongst other channels
  • An hour per week self study (watching Pluralsight videos, etc) to learn about any development / test subject that they are interested in
  • An hour per week for each team to get together and discuss improvements / changes they would like to make to their environments / processes
  • A weekly 1-2-1 to discuss the previous week, what they have learnt and any progress against objectives. Annual reviews become a highlight / review of that year's 1-2-1 notes; allowing much more time to concentrate on and discuss the plan for the coming year
  • The ability to attend any free day conferences on relevant subjects (we do also go to paid conferences)
  • Group trips to community events in the local area
  • Pair programming team development exercises

To start with an hour per week self learning might not sound much, but it is a small, constant amount which over the course of a year adds up to 45+ hours (once you take into account holidays, etc). This is similar to the time you'd spend if you went to devWeek or a similar conference every year; which I'm sure you'd agree is a pretty nice benefit. I also recommend that the team don't spend this time learning about anything they are currently working on. Since we've been doing this the team have learnt about, recommended and agreed various new technologies that we are and will be using on future projects. We've learnt about features / libraries in different unrelated programming languages which we've since applied in our day to day usage of .NET. This simple process has paid back at-least ten fold for the time we've invested in it and the team are constantly learning new things.

Similarly, the pair programming development exercises have been really successful. Picking a particular task / challenge we've run several sessions trying full on TDD (something we are using in our new system and slowly introducing to our legacy code base), recoding to remove primitive obsession and removing any conditional logic.

We're also investing in training up new developers / testers to help build a balanced team and give something back to the industry. Those new starters get a great founding from the above, plus the rest of the team get the opportunity to learn by being a mentor (which research says aids retention of new skills).

So far we're finding this is working really well for us, the teams are engaged, constantly learning and really happy; which is leading to obvious productivity benefits for the company. Strangely, given the obvious benefits, this approach seems pretty unique in the software industry, even Google appears to have abandoned it's famous 20% innovation time. I'd be interested in hearing from people who's company has implemented something similar and their experiences, as I'm sure we can't be the only people doing this.

If this sounds like something you'd like to experience and are looking for your first opportunity or a new challenge, then check us out as we're a growing team and often have openings. Just remember the most important point; it should be a joint investment in your career!

Sunday, 14 February 2016

Starting out in software development

If you're trying to begin your career in software development it might feel like all the positions you see are asking for previous experience and there are few opportunities to gain that required experience. In my opinion, as a relatively new industry, it feels like we're currently going through some growing pains. Companies are struggling to find suitability qualified mid / senior developers but very few organisations have a plan in place to help train the juniors required to feed into the system to generate tomorrow's mid / senior level developers.

I also feel that the current (UK) education system is letting down graduates by not preparing them with the programming skills needed by the industry. It seems like it is possible to graduate a computing degree with only a few months exposure to actual development. This practical experience is critical to understanding the theory and it's application. I'm sure I'm not alone in that feeling, with Scratch and the current crop of micro computers, such as the Raspberry PI, focused on building a new generation of developers similar to ones that cut their teeth on Sinclair, Amstrad and Commodores, or in the early days of the web.

But that doesn't help you if you're trying to enter the industry and are experiencing companies that are all looking for developers with at least one previous role. The good news is that it has never been easier to improve your coding ability. To stand out from the crowd you should invest in your future career by:

  • Code, and code again: There are various coding dojo / kata sites that have many programming exercises that you can practise in your chosen language. This is the number one recommendation I can make, do these and do them again, trying them in a different language or look to see how you can improve on your previous attempts using what you have since learnt. Get a Github account and commit your code to demonstrate your skills, if you only link to one thing in your CV - make it your GitHub account!
  • Stack Overflow: We all use Stack Overflow when things get tough but don't be a lurker. Set up a profile (ideally with your real name, see the last point) and ask questions if you can't find an answer to your issue (don't worry, all the questions haven't been asked yet). Take notice of the feedback you get when asking questions and if your question doesn't get any answers / feedback, revisit it and see if you can provide more detail to clarify / define your issue further. You'll be surprised how quickly your writing / question asking skills will improve. Also it's a great buzz when you find a question that you can answer and even more so if it gets accepted!
  • Be part of the development community: Do a Google search for any events that are taking part in your local area, if you're lucky you'll find a group using the technology you are interested in just down the road from you. Be brave, the first one can be a little scary but if it's a good group they're always welcoming to new members and see my initial comments about the current state of the industry. The people running these groups are aware of the challenges in recruitment and will want to help you. Make sure you continue going and take time to get to know other people, if you follow most / all of the points listed here then it can be a great opportunity to find a fantastic role in which you could really grow.
  • Learn: Depending upon the language you're looking to learn, you'll be be able to find varying free or paid training sites. .NET has Channel 9 whilst Android has a fantastic YouTube channel. Whilst it is not free I am a big fan of the content on PluralSight which covers many different languages and technologies as well as having some good videos on career development too.
  • Stay up to date: Get on twitter, follow popular blogs (maybe even this one), listen to Podcasts. Find out what the current trends are in the technologies you are interested in. Many technologies have forks / competing versions (Python/Node) and/or a next version with breaking changes (.NET core/Angular). Being aware of these things and what they mean can make a big difference during the interview process.
  • Blog: Writing a blog can be extremely difficult, I've found it to be one of the hardest things you can do. Don't expect it to be an overnight success, all the advice is that you need regular content that is relevant to attract return visitors. Keep an eye on your stats to see what your most popular articles are and try to determine why. It would be nice if it was my content / writing style that was the draw but my most popular articles are ones that contain a clear error message so are obviously being turned up by web searches by people that are having the same problem. I can remember feeling fantastic when I noticed Stack Overflow in my referrers and found that someone had linked to one of my articles in their answer.
  • Find a mentor: This is something that I have heard about recently in a podcast, there are several coding mentor sites out there. I can't comment on their quality / integrity I'm afraid, but it is something that I'm going to be looking into further.
  • Build your online presence: Make it easy for future employers to find out as much as they can about you with the minimum effort on their part. Use it as a chance to demonstrate your web skills, get a domain, put a web site up and make it look good (note to self, follow own advice).
  • Remember it's about shipping stuff: A bit of a bonus point really, demonstrate in the interview that you're aware that code no one is using has no value no matter how well it is written! So it's all about early visibility/feedback and SOLID, DRY concepts and automated unit testing should only exist to help promote that and make shipping easier / repeatable.

If you follow some or all of the steps above, you can be sure that you will stand out from the crowd! I wish you good luck in your journey in software development and if this article helps it would be great if you left a comment to let me know.