3 ms·

I read this as "I don't write code all day." I did write code all day, and when I worked in that exact environment, I could not do it. Too many audio distractio

I read this as "I don't write code all day." I did write code all day, and when I worked in that exact environment, I could not do it. Too many audio distractions and distractions in my peripherals. And I was supposed to be doing difficult programming work? I have always gotten my best work done at home, alone, while you "not a code monkey" types chit chat in the office.

scottLobster 9y ago
Depends on the work. I do code all day, but the codebase I work on is massive, fairly old (although some parts have been updated) and everyone in the office has their own area of knowledge. What the code does is also complex enough that it requires specific domain knowledge to code properly (I suppose "expert system" is the correct term), so you can't just throw general computer science at every problem. In that type of environment collaboration among developers is vital, I often leave in the evening not because there's nothing to do but because almost everyone else is gone and I've exhausted the bounds of my knowledge. At that point I can bang my head against a problem for 5 hours or ask the local expert the next morning and get my answer in 5 minutes. But yeah if I was just churning out CRUD apps then I'd probably be more productive on my own.
- RHSeeger 9y ago
  I use slack for those questions and, very rarely, a phone. Collaboration doesn't need to be in person.
  - pmiller2 9y ago
    I consider it rude to Slack someone after they've left, unless it's a critical issue. People shouldn't be "on call" for anything that could wait until morning.
    - tomsthumb 9y ago
      Slack has options to snooze notifications until working hours. We slack each other all the time after hours if someone is on call or just working late, but there's no expectation of answering till the next workday. It's nice because you can get things out there without having to remember.
    - joncampbelldev 9y ago
      This is why slack has configurable notification levels, depending on message content and the channel its sent to.
  - scottLobster 9y ago
    No, but I find it's a lot more fluid when it is. Talking with a white board is much more time-efficient than typing aside from exchanging code/logs/etc, and why go through the trouble of video conference/screen share with all the myriad of things that can go wrong when I can just walk over to someone's desk (or have them walk over to mine) and point at the screen/draw on the white board? Even in individual offices I'd still rather walk over or have people walk over to me. Slack and such have the advantage when it comes to location flexibility/distributed workforce, but for effective active collaboration co-location is still king IMO. At the end of the day you're having a human conversation with someone, no point in adding unnecessary layers. I think too many developers have a "shut up and let me code" mentality that ironically hurts their progress in any collaborative effort.

scottLobster 9y ago

Depends on the work. I do code all day, but the codebase I work on is massive, fairly old (although some parts have been updated) and everyone in the office has their own area of knowledge. What the code does is also complex enough that it requires specific domain knowledge to code properly (I suppose "expert system" is the correct term), so you can't just throw general computer science at every problem. In that type of environment collaboration among developers is vital, I often leave in the evening not because there's nothing to do but because almost everyone else is gone and I've exhausted the bounds of my knowledge. At that point I can bang my head against a problem for 5 hours or ask the local expert the next morning and get my answer in 5 minutes. But yeah if I was just churning out CRUD apps then I'd probably be more productive on my own.

RHSeeger 9y ago
I use slack for those questions and, very rarely, a phone. Collaboration doesn't need to be in person.
- pmiller2 9y ago
  I consider it rude to Slack someone after they've left, unless it's a critical issue. People shouldn't be "on call" for anything that could wait until morning.
  - tomsthumb 9y ago
    Slack has options to snooze notifications until working hours. We slack each other all the time after hours if someone is on call or just working late, but there's no expectation of answering till the next workday. It's nice because you can get things out there without having to remember.
  - joncampbelldev 9y ago
    This is why slack has configurable notification levels, depending on message content and the channel its sent to.
- scottLobster 9y ago
  No, but I find it's a lot more fluid when it is. Talking with a white board is much more time-efficient than typing aside from exchanging code/logs/etc, and why go through the trouble of video conference/screen share with all the myriad of things that can go wrong when I can just walk over to someone's desk (or have them walk over to mine) and point at the screen/draw on the white board? Even in individual offices I'd still rather walk over or have people walk over to me. Slack and such have the advantage when it comes to location flexibility/distributed workforce, but for effective active collaboration co-location is still king IMO. At the end of the day you're having a human conversation with someone, no point in adding unnecessary layers. I think too many developers have a "shut up and let me code" mentality that ironically hurts their progress in any collaborative effort.