News for hackers. Stuff that matters.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by superpope99 on Monday January 02, 2023 @09:02AM (#34217891)
I feel insane when I read stuff like this.

If you work in a team in any capacity then you need to have a strong baseline of trust in order to work effectively.

Trust is the building block that all effective team performance stacks on top of (see 5 dysfunctions of a team).

You don't just get trust for free, you have to build it by creating moments like this where people can demonstrate vulnerability around each other.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by comfypotato on Monday January 02, 2023 @09:26AM (#34218164)
It’s a weird balance. Being in a meeting where the manager is basically forcing people to volunteer for the fun committee makes me cringe, but then I enjoy the results of the fun committee. I greatly enjoyed Wolfram’s take on video calls. They’re essential for social aspects like building trust. When it comes time to put your nose to the grindstone and debug something together, the video is a distraction that should be eliminated.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by ElevenLathe on Monday January 02, 2023 @09:24AM (#34218147)
Doing it on purpose is the part that feels sociopathic (because it is). Working together 40 hours a week for years at a time should provide plenty of opportunity to become intimate with your coworkers. We don't need a line item in the department budget that says "fun/friendship".
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by guywhocodes on Monday January 02, 2023 @09:31AM (#34218221)
This, working in big tech I've found that the activities are also incredibly infantile and marketed as such.

Yes I work with software, no I don't expect everything to be a computer game or "cute".

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by ElevenLathe on Monday January 02, 2023 @09:43AM (#34218350)
It's doubly infantilizing: First, management assumes that their pet programmers are little babies that need play dates with the other office furniture (to mix several metaphors). Second, they assume that the only way to help us is to let us expense a round of laser tag.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by spacemadness on Monday January 02, 2023 @01:06PM (#34221299)
That’s because it’s incredibly safe to go into Disney mode. I hate it too as it makes me feel like they’re treating me like a fragile 12 year old.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by pydry on Monday January 02, 2023 @09:46AM (#34218380)
>Working together 40 hours a week for years at a time should provide plenty of opportunity

Yeah, but when starting a new project affords almost none. Should it remain like that for years?

I hate the "corporate fun" exercises as much as the next guy but without something to build trust most teams flounder.

Japananese/South Korean salaryman drinking culture (or any after work drinks culture) works well at this coz alcohol naturally makes people vulnerable. It obviously has its own problems.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by ElevenLathe on Monday January 02, 2023 @09:53AM (#34218471)
Starting a new project with a brand new team is a management failure. If you can't put the project into the hands of a team that is already functional, it will inevitably fail. Barring that, sure, you can try to fake it by pressuring your employees into doing a ton of drugs with each other on your say-so.

Just because a certain pattern of behavior is desirable for management doesn't mean that it is a healthy or even possible pattern of behavior for real human beings.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by irrational on Monday January 02, 2023 @12:21PM (#34220590)
Work build trust. Trust is built as I see your work output and the effort you are putting in. I’ve never developer trust in anyone through an activity outside of work. I have come away with a worse opinion of some people as I see how they behave outside of work.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by ElevenLathe on Monday January 02, 2023 @12:29PM (#34220720)
Exactly. Just because it would be convenient for management if $200 worth of Dave & Busters could turn a group of strangers into a well-functioning team does not make it so. Sure, you can try it, but it won't work. What will work? Not doing anything at all beyond paying people fairly, letting people have adequate time off, setting realistic expectations and deadlines, and not constantly shuffling your organization around like it's a fantasy football team.

Even if you could somehow sprinkle social fertilizer on your team and make them all besties with a sick ropes course in Provo, it is immoral to expect it. Your employees' relationships are their business, not yours.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by ghaff on Monday January 02, 2023 @10:28AM (#34218901)
I can live without a lot of the forced fun/team building exercises. As you say, a lot of this happens fairly naturally at least in person. (Certainly, less so remotely.)

On the other hand, I've heard remote/distributed people very vocally object to being asked to travel to a team meeting once or twice a year on the grounds that they work 9-5 (or whatever) and that's it.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by pydry on Monday January 02, 2023 @09:27AM (#34218179)
>You don't just get trust for free, you have to build it by creating moments like this where people can demonstrate vulnerability around each other.

This point is so important and so commonly missed in the context of remote (or indeed, any) work.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by mkl95 on Monday January 02, 2023 @09:56AM (#34218507)
> You don't just get trust for free, you have to build it by creating moments like this where people can demonstrate vulnerability around each other

Not every company is an ideal organization where demonstrating vulnerability is going to lead to a positive outcome. Fast growing orgs are often stuck with bad actors because hiring a replacement is difficult, in some cases virtually impossible. You will be stuck in a political game before you are even aware of it and forced to work with people who hate you because you worked for a FAANG or whatever tickles them.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by superpope99 on Monday January 02, 2023 @01:53PM (#34222019)
Fair point. I'm someone who's been lucky to work in high-trust low-ego teams at quite a formative stage in my career - and for this reason I try and work for companies that have values oriented around this. My current gig adheres strongly to an "idea meritocracy", and so far I have observed this to hold true. You can tell the founder his ideas suck and that's fine (if you do so in good faith). Perhaps I'm naive and my eyes will be opened to the politics later on, but I don't think so.

A lot of my colleagues in other industries often complain about the political nature of their work, and the impossibility of giving feedback to certain people in certain positions. I always assumed this was a tech/non-tech divide - or a small/large company divide. I still think those are good heuristics to be honest, but you're right about the "bad actor" dimension. I think that's why it's so important to have a well-embedded company culture, it functions as an immune system against bad actors and trust/feedback are huge parts of that immune system.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by dkjaudyeqooe on Monday January 02, 2023 @11:54AM (#34220145)
> You don't just get trust for free, you have to build it by creating moments like this where people can demonstrate vulnerability around each other.

This is bullshit. I trust my accountant because he's competent and honest, not because he's been vulnerable in my presence. What you're describing is unprofessional.

The last thing I want to know about (or experience from) my co-workers is anything personal or intimate, unless it's relevant to the job.

If I want to know my coworker better that's my choice, but otherwise it's somewhere between irrelevant and unwanted.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by JamesBarney on Monday January 02, 2023 @01:18PM (#34221473)
There are two types of trust.

1. Will I trust this person to do their job competently?

2. Would I trust this person not to defect in a prisoners dilemma situation?

The second is what you need the personal connection for. There are two ways to work on a project, to make sure it has the highest chance of success, or to make sure when it fails you don't look like your to blame.

#2 is needed so that both parties take a chance on each other and don't optimize for throwing the other under the bus.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by marcosdumay on Monday January 02, 2023 @01:45PM (#34221894)
Hum... People should not have to face prisoners dilemma situations against their coworkers. And there is an entire profession called "management" in charge of making sure of that.

People should be able to trust their coworkers on ways that the GP didn't capture. But those do not include adversarial situations. (And honestly, "Hey, how was your weekend?" can as easily add or remove all kinds of trust. None of this is simple.)

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by 411111111111111 on Monday January 02, 2023 @02:40PM (#34222629)
* * *
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by JamesBarney on Monday January 02, 2023 @05:02PM (#34224288)
I don't know what should means, but I've never worked anywhere where at one point a coworker doesn't subtly throw another one under the bus. "I would have gotten that done but I didn't get needed data until Friday". "John told me this was a higher priority." "Zach told me he'd have that done by Tuesday"

Many of the managers I've worked with spend as much if not more time thinking about CYA/metrics/etc... than accomplishing the tasks they're given. And the ones that don't spend a lot of time developing relationships instead.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by tbrownaw on Monday January 02, 2023 @07:49PM (#34226021)
... Failing to obstruct a post-mortem counts as throwing people under the bus?
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by unmole on Monday January 02, 2023 @02:06PM (#34222212)
> Would I trust this person not to defect in a prisoners dilemma situation?

Do you work for the mob?

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by Cardinal7167 on Monday January 02, 2023 @02:39PM (#34222608)
No, but I work with people, who are strangely tribal at every level and company ive ever worked at
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by LiquidSky on Monday January 02, 2023 @03:12PM (#34223024)
I feel like thinking you have to take measures to prevent future potential betrayals by your colleagues demonstrates a profound LACK of trust in them.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by JamesBarney on Monday January 02, 2023 @05:09PM (#34224361)
Software projects fail in ways both big and small every day. By being over time or budget, to not accomplishing what it set out to do, to not being able to be sold.

When those products/projects inevitably don't deliver on some expectation, someone is going to ask why? It is pretty important when that happens the answer isn't "jamesbarney is an idiot".

Here's a subtle betrayal that can happen, it comes raise time, you've been busting your ass on something that is really beneficial for the project but doesn't help any of your KPIs. Is your boss going to go to bat for you pr are they just going to tell you how important your KPIs are and wish you better the luck next year.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by LiquidSky on Monday January 02, 2023 @05:47PM (#34224779)
That sounds more like the need for standard office brown-nosing than building trust with your colleagues. Note here that your boss is not your colleague, no matter what they may encourage you to think.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by JamesBarney on Monday January 02, 2023 @08:07PM (#34226175)
Your boss is absolutely your colleague. And many times you work more closely with them than the your peers.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by LiquidSky on Monday January 02, 2023 @08:24PM (#34226301)
No, your boss is your boss. Work closely or not, be friendly or not, you are never on the same level. Forgetting that is what leads to “betrayals”.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by dinkumthinkum on Monday January 02, 2023 @07:39PM (#34225920)
I mean, can’t you make your own case by your own technical excellence and if they don’t like it, you just go somewhere else? Even if that’s not true for you, I think many would prefer that than putting themselves in better positions for who’s-fault-is-it game.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by JamesBarney on Monday January 02, 2023 @08:21PM (#34226287)
Most companies only care about technical excellence as a means to an end. Given two otherwise identified people they'd love to hire the more technically excellent one. Given two employees they prefer results.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by canadaduane on Monday January 02, 2023 @01:22PM (#34221534)
The difficulties arise when trust is single dimensional and the problems are multidimensional. If you trust someone professionally, but not personally, and there are personal conflicts or misunderstandings, you have no where to go.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by irrational on Monday January 02, 2023 @12:17PM (#34220519)
No. Absolutely not. Trust is built up over a significant period of time through… work. When I see your work is good and you are putting in the effort, it builds trust in you. I will never come to trust you over a game of kahoots.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by superpope99 on Monday January 02, 2023 @01:38PM (#34221784)
I'm talking about trust in a slightly different sense.

I'm talking about trust in a sense of - if I give you some feedback on something e.g.

"Hey I noticed that in our Zoom meetings you've had your camera off recently - we have a team working agreement that we try to keep cameras on in meetings to make remote work more tolerable. It makes me worried that you're checked out"

If there is a baseline level of trust in the relationship, that means the recipient trusts that I have their best interests at heart, and I am trying to help them through feedback, not attack them. The giver of the feedback trusts that the message will be well received.

Having this kind of trust encourages feedback, which leads growth. If you don't have this trust, everyone follows the path of least resistance of not giving feedback.

I think that especially in remote work, peer to peer feedback is such an important avenue for professional growth. Especially when a manager has 8 reports and doesn't really know what's going on.

Perhaps you disagree on the importance of feedback. But if not, then perhaps you disagree on the importance of trust in giving feedback. If so I'm curious as to whether you always find it easy to give and receive it regardless of who you're talking to?

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by ThalesX on Monday January 02, 2023 @01:56PM (#34222067)
> "Hey I noticed that in our Zoom meetings you've had your camera off recently - we have a team working agreement that we try to keep cameras on in meetings to make remote work more tolerable. It makes me worried that you're checked out"

I'm having a horrible period in my home life. My wife and I are getting ready for a divorce, my mother is sick, my child can't stand his own father. The house is always a mess and so am I. I can barely look at myself in the mirror without crying so I can't stand the idea of colleagues looking at me in a webcam.

This is hyperbole. But how would you respond in a 'trusting' environment to this?

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by bravetraveler on Monday January 02, 2023 @02:43PM (#34222673)
I'm glad you raised this -- as a person who tends to isolate when things get hard, this pretend conversation reads as fairly manipulative (the agreement and such)

That's likely not even the intention... but, something well meaning can go wildly wrong - particularly when someone is stressed

Confusing care for supervision in a way, interesting internalized response I'm chewing on

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by superpope99 on Monday January 02, 2023 @06:19PM (#34225130)
So here's the counterfactual - If there's no conversation about it, what happens? If that is the reality of that person's situation what are the outcomes if it goes unaddressed? I guess either it blows over and the person happens to pull through, or it builds up to an intolerable point and then suddenly without explanation there are 2 weeks of sick leave while the person has a breakdown?

I've had periods of my own life where I've been through tough stuff that has affected my ability to do my job - I guess I feel lucky to have had managers and colleagues who I've been able to talk to fairly candidly in these situations. In all cases I've had signal that they were grateful I shared.

In answer to your question - I would imagine a more realistic conversation might go:

"Hey I noticed X thing, what's up?" "Yeah, I'm having some trouble in my personal life I haven't been myself" "Anything you want to talk about?" "It's complicated to be honest" "Ok well take the time you need and let me know if you need anything".

That's from manager->report. Between colleagues at the same level I guess this scenario could be a bit more complex to navigate. One trivial example I can think of though is in the company I worked at during the pandemic - many moments on team meetings or 1:1 calls where people opened up about their experience of lockdown and how painful it was to be stuck inside in a shoebox of a flat in London. These moments bring people together

I also recognise that peoples' feelings on these matters are hugely cultural - I think huge chunks of the dialogue that happens in the HN comments is just people with different cultural frames of reference talking at cross purposes, but the anonymous feel of the comments section blurs this and makes it feel like everyone works at a FAANG in silicon valley.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by ThalesX on Tuesday January 03, 2023 @05:57AM (#34230029)
> I would imagine a more realistic conversation might go:

Thanks for the answer. There’s two points this realistic conversation make me think of: one would be that this would put a little crosshair on me (or larger depending on the socio-cultural aspect you mentioned) and ultimately it would end up in the same counterfactual scenario you proposed. I can’t realistically take as much time as I need to fix the situation and will end up ultimately passing it or breaking down.

Thanks again for answering, but I’m still struggling to understand bringing personal baggage in a work scenario where deep friendship is not involved.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by ohdannyboy on Monday January 02, 2023 @12:32PM (#34220769)
Trust can be built by working. Do you meet deadlines, not require me to rewrite your code on review and know your stuff? Great, we'll have a strong working relationship after a month of that. Conversely, you can be the best Among Us player in the company and I'll still hate you if you keep Slacking basic questions and submit non functioning code on review.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by superpope99 on Monday January 02, 2023 @01:26PM (#34221601)
I see your point - but rather than hate your colleague for not doing their job well, why not find a way to give them feedback? "Trust" is obviously not a substitute for performance management - but having high psychological safety/trust makes it 10x easier to have a conversation with a colleague to say "Hey I noticed you asked this question in slack - we've actually got this in a wiki over here" or "hey, I noticed you keep submitting non functioning code - why is this?". This sounds like you are describing a junior engineer - perhaps you will learn something along the way - perhaps their local dev environment is broken meaning they can't run the tests without pushing to GitHub actions, and they don't know how to fix it, but they're in a low psychological safety culture that makes them afraid of asking "basic questions" (as you put it) in Slack.

What's your philosophy on developing people in teams? I'm sure it's not just to 'hate' people into good performance. If you take a long view on people, you have to create a space where people are comfortable admitting their shortcomings.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by ohdannyboy on Monday January 02, 2023 @04:13PM (#34223759)
FWIW I don't mind being asked questions. As I have grown I've tended towards being a technical specialist over a manager and part of that is being a resource. I'm also very good with Git, GDB and Linux so I end up as the go-to guy for a lot of things (I've trained several teams on Git with a lot of success).

I've never had to build/maintain a team from a management perspective. But from my own experiences the people I've learned the most from were competent themselves, good teachers (IE they explain their reasoning and ask leading questions to help understanding) and approachable. So if I was asking too much or stuff I needed to do myself, instead of dressing my down in front of the team they'd privately say "I know we're throwing a lot at you, but time is becoming an issue on our end. I'd recommend talking to [manager] and asking for a some time to research this subject with a wiki page as a deliverable." (this is a non-hypothetical form when I was a newbie). Semi-compulsory social interactions were never a factor.

Also the person I had in mind when writing my post was actually very experienced. Affable, but totally incompetent with no interest in learning.

My expectations are relative to experience.

- Juniors need a lot of help and won't be independently solving complex problems. Every review they submit will need some guidance and it will probably be about basic things like "this function does 3 things and over uses global variables." If they're learning then they're doing it right.

- Mid level developers should be independent contributors for everything except higher level design or very technical work. Mistakes will be present but more rarely and relating to harder subjects. Mistakes I'd expect from a mid level dev would be more along the lines of not knowing that signed integer overflow is undefined in C, passing a pointer in a not quite safe way, ect.

- Senior level developers should need little technical guidance and their reviews should be almost all QA. Since they have a deep understanding of their field they can refer to documentation and datasheets more readily and when they need help they usually know what to ask. In general they should be answering a lot more than they're asking.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by kcb on Monday January 02, 2023 @12:39PM (#34220871)
Sure but that doesn't happen by getting everyone in a Zoom call and going around the room asking "Tell us a about time you felt vulnerable"
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by superpope99 on Monday January 02, 2023 @02:48PM (#34222716)
Fair point. I have found building deep trust a lot harder remotely. Thinking it through, perhaps its easier to do this 1:1 with everyone in your team, even though it's o(n^2)
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by david38 on Monday January 02, 2023 @12:53PM (#34221110)
Have you ever had surgery? Did you go out for drinks first?
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by superpope99 on Monday January 02, 2023 @02:45PM (#34222689)
My surgeon is not on my team. To take your analogy further - perhaps I would go out for drinks with my family/friends afterwards.

Intra-team relationships are different to inter-team relationships.

Re:Lessons Learned from the Book “Effective Remote Work” (2022) by layer8 on Monday January 02, 2023 @04:59PM (#34224250)
Team members shouldn’t be required to be friends though. The reason is you can choose your friends, but you can’t usually choose who’s on your team. Socializing with someone needs to be an individual choice and not a prescription.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by babyshake on Monday January 02, 2023 @01:01PM (#34221220)
My personal take on this is I don't like it when fun team building and important work meetings are mixed together. Usually this takes the form of the first 5-10 minutes of a meeting being used by the same couple people sharing mundane details from their personal life and then the meeting going over the allotted time because it started 10 minutes late. This is just bad meeting etiquette. Create separate times for this type of "fun" chat and make it completely optional to attend.
Re:Lessons Learned from the Book “Effective Remote Work” (2022) by amag on Wednesday January 04, 2023 @05:55AM (#34244176)
If you for instance work with software developers, true vulnerability shows at a code review not at a occasional game of soccer or similar. Few software developers identify themselves as great soccer players so it's not a threat to their identity to be perceived as bad at it.