Expanding capabilities

, a 1-minute piece by Dev Mukherjee Dev Mukherjee

In the last twelve months we have been doubling down our efforts on transforming into a product business. In my review of the year 2016 I wrote about our interests in virtual and augmented reality. Gaming technologies have been of great interest to many that work at Anomaly.

Announcements like Apple’s ARKit2 hint serious potential in these emerging markets. We have traditionally focused our service offerings around scalable Web and iOS. To enable us to provide products and services in these new markets, we have been building substantial capability in Android, and Unity. A combination of these will allow us to deliver gaming and entertainment applications to several platforms.

Colleagues at Charles Sturt University have been running several research projects in augmented and virtual reality. They’ve often expressed their disappointment of not being able to hire a local studio to assist build applications in this space. Our expanded capabilities will allow Anomaly to provide service to researchers, educators, digital entertainment houses to build such applications locally around the Riverina.

Over the next couple of months we will be unveiling several projects we’ve been working on, in this space. We’re excited to step into new territory and welcome any opportunities to collaborate.

Announcing, Wattle Cloud Platform

, a 2-minute piece by Dev Mukherjee Dev Mukherjee

About a decade ago, in the very early years of Anomaly, we were engaged by Coolamon and Temora shire councils to build them a cost effective solution for conducting business online. Focused on just selling certificate related to land parcels, CouncilShop was a purpose built workhorse. It was a one off engagement and as time passed the platform started to show it’s age, until a couple of years ago the discontinuation of the payment gateway broke the camel’s back.

Anomaly has a track record of delivering projects for Australian local government. We have been trusted by Riverina Eastern Regional Organisation of Councils for over a decade and have delivered several platform including Safe Sharps.

We were to either shut CouncilShop down or enter the market with a solution to not just sell certificates but a complete next generation Internet platform for local government. We decided on the later. Early last year we prototyped the proposed platform and Coolamon and Temora have been participating in a closed Beta since October 2017.

Today, Anomaly Software is proud to announce Wattle, a cloud platform with the mission to accelerate the digital transformation of Australian local government. Featuring a one for one modern replacement for the certificate shop, the release of platform lays the foundation for us to bring any local government service to the Internet. With a customer informed roadmap we aim to aggressively bring services online.

Wattle is deeply integrated with Stripe, a leading payment gateway and Mapbox, a mapping platform for developers, allowing us to build anything that our customers need. Focused on the council and their customers alike, Wattle aims to bring a unified experience to the general public across all councils and a robust workhorse for the council staff.

Affordable at flat annual fee covering all features, unlimited users and transactions, Wattle strives to be the back office of choice for local government.

The platform offers a no obligation 60 day trial inviting every council around country to experience the Wattle difference.

At Anomaly we believe in building software that empowers human endeavour. Wattle Cloud Platform is our investment into local government space in streamlining their work flow.

Learn more about Wattle Cloud Platform

Sharing our knowledge

, a 4-minute piece by Dev Mukherjee Dev Mukherjee

Over a period of five years, we have developed a process of software design and engineering that allows a small team to deliver extremely large and mission critical projects. Part of the magic is sharing the core knowledge amongst the team. At an engineering level we achieved it partly by documentation, mostly with maintaining a sharable and reusable repositories of code. We go as far open sourcing our core engineering knowledge, letting everyone benefit from our collective experiences.

Around this time last year we issued beta invites for Twine. The unexpected departure of the person, who had been leading design on our product for several years had us hamstrung and we had to delay the launch. Asides from highlighting obvious issues with our human resources policies, we were witnessing five years of knowledge just walking out of the door (this was also a lesson of the negatives of remote employment, which I will write about at another time). We had been so caught up in pursuing our product future, that we had forgotten to take out an insurance policy on our design knowledge, documentation and education.

On review the above was also partially true of our DevOps knowledge. Being an engineering process this is far easier to capture than something as subjective as design. Sharing knowledge is about sharing the thinking process. It’s role is allowing a team to carry a train of thought. Our biggest lesson learnt was no matter how small or how big a team, sharing knowledge is crucial. People who deliberately protect knowledge are simply threatened by democratisation of information.

Foundation projects

We set out to document our style, thinking, best practices and develop tooling around each portion of interface design and product delivery. Our aim, to create central repositories of knowledge that all of our projects can assimilate from.

These are referred to as our foundation projects. They are offered under the Apache 2.0 license for anyone to use.

Design: We had absolutely no documentation of frontend technologies like Cascading Style Sheets. I am not referring to syntactical knowledge, but best practices and gotchas. Jekyll has been our primarily platform for prototyping interfaces. Every project was setup better than the previous, what we had failed to do was push the newly learnt habits back into older projects.

We started the Jekyll-Foundation project to establish a repeatable process and centrally document good habits of frontend technologies.

Jekyll-Foundation has been maturing over the last number of months with contributions to plugins allowing us to streamline our build process (e.g automatic annotations of style sheets for Google Closure compiler compatibility). It’s not quite mature enough to receive a 1.0 tag but it’s certainly getting there.

DevOps: A parallel project will cover deploying and scaling Python applications on Amazon Web Services. AWS-Foundation will cover security best practices, auto provisioning and scaling of first class citizens of the cloud.

There’s a plethora of out of date information on the subject. Something that all operations engineers have to dig through and keep references to the relevant information.

Our aim is to maintain up to date master documentation complimented by a reference application that can be used to validate the infrastructure.


Alfred Borden calmly put it as “The secret impresses no one. The trick you use it for is everything.” in The Prestige. I share that sentiment, and have decided to document and share all core knowledge that will allow more people to build quality digital products.