But admit this boost is only seen in ‘an obscure filter’.
Just goes to show that when you work on a project that’s so fundamentally useful that it doesn’t require constant pivoting, you can not only address all your tech debt, but actually get around to those optimizations you brainstormed.
“Almighty PM, I can write the cleanest and fastest of holy ASM. It will be the most glorious thing.”
“Best I can do is another button.”
That’s why one of the most common ways of dealing with tech debt is allocating time for it within other sometimes completely irrelevant stories. For management you can just say “oh I take a bit of extra time for tech debt there”, if they’re known to take that well, and if not, you don’t say anything at all. The ones who you should definitely tell all the details is your team lead / collegues. Like, “oh this is a mess I’ll take some time for refactoring/optimizing this next planning”, which often implies you allocate this time within other stories.
AVX512, SIMD
It’s not just “handwritten assembly”, it’s all intrinsics, again. The reason a lot of tech that needs to use fast matrix algebra (or fast numeric math in general) tries to use the same small set of libraries, tightly optimized to use those optimized instruction sets.
These guys are true assembly wizards
What does ‘handwritten assembly code’ mean? I assume they’re not writing it in cursive. Apparently some code is compiler created so it sounds like this is a synonym for code written by a person? There must be a better term for describing this than ‘handwritten’.
It means someone wrote actual assembly code instead of writing C code and relying on the compiler to generare optimal assembly for them.
Yes, I believe you understand correctly. The vast majority of all native code is written by other computer programs (compilers). Handwritten assembly code usually means code that was instead produced more directly by a human programmer, most probably with the help of an assembler rather than compiling from a higher-level language.
