If I didn ' t already have a Deathadder , I would jump on this deal . <| sep |> The fact that he justifies undeniably rude behavior as the world isn ' t fair . It ' s a rationalization to excuse bad behavior . That ' s how he is entitled . <| sep |> He averaged 210 passing yards through 4 games . <| sep |> ARE YOU SATISFIED WITH MY NAE NAE , YOU FUCKING PEDESTRIANS ? !<| sep |> The master approves ? <| sep |> Heard that he had some weight issues so he had to do some type of a surgery not sure though <| sep |> i took 12 day leave Di was lucky got a manager cool enough for this <| sep |> I zoomed in on the first picture and then scrolled down and saw it was close enough to read <| sep |> It comes down to using it where it makes sense and not just using it to avoid null . It ' s best to use it when there ' s an explicit business rule for handling value vs . no value . If no value is merely an error state , I find using null checks to be cleaner . A good example is a project I worked on recently . I was receiving a stream of video frame objects over the network . I got a Frame object , and it it was valid drew it to the screen . If I ever didn ' t have a valid Frame , I was to draw a blank frame myself . The code handling the incoming data would give me a null if it couldn ' t produce a valid frame . I bubbled this up as OptionalFrame into my controller , so I could cleanly express if I have a value , draw it , if I don ' t have a value , draw something else . In this case , merely checking for null wouldn ' t convey that the API very well could return null as something that was still valid in terms of business rules .