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.
A few of our wonderful QAs at REA Group
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
DevOpsDays Sydney 2016 took place recently in the Sydney SMC Function Centre, by Goulburn Street. The halls were named after Greek columns. Ionic, Doric, Tuscan. Pillars. Many of us from REA were in attendance, along with leading practitioners from around the country. Continue reading
Good [insert time of day here] to you my friend.
Welcome to the October edition of the girlapalooza’s monthly blog post, this edition’s topic was not voted on, however I promise democracy will be restored next month. Continue reading
In this blog post, I'm going to demonstrate how Reactive Streams can allow us to elegantly work with DynamoDB, a key-value data store with a predetermined write capacity.
DynamoDB is an Amazon managed NoSQL database.
Amazon DynamoDB Documentation
The performance characteristics and client behaviour of DynamoDB are very different to traditional data stores (for example, databases). When working with a relational database, performance may gradually decrease as load on the database increases. DynamoDB tables have a configurable read and write capacity, specified as the number of reads / writes per second the table will accept. AWS charges based on the provisioned capacity. Exceed this limit and DynamoDB will reject the read / write. If using the AWS Java client, this failure will be represented as a
In this blog post, I'm going to provide a very simple explanation for Applicatives (aka "Applicative Functors") just the way I know them. I'm not going to cover the math behind it, or the laws which applicatives must obey.
I've taken a reverse approach compared to many other posts explaining Applicatives: rather than starting with what Applicatives are, I'm going to start with some examples to demonstrate the need for them, then I'll show how Applicatives can be used and at the end, I'll briefly cover how they can be implemented. Continue reading