Dangerous Advice for Software Engineers
15 days ago
- #dangerous-advice
- #career-growth
- #software-engineering
- Dangerous advice is powerful but requires competence and judgment to use effectively, similar to sharp tools like production access.
- Examples of dangerous advice include making your own decisions on what to work on, breaking company rules deliberately, and taking strong positions even when uncertain.
- Most career advice is considered fake, written to avoid liability or impress, whereas dangerous advice is sought by strong engineers for its effectiveness.
- Managers rarely give dangerous advice due to the risks involved, even though they might appreciate when engineers follow such advice tactically.
- Following dangerous advice is high-risk, high-reward, making it more beneficial for strong engineers but potentially harmful for weaker ones.