, 4 tweets, 1 min read Read on Twitter
There is unreasonable amounts of leverage in both software and security by communicating the blessed path to do something and making it more easy and obvious to take the blessed path and harder, crufty, and scary to take the non-blessed path.
This can be as easy as forcing an engineer to type the word "unsafe" to do things that are unsafe. (And then you can audit for that, grep for it, discourage it in training, encourage people to push back in code reviews, etc.)
Corollary: DON'T MAKE THE SAFE PATH THE HARDER ONE. This includes e.g. safely_query_the_database() over query()
That should be query() versus unsafely_query_the_database_i_know_what_i_am_doing_and_this_will_not_blow_up_because_we_had_a_review_meeting_about_it()
Missing some Tweet in this thread?
You can try to force a refresh.

Like this thread? Get email updates or save it to PDF!

Subscribe to Patrick McKenzie
Profile picture

Get real-time email alerts when new unrolls are available from this author!

This content may be removed anytime!

Twitter may remove this content at anytime, convert it as a PDF, save and print for later use!

Try unrolling a thread yourself!

how to unroll video

1) Follow Thread Reader App on Twitter so you can easily mention us!

2) Go to a Twitter thread (series of Tweets by the same owner) and mention us with a keyword "unroll" @threadreaderapp unroll

You can practice here first or read more on our help page!

Follow Us on Twitter!

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just three indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3.00/month or $30.00/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!