Maximizing detection and swift resolution of bugs in IguanaX

The bottleneck we are focused on is how to most swiftly debug the product. It’s all to do with the flow of feedback about it. We’ve been doing extremely well on this target - 10.1.90 is extremely solid.

One of best tools we have for this is Cascading Communication and making sure everyone realizes this is our Thematic Goal.

The most important bugs are found from using IguanaX to solve real problems. It’s much more effective than clicking around.

So how do we get people to use IguanaX in to solve real problems and then collect the information in the best way to give focused attention on the most important issues so that development team can solve those problems in a time efficient way?

Automated Crash Reporting has been massively helpful in giving us fast, timely information on where significant bugs and being able to fix them quickly. Also Memory Corruption Detection Tools running address sanitizer on a Linux ARM instance with our Build system .

That means porting our internal interfaces over to it and:

All future professional service projects need to be delivered on IguanaX.

IguanaX is our default download now

IguanaX is the only solution we will license to new customers

We can deliver high availability solutions on IguanaX today

What are other ways to do it?

Build Adapters to really push the product. We need to get at least one person working on this immediately because of this. Lianne is on board on this role now.

Once again this really helps to establish the workflows that the product needs to be used with. Staff being trained with the product really helps to find issues.

We could consider to have someone dedicated the role of internal trainer. We already have a dedicated person working exclusively on documenting the product.

This is a process which is evolving - it’s a conversation as to what the next bottleneck is and how we can resolve it.