3 ms·

Nah paper is still more efficient than computers in quick meetings. You can imagine many seconds being wasted if they were on a laptop and the engineer needs to

Nah paper is still more efficient than computers in quick meetings. You can imagine many seconds being wasted if they were on a laptop and the engineer needs to find his files. Paper the UX is perfect and instant.

kweingar 4y ago
Paper is instant until you say “can you show me that part of the code that handles X” or “where is this function defined” and then it’s multiple orders of magnitudes slower. (Editing to say, you could also just tell the engineers “hey make sure your code is pulled up and ready to go before the meeting starts”)
NegativeK 4y ago
"Please send us links to your changes before the meeting begins." And display them on a large screen. I don't think it's really relevant, though. The entire situation is cruel and silly.
- wittycardio 4y ago
  Elon fan brain is a debilitating condition
govg 4y ago
How do you search, tag, jump to code definitions, look up libraries referenced if it is in paper?
seadan83 4y ago
I very recently reacted the same copy/pasted code that was in in 7 files, each one had 6 touch points of 5 lines each, and the touch points were 50-300 lines as part. Would be a lot of paper for what had been a 30 minute exercise. I cantquite how to picture going over that diff on paper. The time wasted doing so seems sad, as do the natural resource waste (which tends to make me think the guy got into electric cars because it was cool and had an open market opportunity rather than ecological reasons - but that is a very random aside)
jen20 4y ago
Unclear to me why this is being downvoted. I always read code on paper, it’s easier to annotate. If jumping around a codebase is hard on paper, it’s a good indication that the code does not consist of cohesive modules. Sadly these days most people no longer adhere to 80 column limits, so it has to be printed in landscape. In the worst cases, landscape on legal paper…

kweingar 4y ago

Paper is instant until you say “can you show me that part of the code that handles X” or “where is this function defined” and then it’s multiple orders of magnitudes slower. (Editing to say, you could also just tell the engineers “hey make sure your code is pulled up and ready to go before the meeting starts”)

NegativeK 4y ago

"Please send us links to your changes before the meeting begins." And display them on a large screen. I don't think it's really relevant, though. The entire situation is cruel and silly.

wittycardio 4y ago
Elon fan brain is a debilitating condition

govg 4y ago

How do you search, tag, jump to code definitions, look up libraries referenced if it is in paper?

seadan83 4y ago

I very recently reacted the same copy/pasted code that was in in 7 files, each one had 6 touch points of 5 lines each, and the touch points were 50-300 lines as part. Would be a lot of paper for what had been a 30 minute exercise. I cantquite how to picture going over that diff on paper. The time wasted doing so seems sad, as do the natural resource waste (which tends to make me think the guy got into electric cars because it was cool and had an open market opportunity rather than ecological reasons - but that is a very random aside)

jen20 4y ago

Unclear to me why this is being downvoted. I always read code on paper, it’s easier to annotate. If jumping around a codebase is hard on paper, it’s a good indication that the code does not consist of cohesive modules. Sadly these days most people no longer adhere to 80 column limits, so it has to be printed in landscape. In the worst cases, landscape on legal paper…