"Clearly if your manager passes your doc through an LLM, you made an error in judgment" It could also be the PM, passing everything through an LLM to make it "more understandable". Clearly, they didn't care enough to…
The boss also tried to fix it in the lowest effort manner possible, without even checking the results.
"Perhaps you should ask the manager why he passed it through AI." Because they were lazy and disrespectful, done.
As someone into performance cars and motorcycles, removing a cat is pretty uncommon, and you're generally seen as a dick if you do it.
If your program does 1 million adds, but it takes significantly longer than 19 milliseconds, you can guess that something else is going on.
Seb is incredibly passionate about games and graphics programming. You can find old posts of his on various forums, talking about tricks for programming the PS2, PS3, Xbox 360, etc etc. He regularly posts demos he's…
Would you have have chosen to work at your job if you were never going to get paid?
Damn, so you can just choose to not have guns pointed in your face? Regardless of where you live? Everyone who has had a gun pointed in their face must have been really stupid then.
It definitely makes it simpler. You can do a per-screen window sort, rather than per-pixel :). Per-pixel sorting while racing the beam is tricky, game consoles usually did it by limiting the number of objects (sprites)…
It depends on your network though. In my case the image quality was good, but going to the link cable was a substantial improvement in quality and latency.
Last year I emailed Ken Silverman about an obscure aspect of the Build Engine while working on a similar 2.5D rendering engine. He answered the question like he worked on it yesterday.
Sometimes "just thinking harder" works, but often not. A debugger helps you understand what your code is actually doing, while your brain is flawed and makes flawed assumptions. Regardless of who you are, it's unlikely…
printf isn't faster if you want to single step through code to find math precision errors. I've had to do that on a embedded system that didn't support debugging. It was hell.
Those were the 90s. Modern rasterizers* all use barycentric coordinate based algorithms for a few reasons. Easier to implement with proper fill conventions and multisampling, and much easier to parallelize in hardware…
Until the array no longer fits in your cache :)
My guess is 'A Philosophy of Software Design'.
"I don't get to get away with dealing illegal substances just because I give it away for free." Good to see you want virtual machines to be illegal.
If your headphones are blocking sound, yeah it can be hazardous.
I'm willing to bet 99.99% of the time you hear music from outside a car it's not due to someone being hard of hearing, unless they caused that issue themselves by listening to music too loud. However, if you are hard of…
Realizing that you enjoyed being forced to listen to music you didn't decide to listen to doesn't mean you might be an asshole for not enjoying it at other times. That's ridiculous.
Yeah, for example, movs between registers are generally effectively no-ops and handled by the register renaming hardware.
Sure, but lack of perspective correct texturing is a separate issue, with a separate visual artifact. Jittery polygons refers to the artifacts you get when polygon vertices are snapped to integer pixel coordinates,…
I'm guessing, just guessing, that most of the people who don't think slow execution is bad are probably not that interested in what the machine actually has to do to execute their code, and hence, are not actually well…
Quake did not use floating point in it's rasterization math, and it exhibited none of the jittery polygon issues that the ps1 did. It's largely a lack of subpixel accurate rasterization causing it (not even sure if PS1…
Sure, a year or two back in the 90s was huge. :)
"Clearly if your manager passes your doc through an LLM, you made an error in judgment" It could also be the PM, passing everything through an LLM to make it "more understandable". Clearly, they didn't care enough to…
The boss also tried to fix it in the lowest effort manner possible, without even checking the results.
"Perhaps you should ask the manager why he passed it through AI." Because they were lazy and disrespectful, done.
As someone into performance cars and motorcycles, removing a cat is pretty uncommon, and you're generally seen as a dick if you do it.
If your program does 1 million adds, but it takes significantly longer than 19 milliseconds, you can guess that something else is going on.
Seb is incredibly passionate about games and graphics programming. You can find old posts of his on various forums, talking about tricks for programming the PS2, PS3, Xbox 360, etc etc. He regularly posts demos he's…
Would you have have chosen to work at your job if you were never going to get paid?
Damn, so you can just choose to not have guns pointed in your face? Regardless of where you live? Everyone who has had a gun pointed in their face must have been really stupid then.
It definitely makes it simpler. You can do a per-screen window sort, rather than per-pixel :). Per-pixel sorting while racing the beam is tricky, game consoles usually did it by limiting the number of objects (sprites)…
It depends on your network though. In my case the image quality was good, but going to the link cable was a substantial improvement in quality and latency.
Last year I emailed Ken Silverman about an obscure aspect of the Build Engine while working on a similar 2.5D rendering engine. He answered the question like he worked on it yesterday.
Sometimes "just thinking harder" works, but often not. A debugger helps you understand what your code is actually doing, while your brain is flawed and makes flawed assumptions. Regardless of who you are, it's unlikely…
printf isn't faster if you want to single step through code to find math precision errors. I've had to do that on a embedded system that didn't support debugging. It was hell.
Those were the 90s. Modern rasterizers* all use barycentric coordinate based algorithms for a few reasons. Easier to implement with proper fill conventions and multisampling, and much easier to parallelize in hardware…
Until the array no longer fits in your cache :)
My guess is 'A Philosophy of Software Design'.
"I don't get to get away with dealing illegal substances just because I give it away for free." Good to see you want virtual machines to be illegal.
If your headphones are blocking sound, yeah it can be hazardous.
I'm willing to bet 99.99% of the time you hear music from outside a car it's not due to someone being hard of hearing, unless they caused that issue themselves by listening to music too loud. However, if you are hard of…
Realizing that you enjoyed being forced to listen to music you didn't decide to listen to doesn't mean you might be an asshole for not enjoying it at other times. That's ridiculous.
Yeah, for example, movs between registers are generally effectively no-ops and handled by the register renaming hardware.
Sure, but lack of perspective correct texturing is a separate issue, with a separate visual artifact. Jittery polygons refers to the artifacts you get when polygon vertices are snapped to integer pixel coordinates,…
I'm guessing, just guessing, that most of the people who don't think slow execution is bad are probably not that interested in what the machine actually has to do to execute their code, and hence, are not actually well…
Quake did not use floating point in it's rasterization math, and it exhibited none of the jittery polygon issues that the ps1 did. It's largely a lack of subpixel accurate rasterization causing it (not even sure if PS1…
Sure, a year or two back in the 90s was huge. :)