black0ut@pawb.social to Programmer Humor@lemmy.ml · 11 months agoThey had a paid break, right?pawb.socialimagemessage-square60fedilinkarrow-up11.14Karrow-down111
arrow-up11.13Karrow-down1imageThey had a paid break, right?pawb.socialblack0ut@pawb.social to Programmer Humor@lemmy.ml · 11 months agomessage-square60fedilink
minus-squareherrvogel@lemmy.worldlinkfedilinkarrow-up65·11 months agoManually 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.
minus-squareCoreidan@lemmy.worldlinkfedilinkEnglisharrow-up9arrow-down2·11 months agoThat doesn’t sound like optimization.
minus-squareFreesoftwareenjoyer@lemmy.worldlinkfedilinkarrow-up17·11 months agoNo worries, he can optimize it later.
minus-squareTheGreenGolem@lemmy.dbzer0.comlinkfedilinkEnglisharrow-up13·11 months agoPut a refactor ticket in the backlog. We’ll get to it eventually, right?
minus-squareFreesoftwareenjoyer@lemmy.worldlinkfedilinkarrow-up13·11 months ago// TODO: fix this code
minus-squaremarcos@lemmy.worldlinkfedilinkarrow-up6·11 months agoWell, 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.
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.
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 codeTo you, maybe.
It’s just reverse optimizing!
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.