3 ms·
This is an interesting problem for any kind of significant contribution made to a big project. To summarize, you seem to have some expectation that you would at
by infogulch 4y ago
This is an interesting problem for any kind of significant contribution made to a big project. To summarize, you seem to have some expectation that you would at least be notified when your past contribution is undergoing changes, with the intention to provide feedback at your discretion. Personally I find this expectation relatable and reasonable, but I'm not exactly sure why.
To counterpoint, it's pretty easy to explain why you might not have been pinged; if every engineer was pinged every time any of the code they wrote changed I expect they'd be buried in notifications. Also, whose responsibility is it to send the notifications? the org's? the engineer making the changes? This seems like a lot of organizational and/or social complexity that has no chance of actually being implemented.
Maybe the solution is that it's the engineer's responsibility to watch the code they care about. This model is better aligned with everyone's goals, but it highlights the lack of tooling to watch for proposed changes and manage your desired notifications.