Here at REA we have implemented a street address autosuggest system using Elasticsearch’s Completion Suggester feature. This turned out to be much more interesting and more challenging than expected, and so I thought I should share some of what we learnt along the way. Continue reading
Like a lot of on-call systems ours was once pretty terrible. We had 10 operations staff on-call, and we were responsible for every system in the company. Spending a week on-call usually meant a week without sleep.
Eventually one of the on-call engineers got fed up with this, so they removed every single check from the after-hours notification period. They then went through and selected only the most critical ones to put back in. Continue reading
On the 30th of November I spoke at CTO Summit about Getting to Gender parity without the Awks.
Previous attempts I had made to sum up answers to ‘How can we attract, retain and inspire more women in technology careers?’ had left me fumbling for easy-to-digest responses. My male colleagues wanted to help, but it can be an awkward conundrum to untangle and confront.
On one hand I’m sure I’ve been the recipient of some positive discrimination in my career: was I entitled to weigh in on this subject? Continue reading
“I’m not good enough” says the graduate to herself, shuffling her feet. “All those uni assignments made no difference; everyone knows more than me. Why would anyone want to listen to what I have to say?” Surrounded by self-assured, battle-hardened colleagues, there seems an insurmountable distance to cover—but one day, she’ll surely know enough.
“I’m not good enough” said the programmer with a grimace, starting a new job at a famous company. “Seven years of work and it’s like nothing! Everyone here knows so much; how long will it take for me to know enough?”
So when is enough? Is there a line we cross when we become experts? Does ticker-tape fall from the ceiling, and the mayor of Hackertown give us a medal?
“I’m not good enough” said the veteran of fifteen years. “The people writing these libraries, blogs and conference talks are so smart—am I ever going to know enough to have such an impact?”
Every point on this slope is fractally self-similar to every other, differing only in scale. We know only so much; the unfathomable expanse of the unknown is spread before us. It was like this when you knew a tenth as much, and it will look the same when you know ten or hundred times more again. From the horizon, we all look like ants.
Look at your heroes; the best in the world at what you do. In fact, what they see is roughly what you see: a body of accumulated knowledge, and the brutally vast frontier of their own ignorance ahead.
So when do we draw the line and call ourselves “expert”? Never! This is for fools who have already stopped pedalling. It takes humility to accept that a life’s work can barely hope to recover a drop from this ocean of ignorance, and a noble madness to cheerfully hurl oneself into the waves. If there is a line to draw, it is between these folk and those who turn their backs, turtling in with trinkets and baubles already won.
This light harshly exposes those who can’t empathise with junior colleagues. So, they asked a stupid question. Why did you stop asking stupid questions? Nobody still open to improving themselves would fail to recognise one of their own.
So learn! Abandon yourself to permanent inadequacy. Your life may host any number of hardships, but you’ll never know boredom again. You’ll forget what it was like to endure barren, aimless hours. The waiting-room becomes a study, the bus-stop an opportunity, the laundry a goldmine.
No, you’re not good enough, because there’s no such thing and never was. But you can still head that way.
We have been busily re-building our core property listings experience using ReactJS for a while now. After the release of our revamped sold property section, we decided to find a way to engage the other areas of the company and give back to the local tech community.
With that in mind, REA Group is very excited to announce that on the 8th – 10th February 2017 we will be hosting a ReactJS workshop run by the amazing React Training team. React Training is a US based group comprised of ReactJS experts and the creators of some of the most popular open source libraries in the space, many of which we use here.
When I first joined REA, I soon realised that the QA role at REA is very different from a typical QA role and the roles that I had done previously in my career.
Some of the highlights of being a QA at REA for me are:
- The entire team owns the quality of the work we do. You are not the Quality Gatekeepers
- QA at REA is not defined as Quality Assurance but Quality Analyst
- You are free to venture into previously unknown territory like BA or Ops and it is encouraged
- You are not meant to test every card that gets developed
- Your role is not limited to the testing column on the Kanban board
- If you are passionate about the work, you have a voice in determining what work you actually do
- Your efficiency is not measured or based on the number of test cases you create/execute
- You are trusted with access to most critical production systems, so you can learn and contribute more
- You are not meant to document each and every test case you execute
- You can get help in finding bugs. E.g. Bug bashes
- You can pair with developers on testing
- QA effectiveness is not measured based on the numbers of bugs that you discover
- You can do pretty much anything on Hack Days, be it on a project or your personal project to improve your automation skills
- You can attend a countless number of external training or conferences
- You have a vast array of internal training available, including technologies like AWS and Docker.
- You can be part of the QA Guild where you can bounce ideas off other QAs in the building and share ways of working
- You can get an REA T-shirt just for QAs!
While the role came with a lot of benefits there were some challenges too. Understanding what other QAs at REA do was not easy. This made it hard to learn from each other.
To help increase visibility I decided to come up with a QA Strategy initiative which first will enable us to talk about and understand what QAs at REA really do, and then help us come up with strategies to improve. Continue reading