AMD cards are fine from a raw performance perspective, but Nvidia has built themselves a moat of software/hardware features like ray-tracing, video encoding, CUDA, DLSS, etc where AMD's equivalents have simply not been as good.
With their current generation of cards AMD has caught up on all of those things except CUDA, and Intel is in a similar spot now that they've had time to improve their drivers, so it's pretty easy now to buy a non-Nvidia card without feeling like you're giving anything up.
It's not too difficult to use the TypeScript type checker on JS files, so it's possible to reap most of those benefits without having to introduce a compilation step.
I used to use a similar extension in Chrome called wasavi, but I got burned once too many times by bugs in extension causing me to lose all of the text I had been writing.
I was thinking about this the other day; it would be really interesting to have big corporations whose profits depend on public-domain data. We might actually see lobbying to decrease copyright terms, to counter companies like Disney trying to extend copyright until the end of time.
As someone with a YouTube channel, from looking at my metrics it's pretty clear that YouTube is being held afloat by a) the fact that non-technical users can't easily block YouTube ads on mobile devices, and b) YouTube Premium.
A single user depriving YouTube of their revenue is inconsequential sure, but when hundreds of millions of people do it (like with blocking ads on desktop) it obviously runs the risk of making the entire company unviable. Hosting videos for free is a great way to lose a lot of money.
I think there's a lot more that could be tested that what current implementation-centric interviews measure. At my company for example, I feel like we've gotten a lot of use out of our debugging interviews.
I think something interesting to note is that once we stopped atmospheric nuclear testing steel radiation levels went back down and are almost at normal background levels. So maybe the same thing will happen if we stop using GenAI.
In my experience, it genuinely lowers the activation (and total) energy for certain tasks, since LLMs are great at writing repetitive code that would otherwise be tedious to write by hand. For instance, writing a bunch of similar test cases.
People absolutely flowchart fighting games at a high level. Combos are, unsurprisingly, completely non-interactive in most games, but there's also a term specifically for non-interactive offense: setplay https://glossary.infil.net/?t=Set%20Play
The goal of an optimal strategy in fighting games is generally to reduce the amount that you have to read your opponent as much as possible, ideally to zero. Obviously the developers don't want this to be fully possible, but players generally try to get as close as they can. Even at the highest levels, you can have rounds that go like: canned opening -> combo -> setplay -> combo -> setplay -> combo.
> What's even more rare is a UX designer that also thinks about these things, who are worth a million bucks.
Tell me about it. I've been struggling for years to get our designers to think of their designs as more than pixels on a screen. I'm really tired of having to be the accessibility police, or explain that small viewports and mobile devices aren't synonymous for the nth time.
That may be your experience, but I assure you that there are plenty of companies where it's not like that. Where I work, our product team is pretty receptive to us taking time to fix tech debt, since:
- Engineering is very transparent about explaining when tech debt is slowing down development of new features
- We recognize that buggy/unreliable software hurts customer retention
- Engineering leadership has set the expectation that a significant portion of each team's time should be spent on maintenance and reliability.