578 karma · joined May 7, 2015
Perhaps we don't agree on everything here, though, because I still do not see any problems with the existence of NPEs. However, I do appreciate language features that allow you to enforce non-nullability at compile time if desired.
IMO, it would. NPE exists for a reason: to instantly alert you to a bug and/or contract violation. Maybe I misunderstood the author's intent here, but sweeping the contract violation under the rug with a superfluous null check doesn't seem to help anything here. If successMsg is null, what are you going to do, display "" instead? Often, immediate termination with NPE seems to be the best approach in cases like this, IMHO.
Yet.
My views here are purely anecdotal, and based only on interactions with former peers (students) and something an Amazon recruiter told me at one point.
What's always been a little baffling to me, though, is how easily these companies hire fresh grads. I have several friends that walked straight into FAANG jobs right out of school with little more than a couple quick phone interviews. One recruiter told me that the bar is lower for fresh grads because they can be more easily molded into the company culture.
https://www.outsideonline.com/2330916/mount-whitney-climbing...
I live near Mt. Shasta and, though inexperienced climbers do climb it, many people, because of their inexperience, vastly underestimate what can go wrong there, including very sudden changes in weather conditions.
Yeah, I've always been amazed at how unreliable and broken the Chromecast software seems to be (for me, at least). I feel like Google really missed an opportunity here.
If this hadn't been the case, I personally would have purchased more of them and, importantly, recommended them to many people. But, after a couple tries (gen. 1 and gen. 2), I gave up.