I don't know, I've lived in Austin my whole life and I've always loved it. But I've also never lived anywhere else for any kind of comparison. But the traffic I've experienced visiting other cities really makes the traffic here seem not so bad, especially now that the Mopac construction has wound down.
But yes, it's frickin' hot. But I'm a homebody anyways :)
Nothing is forcing you to put everything in Redux. If state only has relevance to a single component then keep it in that components state, Redux works perfectly fine with this approach.
I'm wondering how this compares to the frequency of any comments by day. It could be that more comments are posted on Sunday in general, and the least on Wednesday.
The authors company isn't a Slack competitor, it's a real-time data platform. Otherwise I imagine they wouldn't be using Slack for their internal messaging.
That might be okay for a software engineer who can likely find a different offer somewhere else without much trouble, but that's not going to be realistic for everybody.
It looks like they've kept the D-Pad in so it can double as the A/B/X/Y buttons in that situation, which I think is a really clever way to alleviate some of that issue. I think the type of games where this use case makes sense probably don't need a large number of buttons anyways, though.
Not that I believe the rape allegations against him are necessarily true, but just because she consented before doesn't mean she consented then. That's a dangerous assumption to make in any situation.
On the other hand you could use static typing to avoid writing a lot of tests. Maybe it's a bit of preference thing, I don't mind either approach personally.