@[email protected] to Programmer [email protected] • 9 months agoThey had a paid break, right?pawb.socialimagemessage-square57fedilinkarrow-up11.12Karrow-down111
arrow-up11.11Karrow-down1imageThey had a paid break, right?pawb.social@[email protected] to Programmer [email protected] • 9 months agomessage-square57fedilink
minus-squarePM_ME_VINTAGE_30S [he/him]linkfedilinkEnglish19•9 months agoWhat are you doing in assembly?
minus-square@herrvogellink65•9 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-square@[email protected]linkfedilinkEnglish13•9 months agoPut a refactor ticket in the backlog. We’ll get to it eventually, right?
minus-square@marcoslink6•9 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.
minus-square@[email protected]linkfedilink2•9 months agoDoing 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)
What are you doing in assembly?
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.
Suffering.
Assembling.
Pretending I was born 40 years earlier
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)