As a software tester, I hope you already know the value of focussing on a specific task. There has been many studies to prove that multi-tasking is not as effective as we may think and cost of switching context in our brain is huge. That is why practices such as session based testing are so effective.
However, it's easier said than done. Distractions are everywhere. You can be distracted easily by
- A Twitter or Skype notification on your computer screen.
- A noisy workplace environment.
- Your manager or a colleague.
- A call or a text message on your cell phone.
- Push notification from apps like Facebook, What's App, Linked-In, Emails etc.
- Thousands of other things such as smell of food / coffee from the kitchen :-)
It's hard to maintain focus. Do you agree?
We can not remove all the distractions. We can not control all of them. However, some ...
Exciting times :-)
Some of you know that I have been working on Planned Departure for a while now. Till now I was working on it on the part-time basis. However, now we have our team in place and we are moving in our own office. YAY!! My primary focus now would be to drive business and manage development of Planned Departure. If you do not know what Planned Departure is, please have a look at this one minute video.
It's a big problem. Last year, identity of around 2.5 million deceased users was stolen in US alone. Do you want to take the risk or protect your digital assets?
Yesterday I was thinking about the importance of having a pause button for the tester and wrote a post on the Linked-In. In my opinion, without understanding mission and identifying stakeholder, there is no point in focussing on scope and strategy. I have shared my experience to substantiate this claim where asking WHY made a difference in the project I was working on. Please read Remember Why before What and How on Linked-in and let me know your thoughts.
BTW, if you are on Linked-In - feel free to connect with me.
I am sure you have seen this debate many times online. You may also have strong views on whether testers should be able to code or not.
Well, In my opinion - testers should be able to write code.
I have just published my views on this here .
Please have a look - would be nice to hear your views on this.
It was good to meet all the regulars (you know who you are :-)) and many new people. It’s always nice to hear experiences of fellow testers. Incidentally, John from Sauce Labs was also there. Sauce Labs is a special company for our community because of Jason and so it was nice to hear from John how Sauce Labs is progressing.
We invited Costin to share his experience. It was great to get insight on the challenges of testing analytics in mobile world. Unfortunately this talk was not recorded - I will check with him and see if his slide-deck is available somewhere.
One of the main reason for me to go to meet-ups is to learn something new and Costin’s talk gave me plenty of things to learn ...
Let’s Test party is over. I am back in London and still trying to absorb everything. I will need to write few blog posts to cover my experience @ Lets Test - this is just start :-)
Let’s Test was on top of my must-attend list from past two years and I am glad I could attend this year. In my opinion, one of the biggest advantage of attending a conferences is being able to confer and Let’s Test provides perfect environment for that.
I reached Stockholm on Sunday and thanks to the power of twitter - I met Richard , Christopher , Geir and Amy at the airport. See the usefulness of this medium? If you are still not on the twitter, come and join us :-)
After checking-in, I headed straight to the lobby and got few tips about the area and nature walk from Carsten . In the next half an hour ...
So this image triggered some discussion on twitter and I think it's worth explaining it a bit more.
With this image, I wanted to highlight two main things
- Shortage of skilled / inspiring testers
- Need to move up and become skilled and inspiring tester.
There is no scientific basis for this image. This image is purely based on what I have observed or experienced. I have met people who would be a perfect fit for the categories I have created. Also, this pyramid has nothing to do with the experience - It's possible to spend entire lifetime as a lazy tester and newbies can be truly inspiring. Also, it's not a progression as such - skilled testers doesn't mean that they'll have to be community builders, domain experts or decent coders. I have used pyramid to show only one thing - size of the pool.
I have seen fewer ...
This is the first time I am publishing my goals for next year public. This will probably put some pressure on me and might give some ideas to you as well.. So here is my list
Things I need to learn to remain a relevant technical tester
- Functional programming languages and NoSQL / Non-relational databases
- Tools available for testing native and hybrid Chrome and iOS apps
- Ops tools such as Kibana, Splunk and deployment tools such as puppet
- Mocking frameworks & tools which give insight on automation coverage.
Things I need to do to contribute meaningfully in the software testing community
- Make London Selenium Meetup Group more effective and organise quarterly meetups
- Active participation in discussions on twitter, blogsphere and software testing club
- Start writing reviews of the books I have read / reading
- Submit articles for StickyMinds, Testing Planet, Testing Circus and TeaTime With Testers
- Share automation code and examples with the ...