ericb 12 days ago | unvote [-] * Better googling. Time-restricted, url restricted, site restricted searches. Search with the variant parts of error messages removed.* Read the source of upstream dependencies. Fix or fork them if needed.* They're better at finding forks with solutions and gleaning hints from semi-related issues.* Formulate more creative hypothesis when obvious lines of investigation run out. The best don't give up.* Dig in to problems with more angles of investigation.* Have more tools in their toolbelt for debugging like adding logging, monkey-patching, swapping parts out, crippling areas to rule things out, binary search of affected code areas.* Consider the business.* Consider user-behavior.* Assume hostile users (security-wise).* Understand that the UI is not a security layer. Anything you can do with PostMan your backend should handle.* Whitelist style-security over blacklist style.* See eventual problems implied by various solutions.* "The Math."
What do top engineers do that others don't?
- Better googling. Time-restricted, url restricted, site restricted searches. Search with the variant parts of error messages removed.
- Read the source of upstream dependencies. Fix or fork them if needed.
- They're better at finding forks with solutions and gleaning hints from semi-related issues.
- Formulate more creative hypothesis when obvious lines of investigation run out. The best don't give up.
- Dig in to problems with more angles of investigation.
- Have more tools in their toolbelt for debugging like adding logging, monkey-patching, swapping parts out, crippling areas to rule things out, binary search of affected code areas.
- Consider the business.
- Consider user-behavior.
- Assume hostile users (security-wise).
- Understand that the UI is not a security layer. Anything you can do with PostMan your backend should handle.
- Whitelist style-security over blacklist style.
- See eventual problems implied by various solutions.
- "The Math."