3 ms·
Plus someone who is doing dev work at night is more likely to be working alone and they won't have an office full of coworkers to ask before they Google. That's
by onion2k 10y ago
Plus someone who is doing dev work at night is more likely to be working alone and they won't have an office full of coworkers to ask before they Google. That's bound to skew the results a little.
- matt4077 10y agoUnless there are some secret Sharepoint Nightclubs or Subversive Subversion Speakeasies I have yet to find, that would affect all languages, and couldn't explain these day/night patterns.
- ikeyany 10y agoI was thinking that some languages like C++ take a lot longer between "tests" (e.g. compile times) and are thus more prone to be worked on at odd times.
- soheil 10y agoI always feel guilty asking questions from coworkers when the answer literally takes me a fraction of the time if I Googled it and opened the first SO link.
- falcolas 10y agoIMO, if it's something that I'm asking a coworker about, SO isn't going to have an easy (or correct) answer. For example, I am attempting to use a namespaced library installed with Pip in my Lambda function. It doesn't work - can't import the library. Google gives a bunch of noise. SO gives a bunch of noise. The solution? Asked a coworker, got an answer back immediately. Import the 'site' package, and set up the current working directory as a site directory. This makes the library .pth files work properly.
- Jtsummers 10y agoNo reason to feel guilty. Questions are good, and it keeps communications within the team going. Silence is worse. As I said in a cousin comment, it also helps your office/team discover what knowledge is lacking. I used git there, but linux (unix in general) is another example in my office. So many of my colleagues have only done Windows-based applications, or embedded (running a one-off RTOS or an off-the-shelf RTOS). We've been moving workload to embedded linux (for reasons), along with moving some development work to linux (because of tooling available there). If everyone googled it, they may get their answers. But no one would realize that it was a systemic issue because there's no communication.
- phowat 10y agoI'd hate to be your coworker. You ought to Google your issues before interrupting someone else's flow.
- Jtsummers 10y agoIf I wasn't willing to answer my coworkers questions, I'd consider myself a bad colleague. It would be annoying if people came up to my desk constantly, but they usually send out an email or IM [EDIT] or catch me away from the desk, like in the break room. It's less distracting from a flow perspective (potentially not distracting if those notifications aren't immediately visible). Related, without getting these questions from colleagues I can't know, no one can know, what institutional knowledge we're lacking. I was surprised (sort of) by how deficient my coworkers were with git, until I realized I was one of 3 folks here who do any hobby programming and so had used git on my own time before we adopted it internally on some projects. I'm glad I know that they don't know, because we were able to put together a training course of sorts to bring them up to speed. This has helped with new hires as well. This makes us, as an office, much more effective than if we'd left it to individuals to google for answers (though it may be quicker in the short term, it doesn't help in the long term because they still don't understand the problems they face and the systems they use).
- kbenson 10y agoBeing willing to answer questions is not the same as being quick to ask them of people that might otherwise be engaged. The first shows patience and respect that the other person is not wasting your time. The latter shows impatience and disrespect for other people's time. Coworkers and friends are a resource to be cherished, not abused.
- onion2k 10y agoThat depends on the problem. I wouldn't want 5 different developers to write 5 different solutions to the same problem only to have 4 of them rejected in a code review because they should have used the first dev's solution, so if someone has an problem they need to solve with code it's far better to talk about it first. Obviously this only really applies if you work on moderately complicated projects in medium-sized to large teams though. If you work on smaller projects you can know the whole codebase so it doesn't really apply. More generally, I'd hate to work in an office where I have to be wary of interrupting the people. That sort of environment is toxic to working in a team. I encourage developers who want to work in a quiet place without being bothered to go somewhere outside of the main office.