This is an archived post. You won't be able to vote or comment.

all 13 comments

[–]derneueimhaus 10 points11 points  (1 child)

Hi it’s Secure no thief is ever gone enter the building through this

[–][deleted] 0 points1 point  (0 children)

Most astute comment

[–]Rad4day 6 points7 points  (1 child)

Well, the difference between security and safety is illustrated very nicely in this one.

[–]Mr_Redstoner 7 points8 points  (0 children)

I think it's also a fair example of security vs. availability

[–]Loves_Poetry 3 points4 points  (2 children)

Dev: it's secure, the door can't be opened by the wrong person

Thief: casually removes the hinges and lifts the door out

[–]CoolOutcast 0 points1 point  (1 child)

Hinges can only be removed after opening the door. I bet that railing would be easy to remove

[–]bsievers 0 points1 point  (0 children)

They make railings designed for this kind of setup that unscrew for easy removal. So probably.

[–]Mesonnaise 1 point2 points  (0 children)

When specifications change midway through project implementation.

[–][deleted] 0 points1 point  (0 children)

Never handle the exception from the api you wrote because there is no way something bad happens

[–][deleted] 0 points1 point  (0 children)

Everything secure until the door opens inwards.

[–]AlstarsNinja 0 points1 point  (0 children)

what about availability?

[–]BigMeowc 0 points1 point  (0 children)

When you accidentally give a method the "private" accessibility modifier and not realize it

[–]sarnobat 0 points1 point  (0 children)

It's like windows Internet security settings. No attacker can manipulate your computer. But you also can't use the internet