Listen

Listened to Ep 5 - Talking Openly About Pay! by Tech Team Weekly
Post details
This week, our main story is the debate over whether companies (and employees) should be happy to disclose salaries, in an attempt to drive pay equality, a chat made somewhat harder by Neil's repeated inability to pronounce the word "equality". We get deep into discussion about our experiences with knowing (or not knowing) how our colleagues are paid, companies and countries who we've seen get the balance right, and the challenges of introducing salary negotiations in the job-hunting process. But there's more! We'll also be talking about a secret new privacy-shattering setting in Chrome which is enabled by default, and bemoaning the lack of accessibility options in some modern games (and championing others which lead the way). You'll also hear what we've all been up to this week, including a top quality J-Lo story from Sanj, unexpectedly relevant election news from Neil, and Gwen basically doing everything under the sun. Plus there's an awful lot of Diablo II discussion for a podcast which isn't from the year 2000. TIMESTAMPS: 00:00 Start   02:02 The Stand-Up   14:43 Social Engineering   21:46 This Week's Epic   44:00 News Bytes   52:22 Competition Time   53:09 The Wash-Up LINKS DISCUSSED THIS WEEK: Incident.io Ministry of Testing: Test.Bash() 2021 YouTube: Neil's Continuous Quality with Postman session Jamie Tanna: Providing a Public Salary History page GOV.UK: Equality Act 2010 Blind social network YouTube: Kevin Goldsmith: How does Salary Work? (LeadDev 2019) The Verge: Apple keeps shutting down employee-run survyes on pay equity - and labour lawyers say it's illegal The Register: Google emits Chrome 94 with 'Idle Detection' API to detect user inactivity amid opposition IGN: Deathloop's Lack of Accessibility Options Is Disappointing Players Tweet thread from Courtney Craven (Can I Play That) outlining Deathloop's issues

 Repost

Reposted a post on Twitter
Post details

 Reply

True, but it does exclude non-binary folks who have vaginas? So using this terminology is inclusive to all

 Bookmark

Bookmarked Why you need a service registry
Post details
As a team's infrastructure estate grows, it becomes increasingly beneficial to create a global registry of all people, services, and components. Once you do, you can integrate with tools like terraform, Chef, and Kubernetes to help provision your infrastructure according to a single authoritative source. This post explains how GoCardless built their registry, and some of the uses we’ve put it to.

 Reply

I'd also say that ads are much harder to block in a native app compared to a browser app