Software developers tend to work in packs. We pool our creativity (and our code) to build software and our strength in numbers helps reduce the risk of errors. The more people who check code and scan for bugs, the cleaner our final product will be. However, this places a premium on effective communication. We will end up accessing, reading, writing and changing the same files over and over again, and it’s vital we keep duplication of work to a minimum.

APIs have become the center of software development, connecting and transferring data across systems and applications. Luckily, testing them can greatly improve the efficiency of your test strategy as a whole, helping you deliver software faster than ever. API testing is an essential part of the software development process, and it’s important to have a team that can work together to create accurate and efficient tests.

Have you ever wanted to see the work of your entire engineering organization in a visualization as it happens? In this article, I'll tell you how I used Github webhooks and Netlify serverless functions, along with a simple Svelte web app, to do just this in my new interactive visualizer tool.

TL;DR: Collaboration between Unity developers and artists can be enhanced by adding some automation tools. For example, using automatic build triggering once a new asset is added allows the artist to see how it looks in the game without bothering the developer, which reduces waiting times and context switching.

Git Sync lets you collaborate with your team on Design Documents that you create in Kong Insomnia. In the last release, we updated the way that Git Sync works for GitHub. We now leverage the OpenID Connect protocol and OAuth2 to make it easier for you to set up Git Sync. Today, we’re excited to announce that we’re bringing that same ease of setup to GitLab repositories as well!

Code review is a widely adopted approach in the world of software development. Having fellow developers check your code (and checking theirs in turn) helps eliminate mistakes, clean the codebase, and share knowledge across the team. But as helpful as it is, code review can still be quite stressful and time consuming.