I think it is more the point that the users for his job were external developers. The role is inherently user facing and user focused. I don’t think anyone was trying to say he wasn’t a developer just that his job wasn’t to directly develop products
Yeah, I guess I just wanted to add that because of the way that quote was cut at the end, made me believe that the person quoting me thought Osmani "isn't a developer".
In 3.1, rejecting (R) fraudulent (F) goods resulting in 0 for the seller is a strong assumption. There are all kinds of possible negatives (typically risks of legal fees) for storage costs of fraudulent goods in the game of hot potato. It might be worth your time to look into the literature a bit more.
The paper was aimed at a broader audience, which is why it simplifies some concepts and makes certain assumptions. While there are potential drawbacks to consider, it’s reasonable to assume that a seller of a fraudulent item gains nothing if the item gets rejected. In that scenario, their goal of making money wouldn’t be achieved, and any additional losses wouldn’t significantly impact the protocol. In fact it would deter fraudsters. I'd love to hear more thoughts on this!
Thanks for the share, but I'm having a hard time understanding this.
On step 2, it's only jailing VS Code. Shouldn't it also jail the Git repo you're working on (and disable `git push` somehow), as well as all the env libs?
Also, isn't the point of this to auto approve everything?
reply