Skip to content
Hallway
0:00 / 0:00

#ethics#softwaredesign

The Consequences of Your Code

Tom Scott

6.7M subscribers • 34 videos on Hallway

YouTube
  • Recommended by 3 people: 1 on Lobsters and 2 in engineering communities.
  • A classic. People kept recommending it from 2018 to 2022.
  • Presented by Tom Scott
  • An opinion. It argues one side of a question engineers disagree on.

Beginner. No background in the topic needed.

1.8M views7 years ago3 recommendations

Tools and practiceCareers and interviewsCode review and teamworkThe tech industry

Tom Scott discusses the real-world consequences and ethical responsibilities that software developers and designers face.

This is the story of one of the best, and also one of the worst, text messages I've ever received. It's about harm, about consequences, and about the responsibilities that designers, coders and hackers have to make sure we treat other people with care. 🟥 MORE FROM TOM: tomscott.com/ (you can find contact details and social links there too) ❓ LATERAL, free weekly podcast: lateralcast.com/ youtube.com/lateralcast/ 👥 THE TECHNICAL DIFFICULTIES: youtube.com/techdif

Why it's here

3 people recommend this

What people say. Engineers point to this video to highlight the ethical responsibilities and real-world impact of software development.

oatson Lobsters • Recommends

The Consequences of Your Code
7View on Lobsters

u/sinagogin r/programming • Recommends

On “I made a playlist of 129 videos on programming that made me a better developer”

You mean from his recent stuff on Twitter about guns and privilege? He's certainly the most divisive figure around! I think some of his work is still really important, and we shouldn't fall into a the trap that because we don't agree with someone, everything they say is bad. I mean, his stuff on how developers kill people, and will kill more people, is entirely true. This Tom Scott video shows that much: link to this video
6View on Reddit

u/ShinyHappyREMin r/programming • Recommends

On “TIL that Hyrum of "Hyrum's Law" is a senior staff engineer at Google whose coworkers - after hearing him frequently refer to an already known phenomenon without a name - jokingly refer to it as "his law". The name stuck and become widely accepted.”

relevant Tom Scott: The Consequences of Your Code
4View on Reddit