You must log in or register to comment.
Manually optimizing the code I wrote in C, so that it runs noticeably slower and has all sorts of stupid bugs that weren’t there before. All in a good night’s work.
Well, I guess it’s either writing a device driver or that.
And the device driver will always end-up with most code in C or Rust.
That doesn’t sound like optimization.
No worries, he can optimize it later.
Put a refactor ticket in the backlog. We’ll get to it eventually, right?
// TODO: fix this code
It’s just reverse optimizing!
To you, maybe.
