4 ms·
the gratitude thing is kinda fun. I imagine that managers treat that as a "positive only" indicator (lack of gratitude markers should not be counted as a negati
by rtpg 4y ago
the gratitude thing is kinda fun. I imagine that managers treat that as a "positive only" indicator (lack of gratitude markers should not be counted as a negative, but a lot of them should be counted as a positive), since it's dependent on coworkers who do that kind of thing.
In a previous job I would always offer "e-bux" for fixes. I was half tempted to write a quick backend to track these e-bux, but gamifying that sort of stuff has its own consequences as well...
> If there is an issue with a single deploy, it stops the whole company from shipping changes.
This definitely feels odd to me. Monorepo shouldn't mean mono-artifact! Perhaps this is more theoretical/one point, but if Stripe engineers feel this and this person felt this after less than a year... Bazel is nice y'all. (EDIT: I'm being too harsh here, CD in particular probably makes the calculus on rollouts very tricky)
- cicdmonorepo 4y ago> If there is an issue with a single deploy, it stops the whole company from shipping changes. I don't agree with this characterization. There is a way to 'lock' an entire repo from deploys, but it's not very frequently used. Single-service deploy blocks are common (if an autodeploy fails, or a team is aware of an issue and actively fixing it). Stripe uses Bazel heavily. > there was a project well underway to pull some core product / business functions into specific repos This quote from the post is also not true to my knowledge: new repos are not allowed and teams are actively working to migrate small repos into the monorepo(s).
- rtpg 4y agoThanks for the feedback, and very glad to hear that there's a distinction going on between merging and deploying.
- ketchupdebugger 4y ago> the gratitude thing is kinda fun. I imagine that managers treat that as a "positive only" indicator (lack of gratitude markers should not be counted as a negative, but a lot of them should be counted as a positive), since it's dependent on coworkers who do that kind of thing. Depending on how it's done. I've seen similar systems where it became an additional metric to measure an engineer. Engineers became upset if they helped a coworker but did not receive any gratitude. (not receiving gratitude means that the help is not documented, so the helping engineer can't claim it during perf reviews)
- clintonb 4y agoPlus-plus-bot does not impact reviews. It’s just a nice way to show gratitude publicly. Folks can use a feedback form to leave review-impacting feedback that is actually delivered to the manager.