@GailKir94323570 @gunsnrosesgirl3 Because this is Akihabara station in Tokyo. People are used to seeing other people do weird stuff around there all the time especially for social media.
Tokyo has 14 million people who live there and yet I’m walking through a shopping street in Ginza and there is no crime, no people shooting up drugs, no looting, no homeless and no random migrants trying to eat pets.
Public safety is a choice and the West has decided to completely give it up for the sake of “wokeness”.
It’s not right, but it’s certainly a choice. It doesn’t have to be the way it is, America. It doesn’t have to be that way.
@lauriewired The Delta in seat video system is pretty buggy and the flight attendants fix it by rebooting the system for everyone. The Linux boot screen probably happens to me every one in ten flights.
@levelsio@NathanLands YMMV. Wildly. Tokyo has both extremes depending on whether they're trying to save money. OTOH, many shops will go as far as making sure the cold air spills out on the street to attract people in. I definitely find this more common than the AC conservation mindset mentioned above.
@hot_girl_spring 1) The current line is more semantically relevant to logging the exception
2) indication that this is expected and a known issue
3) consolidate logging of multiple congruent exceptions that have varying stack traces or types
Would be interested to know if there's a comment above
Here’s the thing folks. I’ve been coding 32 years. When something like this happens it’s an organizational failure. Yes, some human wrote a bad line. Someone can “git blame” and point to a human and it’s awful. But it’s the testing, the Cl/CD, the A/B testing, the metered rollouts, an oh shit button to roll it back, the code coverage, the static analysis tools, the code reviews, the organizational health, and on and on. It’s always one line of code but it’s NEVER one person. Implying inclusion policies caused a bug is simplistic, reductive, and racist. Engineering is a team sport. Inclusion makes for good teams. Good engineering practices makes for good software. Engineering practices failed to find a bug multiple times, regardless of the seniority of the human who checked that code in. Solving the larger system thinking SDLC matters more than the null pointer check. This isn’t a “git gud C++ is hard” issue and it damn well isn’t an DEI one.
I decided to write a blog post describing what's been going on with Crayon and a few projects I've been working on. Long story short, I'm going to be creating a scripting engine as a flexible drop-in library called CommonScript.
Link in the reply because F*ck twitter algorithms.
It has now been 0 days since I googled a question and the first result is a stack overflow question where the first response is "have you tried just googling it?"
@hnshah Used by millions -> company becomes large and more corporate -> employee performance is graded by impact and on quarterly schedule -> disruptive features are shipped sooner than they're ready -> employees get promotions and kudos -> cycle continues