6 ms·
> in my team culture it’s not frowned upon to “snoop behind” people writing code. Whenever I sensed something interesting going on, I’d roll around and watch wh
by OJFord 7y ago
> in my team culture it’s not frowned upon to “snoop behind” people writing code. Whenever I sensed something interesting going on, I’d roll around and watch what was happening.
Agh, I'd hate that. In fact if anything interesting had been going on on my screen it would immediately stop, no way I could work with someone watching.
I struggle enough at desks with my back to a door or where people walk by, just can't stop myself from being distracted and looking.
(It's not that I'm not working, or otherwise doing anything I shouldn't be, it's just.. distracting is the best word I have. It's not where I'd sit in a restaurant, and I've despised not having a choice but to sit at such a desk at work.)
- rbavocadotree 7y agoIt's also strange in that I don't think I'd get very much out of simply watching anyone work, unless they were also giving live commentary or something.
- nitrogen 7y agoThere was an article posted on HN a while back that claimed that the best way for beginners to learn a new skill is to watch an expert just work, without any commentary or explanation. I tried finding a link, but couldn't come up with working search terms on DDG, Goog, or HN.
- dillonmckay 7y agoThis was an interesting article about the trend towards robotic surgery and the new methods to gain experience in such an environment. https://hbr.org/ideacast/2019/08/how-robots-and-ai-are-changing-job-training https://hbr.org/ideacast/2019/08/how-robots-and-ai-are-chang...
- tc7 7y agoReally seems like I should be better at golf, then. :tear
- Bekwnn 7y agoCasey Muratori's and Jonathan Blow's streams are pretty great in this regard. Both do low-level gamedev.
- arkh 7y agoThat's where pair programming can shine: when I see a junior who need help, I'll ask if they don't mind me coming around and helping. Just asking the right questions and guiding them to find a solution to their problem usually do the trick. And it helps me see the pain points of our code, documentation and specs.
- ken 7y agoI've read that in feng shui what you describe is called the "command position". I'm not able to work with my back to a crowd. That's a recipe for anxiety. I quit a company when they moved my desk so my back was to a hallway, and refused to compromise on this issue in any way.
- mikekchar 7y agoIf it happens again, I've been told that having a mirror on your desk so that you can see what's going on behind you can help a lot.
- saagarjha 7y agoOr if your monitor is one of those glossy ones, just glance into a darker part.
- cortesoft 7y agoWouldn't that cause even more distraction as you see all the people walking behind you?
- mikekchar 7y agoApparently (it's not something I suffer from), people who prefer to be facing the aisle tend to glance out at people from time to time, which makes them feel at ease. Having the people at their back makes them uncomfortable because they can't keep tabs on it. For some people, this is apparently so bad that even if they are in an individual office they need to have a window, or keep the door open.
- inimino 7y agoOr if putting a mirror on your desk is the best resolution your employer can offer, run away screaming...
- JohnBooty 7y agoI tried this and it absolutely did not help. In a "normal" situation where your desk faces the rest of the room, you would become aware (in an "ambient" way) of people wandering into your field of view. But with your back to the room/hallway/whatever, you need to explicitly scan the mirror (sort of like polling, in computer terms) with frequency to know if somebody is approaching. It's like trying to work while also focused on a video playing in a desktop window or something. Of course, as with anything, some people are not bothered by this. (And, of course, some of those people are fooling themselves into thinking there's zero impact on their focus/productivity)
- bronxbomber92 7y agoWe have a similar culture on my team. When I was a junior engineer, being able to poke my head into any open office that sounded like it had an interesting conversation going on was really an invaluable way of learning.
- losteric 7y agoListening to or participating in technical conversations is just regular business, but the proposal of looking over someone's shoulder sounds very distracting and unnecessary...
- pkrotich 7y agoSo how do you handle pair programming? It’s almost the same thing to me.
- marcosdumay 7y agoI don't. I could never really pair programming, even in school. Interestingly, I can share my screen with people that have different tasks than mine. I just can't make it work when both people have the same state of mind.
- bryanrasmussen 7y agopair programming is really a forced socializing in a field where a lot of people have trouble socializing, never really understood how it got as far as it did.
- neilv 7y agoPair programming seems to be social in some ways, but I could imagine two programmers with very little social awareness or self-consciousness being able to find a cadence for pair-programming.
- TeMPOraL 7y agoPair programming is an anti-procrastination trick that works by setting two people in a situation where both are afraid to lose face by trying to goof off. This works, but builds up anxiety.
- larzang 7y agoInteraction between devs is unavoidable, at the code review stage if not sooner. Pair programming provides tighter feedback loops and helps get things done quicker than playing CR tennis after a lot of hours have been sunk into something.
- filoleg 7y agoDepends on the definition of pair programming imo. Bad definition (the one I encountered in school): two people of about the same skill level sitting at one computer and programming together. I hated it, akin to my hate of backseat drivers. Good definition (the one I encountered at my workplace): as a junior engineer, I was tasked with implementing this tricky caching thing in one of our systems that I had zero previous experience with. One of our senior engineers was tasked with helping me with that. I would implement as much as I could myself, and when I get stuck, the senior would either give me hints on how to get unstuck or program some parts himself while explaining to me how and why he did things a certain way. This helped me out tremendously in my skill development and got me running confidently in our codebase really quickly.
- harrisonjackson 7y agoFor me, it depends on who is creeping. A junior engineer, I'd probably pull them up and start explaining what is going on. A fellow senior engineer I'd probably take a welcome break and ask them to grab a coffee - the only reason they'd be lurking lol. If it is a PM or someone else it might put me on edge - likely because they wouldn't have the context to understand what I was working on and if they didn't say anything I'd just be wondering what they wanted...
- rakamotog 7y agoThe only time I (a PM) would do this is when you are working on validation messages / error messages / user facing text.
- afarrell 7y agoError message phrasing is really very important, but it’s probably better to have that refined in code review or to have some explicit step for it.
- dotancohen 7y agoError message phrasing should not be in code. It should be in localization files, even for the default language, and not require a developer to modify.
- SamuelAdams 7y agoDepends on the requirements. I've had many internal-only applications only require one language: English. At that point you can hard code many things, which skips the loading other files, checking different languages, etc.
- OJFord 7y agoI'd still rather the exact wording isn't in code, personally: get_msg('fail_add_address') vs. 'I\'m sorry, we\'ve been unable to add the address %s at this time,' \ ' please try again later.' (... but that's an ideal I have without ever having worked with it, so what do I know, and ymmv, etc.)
- neilv 7y agoMy 'favorite' (it seems funnier, with some distance) was when I arrived at a new job as a Research Scientist in a university lab, to execute on a project of a couple PIs... I immediately find out I'm being jammed into this packed, messy, mouse-infested, nest-like office with ~5 grad students (working on other things, not collaborating). With a sense of dread, I sit down at my assigned kidney bean-shaped desk in the middle, someone sits down at their desk that's pushed up against mine... and he's looking at a diagonal of the side/front of my face, from just a few feet away, and seems fine with that. He's a nice person, and I understand not all people are wired to realize this is a problem for some others, but this is reallocating too many IQ points, away from designing and coding and writing, to social interaction/awareness modes. Plus the other distractions. There was no way I could immerse enough in some of the work, and stay immersed. (I'm happy to do group brainstorming and problem-solving around a whiteboard, etc., as well as to mentor. But most of my time is spent programming, designing, and writing, which I usually do best solo and focused. Nor do I want to be working all day, every day, almost breathing down each others' necks. For many introverts, and people who like to focus fully on a problem, being packed up against other people is taxing, not energizing.) In the end, I brought in a laptop from home, and worked every day, cafe-style from the lunch tables in the elevator lobby area of our building floor. Which was suboptimal, but something I could make work. People would come over when necessary, but we weren't sitting on each other's laps. I also got good at quickly cleaning lunch tables without interrupting my thoughts. When my PI renewed my appointment another year, I declined, mainly for a different reason, but the physical work environment made the decision easier.
- scarejunba 7y agoHow interesting! I thoroughly enjoy it. Oddly though, I always hated performing an instrument in front of someone else. I can only play for myself :D
- sharadov 7y agoSometimes it's just working collaboratively, creating an atmosphere where you encourage the "junior folks" to ask questions without judgment. Also whenever you stumble on something interesting you share. I miss this aspect of my current job, am 100% remote and miss those discussions.
- OJFord 7y agoI am a 'junior folk'; I don't have a problem collaborating, the people walking behind me didn't care what was on my screen and many of them wouldn't have understood if they'd looked (different roles) - it's just the fact that I can feel people there that distracts me and compels me to look, even though I 'know' they're not watching, couldn't care less, and will be gone in a second.
- kemiller2002 7y agoI completely agree. Most of the time when I code I am working through problems. It's unrefined and messy until I'm done. You want me to show you what I did and explain how I got there when I'm done? Great! I'd love to but not when I'm in the middle of it. I rarely get things correct the first time, and I would like to not have to be self conscience about people judging how I think.