Imagine you're on a construction site. Documentation is THE currency - safety monitoring, progress updates and evidence for claims all rely on digital media. Yet, no streamlined process exists to capture and organize the thousands of photos and videos taken everyday across construction sites. Site engineers spend upwards of 4 hours a week processing these photos manually but what if there was a better way? Thus Builtview was born - one platform to record, upload and access media for all your documentation needs.

Builtview was the first project I ever worked on professionally so it holds a special place in my heart ❤️ (doesn't everyone's first project?). We took this project from a mere concept to a fully-fledged product rolled out across multiple Laing O'Rourke sites with an ARR over $1M. Having the opportunity to work in a startup environment was amazing; I had lots of freedom and took on difficult features most junior engineers aren't tasked with. Our web app is built on React using TypeScript whereas our backend is instead built using C# .NET Core. It was actually here that I first learnt React and C# all while studying at uni too!

The easiest and fastest way to take photos and videos has always been with your phone, hence leading to the creation of the Builtview Mobile App. By simply opening up the Builtview Mobile app and using the built-in camera function, photos and videos you take are instantly uploaded to our servers which can be accessed by other members of your team from both the mobile or the web. This removed the need to manually transfer and upload your photos to some sort of external storage which was the typical workflow prior to Builtview.

Our mobile app is written in React Native and TypeScript and shares many of the same components as the web app - one of the benefits of using React Native! Sharing our Redux structure also let front-end developers easily jump into the mobile app if needed with little friction. That being said, we also have some native modules for both iOS and Android and we also opted to avoid using Expo in our project. One thing I definitely learnt from developing in mobile is how much more finnicky it is to debug when compared to typical web apps!

ATR Core is a greenfield web application developed by Accenture MyWizard AiOps used worldwide to automate and resolve tickets throughout multibillion dollar companies. Tickets are used in organisations for a range of purposes, from IT Support requests to incident management. ATR Core is able to plug directly into ticket provider sources such as ServiceNow and provide automation solutions. This includes the triaging of tickets to different support teams for manual resolution, machine learning to categorise and automatically resolve tickets as well as adhoc automations through user-created scripts.

ATR Core is built on React TypeScript with a mix of legacy JavaScript in the codebase. The backend is instead written in Java 8 utilising Spring with a microservices architecture which highly leverages Docker. Due to the large amount of services which tie into the ATR Core platform, the application was quite complex and is broken into multiple different teams focussing on different aspects of the entire ATR platform. Despite Accenture Australia being well-established, MyWizard AiOps is much more modern and agile, feeling more like a startup than a corporate environment. Having the chance to work on ATR Core was extremely valuable and despite not knowing much Java, I was able to quickly and effectively adjust my backend knowledge from Builtview with little friction.