▲ 1144 ▼ They had a paid break, right? (pawb.social) submitted 2 years ago by black0ut@pawb.social to c/programmerhumor@lemmy.ml 61 comments fedilink hide all child comments
[–] PM_ME_VINTAGE_30S@lemmy.sdf.org 21 points 2 years ago (12 children) What are you doing in assembly? permalink fedilink source hideshow 12 child comments replies: [–] herrvogel@lemmy.world 66 points 2 years ago (7 children) 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. permalink fedilink source parent hideshow 7 child comments replies: [–] Coreidan@lemmy.world 7 points 2 years ago (5 children) That doesn’t sound like optimization. permalink fedilink source parent hideshow 5 child comments replies: [–] Freesoftwareenjoyer@lemmy.world 17 points 2 years ago (2 children) No worries, he can optimize it later. permalink fedilink source parent hideshow 2 child comments replies: [–] TheGreenGolem@lemmy.dbzer0.com 13 points 2 years ago (1 child) Put a refactor ticket in the backlog. We'll get to it eventually, right? permalink fedilink source parent hideshow 1 child comment replies: [–] Freesoftwareenjoyer@lemmy.world 13 points 2 years ago // TODO: fix this code permalink fedilink source parent [–] herrvogel@lemmy.world 9 points 2 years ago To you, maybe. permalink fedilink source parent [–] Hellstormy@lemmy.world 5 points 2 years ago It's just reverse optimizing! permalink fedilink source parent [–] marcos@lemmy.world 6 points 2 years ago 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. permalink fedilink source parent [–] ikidd@lemmy.world 40 points 2 years ago Suffering. permalink fedilink source parent [–] guiguinofake@sh.itjust.works 7 points 2 years ago Pretending I was born 40 years earlier permalink fedilink source parent [–] jol@discuss.tchncs.de 6 points 2 years ago Assembling. permalink fedilink source parent [–] embed_me@programming.dev 2 points 2 years ago Doing vector operations because the MCU vendor didn't provide APIs for it. (did not actually do that but was preparing to before we came to our senses and ditched that MCU) permalink fedilink source parent
[–] herrvogel@lemmy.world 66 points 2 years ago (7 children) 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. permalink fedilink source parent hideshow 7 child comments replies: [–] Coreidan@lemmy.world 7 points 2 years ago (5 children) That doesn’t sound like optimization. permalink fedilink source parent hideshow 5 child comments replies: [–] Freesoftwareenjoyer@lemmy.world 17 points 2 years ago (2 children) No worries, he can optimize it later. permalink fedilink source parent hideshow 2 child comments replies: [–] TheGreenGolem@lemmy.dbzer0.com 13 points 2 years ago (1 child) Put a refactor ticket in the backlog. We'll get to it eventually, right? permalink fedilink source parent hideshow 1 child comment replies: [–] Freesoftwareenjoyer@lemmy.world 13 points 2 years ago // TODO: fix this code permalink fedilink source parent [–] herrvogel@lemmy.world 9 points 2 years ago To you, maybe. permalink fedilink source parent [–] Hellstormy@lemmy.world 5 points 2 years ago It's just reverse optimizing! permalink fedilink source parent [–] marcos@lemmy.world 6 points 2 years ago 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. permalink fedilink source parent
[–] Coreidan@lemmy.world 7 points 2 years ago (5 children) That doesn’t sound like optimization. permalink fedilink source parent hideshow 5 child comments replies: [–] Freesoftwareenjoyer@lemmy.world 17 points 2 years ago (2 children) No worries, he can optimize it later. permalink fedilink source parent hideshow 2 child comments replies: [–] TheGreenGolem@lemmy.dbzer0.com 13 points 2 years ago (1 child) Put a refactor ticket in the backlog. We'll get to it eventually, right? permalink fedilink source parent hideshow 1 child comment replies: [–] Freesoftwareenjoyer@lemmy.world 13 points 2 years ago // TODO: fix this code permalink fedilink source parent [–] herrvogel@lemmy.world 9 points 2 years ago To you, maybe. permalink fedilink source parent [–] Hellstormy@lemmy.world 5 points 2 years ago It's just reverse optimizing! permalink fedilink source parent
[–] Freesoftwareenjoyer@lemmy.world 17 points 2 years ago (2 children) No worries, he can optimize it later. permalink fedilink source parent hideshow 2 child comments replies: [–] TheGreenGolem@lemmy.dbzer0.com 13 points 2 years ago (1 child) Put a refactor ticket in the backlog. We'll get to it eventually, right? permalink fedilink source parent hideshow 1 child comment replies: [–] Freesoftwareenjoyer@lemmy.world 13 points 2 years ago // TODO: fix this code permalink fedilink source parent
[–] TheGreenGolem@lemmy.dbzer0.com 13 points 2 years ago (1 child) Put a refactor ticket in the backlog. We'll get to it eventually, right? permalink fedilink source parent hideshow 1 child comment replies: [–] Freesoftwareenjoyer@lemmy.world 13 points 2 years ago // TODO: fix this code permalink fedilink source parent
[–] Freesoftwareenjoyer@lemmy.world 13 points 2 years ago // TODO: fix this code permalink fedilink source parent
[–] Hellstormy@lemmy.world 5 points 2 years ago It's just reverse optimizing! permalink fedilink source parent
[–] marcos@lemmy.world 6 points 2 years ago 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. permalink fedilink source parent
[–] guiguinofake@sh.itjust.works 7 points 2 years ago Pretending I was born 40 years earlier permalink fedilink source parent
[–] embed_me@programming.dev 2 points 2 years ago Doing vector operations because the MCU vendor didn't provide APIs for it. (did not actually do that but was preparing to before we came to our senses and ditched that MCU) permalink fedilink source parent
