teirce

Isn't this the whole point of something like Chaos Monkey? Has the industry at large just lost the plot here?

Yes after the success of frostbite around Bad Company 2 and Battlefield 3 or so, EA decided it should be used in everything. Not unlike the mistake Capcom is making with REngine right now, if the performance woes of Monster Hunter Wilds and Dragons Dogma 2 are anything to go by.

Pretty sure there was even a Need for Speed game on Frostbite which was... huh.

Yeah... my program covered basically everything from raw theory to architecture to assembly up to [insert n others] Python and Haskell.

But it was a CS program, not a SWE program, the two of which the industry has confused for all of time (though there was an actual Software Engineering course offered as well).

One anecdote for another - I have an LG CX which released in 2020. It's on basically 24/7 (rotating photos through a Chromecast when not actively in use), occasionally I'll turn it off at night. It does regular pixel cleaning on its own that sleeps the panel for a few minutes.

I've not seen any burn-in.

All of these burnout 'tests' I've seen (this one, and RTings as well) purposefully use static content and are basically abusing the panel in a way that is specifically advised against. I find them pretty useless for anything not an office TV on the wall running CNN 24/7, which I will never be doing myself.

I don't think anyone familiar with the tech will deny using these panels in such a way will cause burn-in, even the test here:

> ...static desktop content such as web browsers, document editors, and spreadsheets, along with creative apps like Photoshop and Premiere. We don't recommend using an OLED monitor like this. These displays are best suited to content consumption[...]

I think it's pretty avoidable on a TV, the real issue comes from what you need out of a desktop monitor. I have a Dell/Alienware (Samsung QD-OLED Panel) that's about a year old without any visible issues, but it's still early to tell in that case.

The tech has gotten better, but the problem still very much exists.

This idea has spread outside of the FGC at this point. I see other places mentioning it as well. I also think you were able to mod SFV to be able to use the paid costumes (or whatever you want as evidenced by the Chun-Li scandal in 6) without actually buying them. Different engines, but I'm sure Capcom didn't like it.

Another point people bring up is that Capcom has been adding micro-transactions post-launch to some of the new Resident Evil remake titles, that effectively power you up to some degree... In the same way that a mod (or cheat engine or whatever you want to call it) could do for free.

The only time period I can even think of that _might, maybe_ qualify would be the Source mod era, but that came and went over a decade ago. And of course they were free mods, not standalone games with purchases or licenses.

Some of these mods turned into games later (Chivalry, Black Mesa, Insurgency come to mind) but without investigating I'm not sure they even use Source anymore.

The point of pair programming isn't really to be talking to someone while they are coding a known solution. It's to work through and discover a solution together to an unknown. In this sense, you're kind of both in the same headspace together, and can have a conversation without necessarily breaking focus. And I would venture that almost any question that comes up in pair programming would either come up later in code review, or could be hand-waved with "yeah, I plan to fix that with X" and move on.

The important part of pair programming isn't really the programming per se, it's the discussion.

It also requires some amount of conversational art. As for being self conscious about things, you would have poor coworkers who make you think that or some unfounded worry. A good pair programmer can have a discussion without making you feel like an idiot - much the same as a good code review.

This was my experience as well. It's completely up to management to recognize these kinds of engineers regardless of role name or leveling.

Thank you for taking the time to write out this detailed feedback. I will have to think hard about how my resume may change, and in what ways.

I may end up starting from scratch and seeing what I can come up with and get further feedback from there.

Thank you for the fresh set of eyes and the feedback. I think I have spent so much time staring at, reading, and revising this thing that I’ve become blind to issues like these.