DEV Community 👩‍💻👨‍💻

Tanya Janca
Tanya Janca

Posted on • Updated on

Pushing Left, Like a Boss — Part 5.9 — Error Handling and Logging

This series, and my blog, have moved! Check it out!

All errors should be caught and handled gracefully; there should never be a stack trace or database error on the screen. Not only so that we look like professionals, but so that attackers are not given extra information to use against us when creating their attacks. When errors happen, an application should never fail into an unknown state, it should always roll back any transaction it was performing, and ‘close’ anything it may have opened. Such a situation should also always be logged, so that if an incident were to arise incident responders would have something to work with when they investigate, and so that auditors can verify that the system is and has been working correctly.

In Hong Kong, at “The Peak”.

Read the rest on my NEW blog!!

Top comments (0)


Thank you.

Thanks for visiting DEV, we’ve worked really hard to cultivate this great community and would love to have you join us. If you’d like to create an account, you can sign up here.