The Unattainable Confidence of Screen Sharing
Description
A screenshot of a tweet from the popular satirical tech account 'I Am Devloper' (@iamdevloper). The tweet, posted on June 26, 2020, reads: 'God grant me the confidence of the person who says they're going to share their screen and doesn't immediately ask if everyone can see it.' The screenshot shows the tweet has garnered 846 retweets and 4.1K likes. This meme perfectly captures the universal anxiety and muscle memory of anyone who has ever had to present or collaborate remotely. The act of sharing a screen is so fraught with potential technical glitches that it has become a standard ritual to immediately seek confirmation. The joke is that abstaining from this ritual isn't just normal - it's a sign of almost superhuman confidence, something to be prayed for. For experienced developers, who often have to lead demos, pair program, or troubleshoot live, this is a deeply relatable moment of shared vulnerability and a commentary on the unreliability of our collaboration tools
Comments
7Comment deleted
The truly confident engineer doesn't ask if you can see their screen; they just start presenting and wait for the inevitable '...you're still on mute' five minutes later
Screen sharing is the harshest eventual-consistency system: my local state shows the IDE, half the quorum reports PowerPoint, and the VP’s replica is stuck on my Slack DMs - classic split-brain with zero failover
After 20 years in tech, I've learned that the people who don't ask 'Can you see my screen?' are the same ones who deploy straight to production on Fridays - either they've transcended fear itself or they're about to learn why we have incident response teams
The real senior move is sharing your screen with 47 browser tabs open including 'how to exit vim', three Stack Overflow threads about the same problem, and your company's internal wiki page titled 'Why is production down again' - all while maintaining unwavering eye contact through the webcam and never once asking for confirmation
Skipping 'can you see my screen?' is like deploying without health checks - optimistic until you realize half the cluster is watching a cached thumbnail
“Can you see my screen?” is the Raft heartbeat of remote work - skip it and you risk a split-brain where half the team is staring at your calendar
Like kubectl apply -f prod.yaml without --dry-run: assumes the cluster's ready, ignores the inevitable 'node not found' panic