We all have our biases when it comes to this sort of thing, I think that we probably largely agree here but I’m not willing to say that it’s a slam dunk. Here’s why not:
Assumption 1: your tenure has some effect when it comes to understanding glowforge’s specific org structure and processes.
A lot of us here are long-tenured technical types, plenty of time to get entrenched in our ways of thinking. It’s possible that longer tenure is even a bit of a disadvantage when it comes to innovation.
Assumption 2: this is a frivolous thing.
Not our call, and definitely is in the eye of the beholder. It comes down the ROI, where the I is “effort” and the R is impact. We don’t know how difficult it would be to do this nor how many users (or the specific demographic of said users) would be affected. It’s possible that this would be more impactful than it might seem.
A counter or two, where it costs little to do this. Both scenarios are theoretical but also both quite possible:
Scenario 1: Glowforge opens up an api to the boxy developers. They create a plugin and ask Glowforge for approval to use it. Very few developer hours spent at GF.
Scenario 2: (again thisnis theoretical) GF has a dedicated plugin developer on staff who is tasked with this sort of integration and has some spare cycles at the moment. Adding this project to the docket would allow for better utilization of her time, thus increasing GF’s efficiency.
I’m just saying that there are lots of cases where this sort of work might not impact the rest of the work at GF, and given that we have essentially no insight into their internal processes or staff assignments it’s a pretty big leap to categorically rule it out.