Very nice, the finished result looks great.

When you mention maker skillset, what's your top 3 (or is there somewhere I can go to find that)?

use us so they can set and forget.

The benefit of years of hindsight.

Working on it part time means it's taken a while to extricate, but now it's done. Product, codebase and infra simplified, costs lowered.

Redirecting our focus back to enhancing our core features

quickly as possible and get out. The most common feature requests we hear are productivity ones (more filters, faster ways to do something).

The feature was ultimately powerful, but was targeted at a customer who would be in the weeds of the data, and ultimately our customers...

a lot of additional complexity.

At a glance it made sense for our product. Where it failed was in an assumption that our customers would spend large amounts of time exploring theoreticals.

That just isn't the case, our customers want to log in, achieve their objective as...

We had a ton of really useful data coming in, used in the backend, so how can we surface and make it useful to our customers?

So began a large and long effort, that resulted in over a man year of effort, not counting the time spent on it since deployment, a lot of money and...

No-one used it. Classic.

This was built some years pre-acquisition. It took a long time, was somewhat complex, and was a good chunk of our infra costs, even with no-use, given the sheer amount of data ingested.

The initial idea was born from the product, not the customers...

This is interesting, and as someone who struggles with networking in general, I've gone through my career without needing to network so far. I've thought for a while I probably need to change that.

What do you think is the best way to start, and are there any resources you'd recommend for doing so?