3 ms·
For what it's worth, it bears keeping in mind that the tool that you are likely using does not report activity on any parts of the codebase that you personally
by dodobirdlord 8y ago
For what it's worth, it bears keeping in mind that the tool that you are likely using does not report activity on any parts of the codebase that you personally don't have permission to view. Also, many teams keep codebases out of the standard code store, either in alternative self-managed version control systems or on GitHub.
- amzn_throwaway7 8y agoI had considered that. This is common in AWS or Lab126, but I've never seen that be the case in Retail. Edit: Missed the part about permissions, that's totally possible, but at least in publicly visible contributions, he is way behind his teammates.
- canttestthis 8y agoThe more I hear about Retail the more it seems like its a bad place to be.
- dodobirdlord 8y agoThere are jokes about "retiring to retail" among more senior engineers in AWS. There are a lot of older low-activity codebases where the pace is slower and someone senior can essentially retire-in-place. There's also a massive diversity of teams in retail. But yea, as far as I can tell most everyone would rather work in AWS, and nobody in AWS seems to seriously consider the possibility of transferring to a team in retail.
- amzn-sdethrow 8y agoCode contributions are public even if you don't have commit permissions on team packages. You can look at anyone's code reviews. Caveat being secret projects. However that's not the case here.