All Topics
All Topics
Technology
Technology
Design
Design
Programming
Programming
Science
Science
News
News
Gaming
Gaming
Entertainment
Entertainment
Business
Business
Finance
Finance
Sports
Sports
Health
Health
Food
Food
Travel
Travel
Art
Art
Music
Music
Books
Books
Education
Education
Politics
Politics
Personal
Personal
No algorithm. No AI slop. No ads. Just RSS. Pro-human. Indie writers. Real journalism. Open web. Chronological. Hand toasted.

Understanding Dangerous Advice in Software Engineering: The Parallels Between Sharp Tools and Risky Guidance

By

gxhao

9mo ago· 3 min readenInsight

Summary

The article discusses the concept of "dangerous advice" in software engineering, comparing it to "sharp tools" like production access that can be both powerful and harmful depending on how they're used. The author argues that certain advice requires competence and judgment to apply properly, and giving such advice to the wrong person can lead to destructive outcomes, similar to providing inappropriate production access.

Key quotes

· 3 pulled
Dangerous advice is dangerous because (like sharp tools) it takes competence and judgment to use well.
Giving the wrong person dangerous advice is like giving the wrong person production SQL access - they might go off and do something enormously destructive with it.
These are tools that are powerful enough to be hugely helpful or harmful, depending on how they're used.
Snippet from the RSS feed
--

You might also wanna read