Event JSON
{
"id": "feebf3f8408cfb948ebef77d6c8581a5890f6f1c64ff306c2de0a8d4349b4685",
"pubkey": "dd407bfb6eb412332cf09b0f30fafe1826f6d6cdd986342adba543b25b6ab11d",
"created_at": 1702047081,
"kind": 1,
"tags": [
[
"p",
"87c34046659925388547bccdb64a863a9da239f1c303f65a4d1ce7c001d5cae3",
"wss://relay.mostr.pub"
],
[
"p",
"2b9c6c28bce249a1ef28497a2ec6f6c01bc7be0721124b8ce7da3e1592080c57",
"wss://relay.mostr.pub"
],
[
"e",
"8eb00f5184b2327a8fb5c072b6143263c7b9968a52ba97d63724987bce8bd49a",
"wss://relay.mostr.pub",
"reply"
],
[
"proxy",
"https://sfba.social/users/soaproot/statuses/111545357544027349",
"activitypub"
]
],
"content": "nostr:npub1slp5q3n9nyjn3p28hnxmvj5x82w6yw03cvplvkjdrnnuqqw4et3ste4xfq Where I work it is the overall policy that teams have to be required reviewers on code they own. The result is sort of similar to the dynamic you describe except that the teams (often) are trying to get out of reviewing code just as much as code authors are (sometimes). trying to get out of attempting to get reviews out of people.",
"sig": "13151c51b0818e70480d0bb398d36077151d4397889358f84d0d48789c6d9ca5149e66221275543e998608864d3e062f15c4213716ee262fb6091a1b7f29c267"
}
