5 ms·

The most bizarre aspect of this was when Twitter engineers were told to print out their code on paper. There is literally no good reason to do that. At best it

The most bizarre aspect of this was when Twitter engineers were told to print out their code on paper. There is literally no good reason to do that. At best it is staggering incompetence. At worst it is an intentionally pointless and expensive exercise that serves purely as a loyalty test.

kuramitropolis 4y ago
Were they? The article said they were told to "stop printing". As in "stop the presses", perhaps. Still sounds weird, though - maybe the author of the invite is not a native English speaker?
KaoruAoiShiho 4y ago
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…
saxelsen 4y ago
The text messages that were published as part of the suit to close the acquisition showed Musk discussing "return to office" as a way to naturally trim some of the workforce by having the dissatisfied remote workers quit on their own. My take on the paper printing is that it is a similar strategy to get people to quit by themselves, because they think it's stupid.
- FireBeyond 4y ago
  Yup, Jason Calacanis "back of napkin"ing a 30% reduction in workforce based on nothing more than some texts with Musk and an hour or two of bloviating.
- ergocoder 4y ago
  The two aren't similar at all. Commute to work = hours lost every day with drastic lifestyle change. Some people even move further away from the office during pandemic. Printing code on paper = 1 minute of work. Paper and ink are paid by company. It is not really that much of a problem. Actually, this is a punishment on the reviewer. No jump to definition and etc. The printing story is fake. I call it now.
  - catmanjan 4y ago
    Imagine if you printed off your code and ended up with only a few pages of paper you’d fee pretty silly and may quit from embarrassment Just a thought nothing to back up this claim
    - ergocoder 4y ago
      Do you need to print code for that? You can just look at your PR history instead. Also, if you print code, it will contain other people's code because it is likely not only you who code on those files... This story is really too stupid for everyone involved. It is not even good nor efficient for the reviewers. It is like the reviewers are also punished. Too stupid to be true.
    - wiseowise 4y ago
ergocoder 4y ago
> At worst it is an intentionally pointless and expensive exercise that serves purely as a loyalty test. The engineers would have used company's resources. I wouldn't be bothered if I am forced to do this. It is a 1 minute of work to print something. I don't think this part is true. It is likely fake. The source for the print out story is so shaky. Leah Culver tweeted obscurely which is hard to tell whether it is a joke. Casey claims to have screenshots but refuse to show the redacted version of them and end with "subscribe to read".... The code review part might be true but it is not a spicy story.
- activitypea 4y ago
  > It's one minute of work to print something There's a bunch of comments echoing this sentiment, and I'm wondering if something's wrong with me. I'm 27 and haven't printed anything in an office... maybe ever? I've only peripherally noticed HR and office managers constantly struggle with printers. At this point, I'd probably be the one asking my parents how to print something :')
  - ergocoder 4y ago
    At the office like twitter, printers are already set up on your work laptop for you. You basically chooses a printer (there are 10s of them) and click print. Literally a minute of work. Also, you are lucky. Visa employees need to print stuff from time to time for h1b, green card, and citizenship. And you bet it. They print it at work because nobody has printer at home.
    - kweingar 4y ago
      I am pretty confident that most developers would take significantly longer to gather and organize all of their code, make sure that everything is in the correct order for presentation, and print it out on paper. It would probably take me several minutes (if not longer) just to figure out how to display all of my recent changes across several repos, let alone print it without long lines of code getting cut off at the margin. There are several other considerations you’d need to think of as well. Am I just printing diffs? If so, how much context do I need? If not, do I print out whole source files, and do I need to tag the parts that were part of my commit? Should I print 100-page generated files that I technically checked in to source control? I would be very interested in a workflow where all of this can be accomplished by a typical engineer in a minute.
duped 4y ago
It's easier than giving source code access to all the outside staff that are coming in to actually read it. But it doesn't really sound like it's a meaningful review, since "last N days" of work isn't useful without context, and only people on the team can give them that. It's truly bizarre.
agilob 4y ago
>There is literally no good reason to do that Or simply Elon is more unstable than Dogecoin and wanted to show new employees who is the boss, it was a really pathetic power move.
vishnumohandas 4y ago
Maybe this is a way of asking engineers who have zero pages to print to walk out? Or maybe this was to set the expectation that only those who care enough to bend to the whimsies of the new management should stay? Or both?

kuramitropolis 4y ago

Were they? The article said they were told to "stop printing". As in "stop the presses", perhaps. Still sounds weird, though - maybe the author of the invite is not a native English speaker?

KaoruAoiShiho 4y ago

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…

saxelsen 4y ago

The text messages that were published as part of the suit to close the acquisition showed Musk discussing "return to office" as a way to naturally trim some of the workforce by having the dissatisfied remote workers quit on their own. My take on the paper printing is that it is a similar strategy to get people to quit by themselves, because they think it's stupid.

FireBeyond 4y ago
Yup, Jason Calacanis "back of napkin"ing a 30% reduction in workforce based on nothing more than some texts with Musk and an hour or two of bloviating.
ergocoder 4y ago
The two aren't similar at all. Commute to work = hours lost every day with drastic lifestyle change. Some people even move further away from the office during pandemic. Printing code on paper = 1 minute of work. Paper and ink are paid by company. It is not really that much of a problem. Actually, this is a punishment on the reviewer. No jump to definition and etc. The printing story is fake. I call it now.
- catmanjan 4y ago
  Imagine if you printed off your code and ended up with only a few pages of paper you’d fee pretty silly and may quit from embarrassment Just a thought nothing to back up this claim
  - ergocoder 4y ago
    Do you need to print code for that? You can just look at your PR history instead. Also, if you print code, it will contain other people's code because it is likely not only you who code on those files... This story is really too stupid for everyone involved. It is not even good nor efficient for the reviewers. It is like the reviewers are also punished. Too stupid to be true.
  - wiseowise 4y ago

ergocoder 4y ago

> At worst it is an intentionally pointless and expensive exercise that serves purely as a loyalty test. The engineers would have used company's resources. I wouldn't be bothered if I am forced to do this. It is a 1 minute of work to print something. I don't think this part is true. It is likely fake. The source for the print out story is so shaky. Leah Culver tweeted obscurely which is hard to tell whether it is a joke. Casey claims to have screenshots but refuse to show the redacted version of them and end with "subscribe to read".... The code review part might be true but it is not a spicy story.

activitypea 4y ago
> It's one minute of work to print something There's a bunch of comments echoing this sentiment, and I'm wondering if something's wrong with me. I'm 27 and haven't printed anything in an office... maybe ever? I've only peripherally noticed HR and office managers constantly struggle with printers. At this point, I'd probably be the one asking my parents how to print something :')
- ergocoder 4y ago
  At the office like twitter, printers are already set up on your work laptop for you. You basically chooses a printer (there are 10s of them) and click print. Literally a minute of work. Also, you are lucky. Visa employees need to print stuff from time to time for h1b, green card, and citizenship. And you bet it. They print it at work because nobody has printer at home.
  - kweingar 4y ago
    I am pretty confident that most developers would take significantly longer to gather and organize all of their code, make sure that everything is in the correct order for presentation, and print it out on paper. It would probably take me several minutes (if not longer) just to figure out how to display all of my recent changes across several repos, let alone print it without long lines of code getting cut off at the margin. There are several other considerations you’d need to think of as well. Am I just printing diffs? If so, how much context do I need? If not, do I print out whole source files, and do I need to tag the parts that were part of my commit? Should I print 100-page generated files that I technically checked in to source control? I would be very interested in a workflow where all of this can be accomplished by a typical engineer in a minute.

duped 4y ago

It's easier than giving source code access to all the outside staff that are coming in to actually read it. But it doesn't really sound like it's a meaningful review, since "last N days" of work isn't useful without context, and only people on the team can give them that. It's truly bizarre.

agilob 4y ago

>There is literally no good reason to do that Or simply Elon is more unstable than Dogecoin and wanted to show new employees who is the boss, it was a really pathetic power move.

vishnumohandas 4y ago

Maybe this is a way of asking engineers who have zero pages to print to walk out? Or maybe this was to set the expectation that only those who care enough to bend to the whimsies of the new management should stay? Or both?