lovatsofa

I'm sorry, that sounds both difficult and disconcerting.

"It's better to hide certain skills."

This perspective hadn't occurred to me, and it's likely a more pragmatic approach than my own, which is to sing my interests from the rooftops and scribble them in chalk, hoping to find other like-minded individuals. A paradoxical approach, driven by the harsh effects of loneliness on well-being, one that might need reconsideration.

Thank you gghoop

While it's not explicitly stated, I would like to respectfully disagree with the notion that developers who avoid webcam use in virtual meetings are being "difficult" or impairing communication by omitting visual cues. Although non-verbal signals can enhance interactions, the insistence on webcam use neglects deeper issues of psychological comfort and privacy, which are particularly pertinent for individuals from minority groups or those with lower social status. For some, not displaying their environment might actually level the playing field.

Your point about body language is well-taken, but it’s crucial to recognize that much of human communication is rooted in biological signals that webcams simply cannot capture. These include oscillatory patterns in our nervous systems, pheromones, and pupil dilation—subtle cues that are crucial for face-to-face interactions but are lost in digital communication. If we find ourselves overly concerned about body language in pixelated, compressed, and inherently artificial digital formats, we might need to reconsider if remote work is suitable for us.

Moreover, it’s important to acknowledge that not everyone interprets social cues in the same way. Neurodivergent individuals, for example, may struggle more with deciphering body language, suggesting that the capacity to do so is not universal but rather a privilege.

Have you had a chance to watch We Live in Public? This documentary delves into an early internet experiment where constant surveillance led to significant stress and self-censorship among participants. Though not a direct analogue to virtual meetings, the film highlights the psychological toll of persistent observation—a toll that does not necessarily foster better communication or collaboration.

In my own experience, I've worked with several developers who prefer to keep their cameras off, and I've observed no detrimental impact on the quality of their work or on team dynamics. If you've noticed that developers who disable their cameras tend to be problematic, it might be worth revisiting hiring practices to ensure they align more closely with the diverse preferences and needs of tech talent.

As for my personal preference to keep the camera off, I prefer not to share too many details, but I've included links to several studies that discuss the broader implications of webcam use along with a more recent study about a potential camera alternative, biosignal data.

- https://ieeexplore.ieee.org/document/10599432 - https://psycnet.apa.org/buy/2021-77825-003 - https://tmb.apaopen.org/pub/nonverbal-overload/release/2 - https://www.tandfonline.com/doi/full/10.1080/13678868.2022.2... - https://www.mdpi.com/2673-8104/3/1/10

If you’re willing to elaborate, I’m curious about what they cited as evidence for your supposed lack of transparency?

I appreciate the point about directing these questions to the source, and you are likely right that I'm unlikely to find any concrete answers here. To answer your question, it feels like I did ask why the decision was being made but the response was vague- essentially, I was told to focus on testing. I'm wary of pressing further, as it risks being interpreted as pushback rather than a legitimate concern about efficiency. This would be a non-issue if I were communicating with technical leadership but given the lack of technical understanding from those making the decision, there’s a real possibility that further questions would be dismissed or viewed negatively.

I see your points, and I genuinely hope you're correct—if this is merely a new policy aimed at limiting access to the code, then I can understand the broader motivations behind it. That said, given my concerns about cost and efficiency, the question becomes whether it's worth the effort to try and get leadership to reconsider. From a practical perspective, the restriction makes my job notably more difficult. The Inefficiencies introduced directly translate into lost time, hindering my ability to troubleshoot, test and debug efficiently. Over time, this could affect my productivity, or at least the appearance of it, which in turn could be detrimental when my output is closely scrutinized. The indirect, long-term impact on the product is another rabbit hole entirely.

TL;DR If due to policy changes and my concerns are valid, do I pursue raising my concerns to leadership?

Good question. No, the same restrictions do not apply to my colleagues, though they are technically part of a different "team"—emphasis on the quotes. The work we do is largely identical. Do you think the disparity in treatment, despite the similarity in roles, suggests that the restriction is less about the actual work being done and more about other, unstated factors specific to my situation?

{MOVED TO COMMENTS}

1. I’ve been asked to keep my camera on in most meetings. 2. Like many in the tech world, I generally prefer to keep it off. 3. I was pulled aside over concerns that my LinkedIn profile "looked suspicious." 4. Admittedly, my LinkedIn does look suspicious to anyone who doesn’t communicate with me regularly or hasn't met me recently. 5. As with many developers, I place a premium on privacy, and some of my actions to safeguard it might appear suspect. 6. I’m involved in the cybersecurity community, participating in conferences and learning platforms. 7. The individual who asked me to remove the repository is non-technical. 8. The company I work for is not a tech company. 9. My direct supervisors and decision-makers are also non-technical. 10. I maintain strong relationships with technical team members. 11. I’ve had difficulties navigating remote work dynamics with non-technical colleagues. 12. I speak up less than I used to—this could be interpreted as disengagement. 13. In the past, I struggled to make measurable progress or explain setbacks, which hasn’t reflected well on me. 14. I’ve made no secret of the fact that Quality Engineering is not my passion, preferring development work instead—a comment that’s occasionally thrown back at me: "I know you’d rather be doing X, but..." 15. I have fewer than 10 years of experience in the industry and appear quite young. 16. I’ve been with the company for several years. 17. I work remotely. 18. I attempted to explain our CI/CD pipelines, the importance of QE, and why I believe I need access to the repo.