News for hackers. Stuff that matters.
Re:Things I Learnt from a Senior Software Engineer by OJFord on Sunday August 25, 2019 @07:57PM (#20796479)
> 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.)

Re:Things I Learnt from a Senior Software Engineer by neilv on Monday August 26, 2019 @12:17AM (#20797428)
My '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.

Re:Things I Learnt from a Senior Software Engineer by harrisonjackson on Sunday August 25, 2019 @10:12PM (#20796978)
For 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...
Re:Things I Learnt from a Senior Software Engineer by Scarblac on Monday August 26, 2019 @03:56AM (#20798124)
So in all three cases, your focus is gone and what you were doing has stopped.
Re:Things I Learnt from a Senior Software Engineer by SamuelAdams on Monday August 26, 2019 @08:28AM (#20799259)
Eh, not really. Not all engineers work in high-pressure environments where focus is essential. Some senior engineers really enjoy teaching others. Some of the best mentors I've learned from were the ones who were happy to spend an entire Friday afternoon showing me how they would solve an interesting problem.
Re:Things I Learnt from a Senior Software Engineer by aspaceman on Monday August 26, 2019 @05:10AM (#20798354)
Helping a junior and maintaining relationships with your fellow seniors is a part of the job too.
Re:Things I Learnt from a Senior Software Engineer by monsieurbanana on Monday August 26, 2019 @08:13AM (#20799155)
But surely there's ways of doing that without making people lose their focus.
Re:Things I Learnt from a Senior Software Engineer by nickpsecurity on Monday August 26, 2019 @10:25AM (#20800093)
Such as assigning times for focused vs collaborative work.
Re:Things I Learnt from a Senior Software Engineer by bochoh on Monday August 26, 2019 @10:38AM (#20800219)
Yes, a vibrant meme room in a "management expects you to respond to business issues in this room" channel on <slack|teams|etc>
Re:Things I Learnt from a Senior Software Engineer by SolaceQuantum on Monday August 26, 2019 @09:20AM (#20799624)
Actually, is there?
Re:Things I Learnt from a Senior Software Engineer by OJFord on Monday August 26, 2019 @12:59PM (#20801501)
Yes, you pick the moment (much) better than wandering over to peek over their shoulder when 'something interesting is going on'. IMO that's exactly when you don't, ask them about it later.

To borrow from that cringeworthy scene in The Social Network: He's wired in!

Re:Things I Learnt from a Senior Software Engineer by chasd00 on Monday August 26, 2019 @03:04PM (#20802679)
also, imo explaining something complex to someone junior often leads to answers to other questions. For some reason, talking through code out loud helps the problem solving process.
Re:Things I Learnt from a Senior Software Engineer by harrisonjackson on Monday August 26, 2019 @07:20PM (#20804700)
Which is _okay_ as long as it doesn't happen too often. I work remotely now, but most offices have conference rooms or quiet spaces or respected headphones on policies for when you need headsdown time. If there's no way to signal that you are busy, then that's probably a separate issue than the 3 cases here.
Re:Things I Learnt from a Senior Software Engineer by inflatableDodo on Monday August 26, 2019 @01:34PM (#20801876)
The first one, less so. Explaining what you are doing to someone (as long as they get the basics) can be a great way to cement your understanding of what you are currently doing.
Re:Things I Learnt from a Senior Software Engineer by rakamotog on Sunday August 25, 2019 @11:47PM (#20797334)
The only time I (a PM) would do this is when you are working on validation messages / error messages / user facing text.
Re:Things I Learnt from a Senior Software Engineer by afarrell on Monday August 26, 2019 @02:53AM (#20797944)
Error 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.
Re:Things I Learnt from a Senior Software Engineer by dotancohen on Monday August 26, 2019 @04:31AM (#20798227)
Error 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.
Re:Things I Learnt from a Senior Software Engineer by SamuelAdams on Monday August 26, 2019 @08:30AM (#20799275)
Depends 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.
Re:Things I Learnt from a Senior Software Engineer by OJFord on Monday August 26, 2019 @01:03PM (#20801554)
I'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.)
Re:Things I Learnt from a Senior Software Engineer by rakamotog on Tuesday August 27, 2019 @09:54AM (#20809570)
And what is this localization file called? We do not have a system where non dev can commit any change in our product.

We do have a constants file which has all the messages but a PM does not access to code/commit and has to go via a Dev.

Re:Things I Learnt from a Senior Software Engineer by rmetzler on Monday August 26, 2019 @11:43AM (#20800751)
It really depends on who‘s the target group. I hate localization in Developer Tools etc, because googling it is harder and a lot of times English is just easier to understand. It’s different for a shopping site.
Re:Things I Learnt from a Senior Software Engineer by high_derivative on Monday August 26, 2019 @07:29AM (#20798917)
How would you know this without entering their personal space?
Re:Things I Learnt from a Senior Software Engineer by ken on Sunday August 25, 2019 @09:05PM (#20796771)
I'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.

Re:Things I Learnt from a Senior Software Engineer by greyhair on Monday August 26, 2019 @08:23AM (#20799207)
This is why, when people complain about cubicles, I tell them how much better a cubicle is than open floor plan.

I have had private offices, two person offices, cubicles, and once in a bull pen with a glass wall. (we called it 'the fish bowl').

Private office comes in first! Cubicle (as long as the walls are at least five feet) comes in a close second.

Open floor plan (or a bull pen) comes in far far far last.

Re:Things I Learnt from a Senior Software Engineer by cr0sh on Monday August 26, 2019 @12:44PM (#20801326)
The best time I ever had was in a "bull pen" situation (our team at the time called it alternatively the "oven" or the "barn"). It was at a new job, doing something new to me (server automation), and our team consisted of one of their senior devs, myself, and two really "green" new guys who were also hired along with me. One was new in the sense that they had a fresh comp-sci degree but had never worked in the field before, and the other had worked in the field, but never at an employer (only as a remote contractor).

The place had no open desks for us, so they decided to turn the small conference room (we had interviewed in) into our shared "office". Trouble was, it had no A/C vent in it. Hence, with four people and four computers and four monitors - it became "the oven" (there were other reasons we named it what we did, but they aren't relevant here).

But the camaraderie we built in a short amount of time as a team was beyond anything I had experienced before. We'd keep the lights off, a fan running, and a spotify playlist cranking out weird music (our lead controlled it, he was younger than me by many years - as an older person just turning 40 - his choice of music was both odd, and interesting - I'm glad for this, as I discovered new music genres I never knew existed - like Pirate Metal - yes, Alestorm was one such band).

Eventually we got a portable A/C unit, which made things more tolerable.

Ultimately, though, that room helped to form a team that cranked out some interesting code in a very short period, which I think helped to lead the company to be sold to a larger competitor about a year or so later. I ended up leaving the company (the new owners did a "rehiring" process in which they offered me my position at a 25% pay cut - yeah, sure, let me get right on that).

Re:Things I Learnt from a Senior Software Engineer by weaksauce on Monday August 26, 2019 @10:48AM (#20800303)
Cubes are almost always back to the people coming so it’s anxiety inducing to me. An office with you facing the door is the only way for peace in my mind.
Re:Things I Learnt from a Senior Software Engineer by mikekchar on Sunday August 25, 2019 @10:08PM (#20796959)
If 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.
Re:Things I Learnt from a Senior Software Engineer by inimino on Sunday August 25, 2019 @11:01PM (#20797145)
Or if putting a mirror on your desk is the best resolution your employer can offer, run away screaming...
Re:Things I Learnt from a Senior Software Engineer by JohnBooty on Monday August 26, 2019 @12:29AM (#20797471)
I 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)

Re:Things I Learnt from a Senior Software Engineer by IloveHN84 on Monday August 26, 2019 @12:54AM (#20797537)
After we moved to another floor/office, I forced my team lead to move to the desk with back facing the door while I conquered the desk with a wall behind me, after spending 4+ years with the back facing the open office we had previously.

I improved exponentially my concentration and quality of work while he showed up that previously he was spending large amount of time watching YouTube/news websites/shows instead of doing work and he is frustrated that he has to do real work now.

Re:Things I Learnt from a Senior Software Engineer by saagarjha on Sunday August 25, 2019 @10:26PM (#20797019)
Or if your monitor is one of those glossy ones, just glance into a darker part.
Re:Things I Learnt from a Senior Software Engineer by dillonmckay on Monday August 26, 2019 @06:14AM (#20798581)
I had a coworker try this, and it made her more jumpy, as she would catch somebody in her rear vision across the room.

She would audibly be surprised and distract others.

Re:Things I Learnt from a Senior Software Engineer by dotancohen on Monday August 26, 2019 @04:33AM (#20798237)
You likely already have one.

The upper bezel of your monitor is likely shiny black. It makes a great mirror to know when someone behind you is taking interest in you. It is also completely inconspicuous and you do not need to move your head from your monitor to use it.

Re:Things I Learnt from a Senior Software Engineer by Sharlin on Monday August 26, 2019 @09:11AM (#20799565)
I’d say that it’s only likely conditional on having a Mac.
Re:Things I Learnt from a Senior Software Engineer by cortesoft on Sunday August 25, 2019 @10:52PM (#20797110)
Wouldn't that cause even more distraction as you see all the people walking behind you?
Re:Things I Learnt from a Senior Software Engineer by mikekchar on Sunday August 25, 2019 @11:10PM (#20797168)
Apparently (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.
Re:Things I Learnt from a Senior Software Engineer by OJFord on Monday August 26, 2019 @01:13PM (#20801655)
> I've read that in feng shui what you describe is called the "command position".

Thanks - now you say it, I think I've heard that before. (Perhaps from my father, who I know 'suffers' from the same.)

And in fact, when working from home (nobody around so it's not about being in 'command' of others at all, as a quick search tells me it isn't in feng shui either) I often prefer to sit at a table where I can see down the corridor to the front door.

Or when it's hot, on the balcony (as I am now) sitting back from the table such that my back's to the corner and my peripheral vision covers both out over the balcony to outside, and through the windows into my flat.

...interesting. It's totally sub-conscious - I always know where I want to sit in a room, or at a table in a restaurant, etc. it doesn't require thought but it certainly isn't random. I don't think about it while sitting down, but I'm sure if you asked me afterwards why I was sitting there I could tell you.

Re:Things I Learnt from a Senior Software Engineer by philwelch on Monday August 26, 2019 @01:14PM (#20801669)
I startle very easily, especially if I'm snuck up on from behind, so if anyone comes up behind me, I unintentionally scream loudly as soon as I notice them. I have found that this tends to discourage that sort of behavior.
Re:Things I Learnt from a Senior Software Engineer by bronxbomber92 on Sunday August 25, 2019 @09:08PM (#20796780)
We 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.
Re:Things I Learnt from a Senior Software Engineer by losteric on Sunday August 25, 2019 @09:15PM (#20796796)
Listening to or participating in technical conversations is just regular business, but the proposal of looking over someone's shoulder sounds very distracting and unnecessary...
Re:Things I Learnt from a Senior Software Engineer by rbavocadotree on Sunday August 25, 2019 @08:50PM (#20796708)
It'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.
Re:Things I Learnt from a Senior Software Engineer by nitrogen on Sunday August 25, 2019 @11:20PM (#20797227)
There 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.
Re:Things I Learnt from a Senior Software Engineer by dillonmckay on Monday August 26, 2019 @06:18AM (#20798591)
This 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-chang...

Re:Things I Learnt from a Senior Software Engineer by Bekwnn on Wednesday August 28, 2019 @12:38PM (#20821390)
Casey Muratori's and Jonathan Blow's streams are pretty great in this regard. Both do low-level gamedev.
Re:Things I Learnt from a Senior Software Engineer by tc7 on Monday August 26, 2019 @02:33PM (#20802422)
Really seems like I should be better at golf, then. :tear
Re:Things I Learnt from a Senior Software Engineer by arkh on Monday August 26, 2019 @05:02AM (#20798326)
That'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.
Re:Things I Learnt from a Senior Software Engineer by kemiller2002 on Monday August 26, 2019 @12:10PM (#20800975)
I 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.
Re:Things I Learnt from a Senior Software Engineer by pkrotich on Sunday August 25, 2019 @10:09PM (#20796961)
So how do you handle pair programming? It’s almost the same thing to me.
Re:Things I Learnt from a Senior Software Engineer by denton-scratch on Monday August 26, 2019 @07:05AM (#20798796)
I think pair programming requires some 'investment' at the team level. For example, the work environment (think desk arrangements) need to be set up to make pairing natural.

It's helpful if pair programming is the default mode (i.e. a dev will only go solo when there's a consensus that pairing would be counter-productive).

If you pair-off at the morning standup, so that ongoing tasks retain one dev from yesterday and gain one fresh dev, then after a couple of weeks everyone on the team can cover for anyone else, and everyone has a birds-eye view of the whole system. This was a revelation to me; prior to my encounters with pairing, I'd never worked on a team where anyone had a good overview of the whole system, including the leader. Morning standups help, but pairing-with-rotation does a much better job of knowledge-distribution.

Re. Sociability: I've paired with some very nerdy, shy people. It generally worked out well; most nerds are just fine when they are explaining what they are currently nerding about.

I've paired with people who were much brighter and more knowledgeable than me, and the other way round. Either way, it worked out fine (as long as you don't develop a Master-Apprentice syndrome).

Pairing involves quite a lot more mental effort than solo coding. I was always dog-tired after a day of pairing. Keeping track of what your pair is up to (or making sure your pair is keeping up) requires attention. And IME breaks are generally shorter.

I only had a problem when I had to pair with someone quite far along the aspie continuum; he was bright, but he was completely unable to explain what he was doing, and his code was far from self-explanatory. If you see coding as a way of communicating with programmers, rather than with machines, strongly aspie types become a workplace hazard.

Re:Things I Learnt from a Senior Software Engineer by OJFord on Monday August 26, 2019 @05:55AM (#20798514)
I've never worked at an org or on a team with an explicit 'we do pair programming', but in general if someone wants to explicitly start watching while ai walk through something, or have me watch whilethey show me something and we figure something out together, that's fine.

I will fumble the keys and be much slower if I'm the one being watched, but I'm fine with that because I know they're there and they asked.

I'd still be bothered by others walking past behind us while the person who came over to 'pair program' (if I can call what we're doing that) watches and doesn't bother me.

Re:Things I Learnt from a Senior Software Engineer by marcosdumay on Sunday August 25, 2019 @11:25PM (#20797244)
I 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.

Re:Things I Learnt from a Senior Software Engineer by bryanrasmussen on Monday August 26, 2019 @12:49AM (#20797520)
pair 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.
Re:Things I Learnt from a Senior Software Engineer by TeMPOraL on Monday August 26, 2019 @06:47AM (#20798720)
Pair 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.
Re:Things I Learnt from a Senior Software Engineer by neilv on Monday August 26, 2019 @03:08AM (#20797986)
Pair 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.
Re:Things I Learnt from a Senior Software Engineer by filoleg on Tuesday August 27, 2019 @03:03PM (#20813301)
Depends 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.

Re:Things I Learnt from a Senior Software Engineer by larzang on Monday August 26, 2019 @08:29AM (#20799262)
Interaction 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.
Re:Things I Learnt from a Senior Software Engineer by sharadov on Monday August 26, 2019 @11:20AM (#20800575)
Sometimes 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.
Re:Things I Learnt from a Senior Software Engineer by OJFord on Monday August 26, 2019 @11:30AM (#20800656)
I 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.
Re:Things I Learnt from a Senior Software Engineer by scarejunba on Monday August 26, 2019 @02:21AM (#20797826)
How 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