I saw this the other day and had to grab a quick picture of it, but I will add that I left both the lock and the locker contents alone after that. It did get me thinking about how we view security in the software industry which, given recent events, is more visible now than it has been in the past.
When we look at writing software we have to think about the security implications of what we are doing. How will the software be used? How will it be accessed? How do we secure data not only when it's at rest (sat on the disk), but also when it's in transit (e.g. being sent over the internet)? Am I likely to leak important information if I keep security information in-memory.
I've often heard people say "well they need a password to get in so it's fine", but like the lock in the picture that could just be putting a façade of security in place, someone could still get in around the sides.
One of the most crucial ways of thinking we can incorporate into daily development is "how would I break into this?". Think about hacking yourself first before giving others the opportunity to because, inevitably, they will try. If you're looking for somewhere to start or to get some ideas from then I'd recommend this excellent blog post from Troy Hunt.
Just in case you can't see the issue with the picture above. The cable which is looped through the lock point and the lock will happily slip between the hole in the door and the lock point, meaning the door can be opened to almost the length of the cable loop.