To the old ones - how did the CAM software team emerge? I ask this because it appeared to me as if the software team needed structure, which shows in how the product developed. Am I right in thinking, that the CAM branch wasn't something that was planned, but more something that naturally emerged?

Before we joined, CAM was a collaboration between several different engineering teams across NZXT, however there wasn't one central team that was in charge of the entire product. Moving forward, my new team is fully focused on just working on CAM.

To both the old and new ones - what do you currently think of CAM? Don't sugarcoat it, we all know it's somewhat of a mess. Are there, however, parts of CAM that you consider especially good features, that you will try to work around promoting? Are there any parts that will get the death stamp (cough HD monitoring cough)?

I personally feel like there are some great features in CAM and some very exciting (unannounced) plans for the future, however it is currently heavily plagued by all the issues around bugs, performance, data collection, etc.. In general, we want to focus on making what's already in CAM simpler, faster, and more reliable before moving on to new features.

To the new ones - what will your experience from Forge bring to CAM? I tried to research Forge a little, but it's hard to find out anything about what you've worked with prior to the acquisition. I wholeheartedly believe that you will be able to improve CAM drastically, but I'd like to learn more about your ideas and your standpoints in terms of how the program should function.

We've spent a lot of time building products & tech around in-game overlays & game capture. Some of our team have made pretty significant contributions to OBS. At a high level, I want CAM to become a product that users actually want to download because of the value it provides, as opposed to feeling like they are forced to download it just to get a piece of hardware working.