Once upon a time at Esri, our codebase conflicted with code written by the JSAPI team - on which we built ArcGIS Dashboards.

In the early days of the JSAPI, it didn't have all the functionality and customization we wanted, so we coded a lot of what we needed ourselves. Unfortunately, as the JSAPI team began working on features we had already implemented ourselves, it broke Dashboards.

Seeing that the API team had made a lot of progress and improved considerably, we began adjusting our codebase to leverage their code to offload our 'boutique' development.

The benefits were enormous. I remember combing through the backlog and closing dozens of bugs that no longer existed because we were importing the API's libraries instead of using our own code. Another added benefit was that we no longer needed to spend as much QA time on these functional areas because our team did not write most of the code!

Moral of the story - Sometimes it makes sense to import functionality instead of ‘rolling your own.’ The benefits can include less bugs, reduced QA requirements, and less stress!


Back to Home
John Solly Profile Picture
John Solly Profile Picture

John Solly

Hi, I'm John, a Software Engineer with a decade of experience building, deploying, and maintaining cloud-native geospatial solutions. I currently serve as a senior software engineer at New Light Technologies (NLT), where I work on a variety of infrastructure and application development projects.

Throughout my career, I've built applications on platforms like Esri and Mapbox while also leveraging open-source GIS technologies such as OpenLayers, GeoServer, and GDAL. This blog is where I share useful articles with the GeoDev community. Check out my portfolio to see my latest work!