3 ms·
I think engineers tend to under-estimate how much of their work is communicating with other engineers. Yes, you need that focus time. But running into someone
by pavel_lishin 5y ago
I think engineers tend to under-estimate how much of their work is communicating with other engineers.
Yes, you need that focus time. But running into someone on another team can be very valuable - you might learn that they're solving the same problem, you might learn that they're consuming the same API you're trying to figure out, you might learn that they're planning on working with your team in a few weeks, etc.
- KerrAvon 5y agoSure, but if your company’s productivity depends on these accidental interactions, you’re in serious trouble if you’re as large as Apple is. Apple Park is so large you can roam the halls all day and not run into the people you’re working with on other teams. Many of the teams will be on other campuses anyway. I would argue the benefits of having more of your state in Slack more than make up for “surprise productive watercooler meeting” thing that managers are so hot on. I think I’ve had that interaction maybe twice in 25+ years, and one of those times was just pointless gossip in the end.
- 1minusp 5y agoThe watercooler comment resonates: i keep hearing it as justification to be back in-person and even in cases where i feel i've ha da productive watercooler conversation, it has very rarely resulted in anything crucial or important emerge from it. Businesses have problems that need solving (using technology): it is unlikely that the problem is identified at a watercooler (or other metaphorical equivalents) or the solution is identified in a one hour in-person meeting. One might 'feel' that the outcome from the quickly made decision in the 1-hr meeting was useful, but thats questionable too.
- jsiaajdsdaa 5y agoI shouldn't need to run into another engineer to find out how the fuck to call their API successfully and what I can expect in return.
- ryandrake 5y ago> Yes, you need that focus time. But running into someone on another team can be very valuable - you might learn that they're solving the same problem, you might learn that they're consuming the same API you're trying to figure out, you might learn that they're planning on working with your team in a few weeks, etc. Out of all the companies out there, I'd imagine Apple benefits from this the least. With all the badge-locked doors, literal curtains hiding projects from one another, and internal NDAs preventing one engineer from even disclosing what they are working on with another engineer, cross-pollination of ideas is going to be almost impossible. "Serendipitous conversations" is not something that comes to mind when one thinks about Apple's internal engineering culture.
- bmitc 5y ago> I think engineers tend to under-estimate how much of their work is communicating with other engineers. That's a good point. I would go so far as to say that the majority of what engineers do is communicate with their future selves and other engineers, in that writing software is to use a communication medium. What code you write today will need to be read and understood later. What the code does on the computer is only a part of software.