Unfortunate for Daniel, but excited to see more of Liam. Seriously impressive drive last weekend, to even keep it on the road in those conditions, with virtually no experience in an F1 car, but then placing above Tsunoda? That's a dream result no one could've anticipated. Eagerly anticipating seeing him run again, with an actual chance to prep a little, and to do the practices, to see if he can keep it up.
Hazzard
joined 1 year ago
Agreed, I thought mentioning those statistics was a tasteful way of addressing that conversation as best as possible in a YouTube video, and those "people will be fired" comments felt like a clear commitment to rooting out and going as far as firing anyone creating that kind of environment.
The amount of "Linus didn't even talk about" in this thread is crazy to me, just feels like bad reading comprehension when he directly addressed most of the conversation (HR, work hours and environment, etc) and even committed to firing people in a video his staff will all be watching.
Dang, this just makes me impressed at what you've managed on your first outing with React Native. You've got impressive design sensibilities to get so much right that you're still one of the best apps out there.
Hopeful this rewrite gives you the technical foundation you've been looking for, so that this can continue building into the best app it can be!
I totally thought those "facts" were going to be the made up crap that dads come up with to mess with their kids.
I.E. My dad once told me that the reason we sweat was because if we didn't we'd burst into flames when we get hot.
Way more entertaining than legitimate misinformation and misunderstandings.
Agreed. The upload schedule has been a holy grail within LTT for a long time, and I truly believe it's the root of all of this, yes, even the sexual harassment. Or at least how that harassment was handled so poorly. When do you have time to make good HR policies? Pull people into HR for reprimanding? Have opportunities for others to second guess decisions? Do training? Or heck, even just have less tired and irritable people making in-the-moment stupid decisions?
This uncompromising maximum velocity hurts everyone, and I hope they keep never bring it back to this pace, even after the process improvements they have planned.
Yeah, this certainly raises to mind the times I've heard them discuss on WAN Show how employees have inquired about reducing the release schedule, and how that's not considered a real option. That decision has costs...
Frankly, this whole situation boils down to exactly what I expected. LTT has always produced content at an insane velocity, and issues like these are the inevitable results. Miscommunications, errors that need to be tidied up, and compromises such as that water block video not being redone with the proper setup. LTT doesn't have the ability to reverse course on an emergency like that, they're already at breakneck pace so that they can't make a change of that scope without missing deadlines. If it wasn't this, it would've been something else.
Is that evil? I don't know. It's the business strategy they've gone with, and much of why they're in the position they are. An LTT that put out half the videos they do may have never made it to this position. This is a good wake up call as to the costs of that kind of operation, and it's up to you how you choose to react to this.
When I was a little kid my parents had to sit me down and teach me the "non verbal cues" for when someone wants out of a conversation: no eye contact, weak or no confirmation ("oh yeah?" "And then what?" vs "uh huh"), and flat body language. It was sorely needed information at the time, and to this day I still occasionally run through a checklist if I catch myself getting too fired up about something or other.
Exactly the mistake threads just made, trying to capitalize on twitter's rate limiting fiasco. The "general public" is extremely fickle, and Reddit will give us more opportunities.
I'm not sure I understand your position here, because voting is such a minor part of the system. A troll that only trolls by upvoting and downvoting isn't much of a threat, unless they've got a dozen alt accounts or a botnet, both of which are different situations that should be handled differently. "The definition of a troll" is ridiculous hyperbole.
And as far as bans are concerned, that's a moderation problem, not your role as an individual. I've never suggested votes should be completely untraceable, that'd be patently ridiculous and remove the ability to actually handle vote manipulation. Moderators and admins should obviously have that access, as I've asserted in this thread.
I'm also not advocating my votes be anonymous, I'm fine with having them public on my page. That alone gives you the complete ability to make a judgement about me as a person, or whatever it is you want to do with that. What I'm suggesting is that a user who's just been downvoted shouldn't have a trivial way of linking it to the individual who downvoted them in order to harass them.
Frankly, the impression I'm getting is that you're not actually paying much attention to the case I've made, and are instead just using my comments as a platform to have a completely different argument that you're passionate about. That's the ONLY way that you could have missed my point so entirely, and come to the conclusion that I could ONLY be a troll or a moron.
It's not being a troll, downvotes are part of the system for a reason: suppressing toxicity. If you downvote a toxic comment to push it down in the algorithm, there shouldn't be a risk of that toxic person deciding they have a grudge and attacking you personally. Otherwise you risk downvotes not being used for their intended purpose, and an overall more toxic environment.
Having used tailwind a little bit, I have nothing but praise for it. Effortless copy/pasting of components with confidence, really nice look by default, easy tweaking, absolutely no management or planning required to organize your CSS, and it's all right there, directly on your html, never anywhere you have to hunt for it. Feels very freeing to just... not think about CSS at all.
And the "clutter" really is fine, modern IDEs with good syntax highlighting, plus a tailwind extension to help complete the class names and clean up accidental duplicates or conflicting properties, and you're good.