@willya@lemmyf.uk to Programmer Humor@lemmy.mlEnglish • 1 year agoLeave it alonelemmyf.ukimagemessage-square56fedilinkarrow-up1823arrow-down131
arrow-up1792arrow-down1imageLeave it alonelemmyf.uk@willya@lemmyf.uk to Programmer Humor@lemmy.mlEnglish • 1 year agomessage-square56fedilink
minus-square@pearsaltchocolatebar@discuss.onlinelinkfedilink44•1 year agolooks at the startup scripts I just took from a 2h runtime to 15m Guess I gotta revert those changes.
minus-square@Moops@lemmy.worldlinkfedilinkEnglish20•edit-21 year agoI mean, runtimes can be a legit reason to say something’s not working.
minus-square@pearsaltchocolatebar@discuss.onlinelinkfedilink14•1 year agoBut it does work. Eventually. Really, I fixed it because we’re doing an OS upgrade and I didn’t want to wait 2h every time I spun up a new instance to test a change.
minus-square@FiskFisk33@startrek.websitelinkfedilink1•1 year agothat’s the problem with the ‘its working’ argument. if you hadn’t touched the working code you might have missed the performance issue to begin with.
looks at the startup scripts I just took from a 2h runtime to 15m
Guess I gotta revert those changes.
I mean, runtimes can be a legit reason to say something’s not working.
But it does work. Eventually.
Really, I fixed it because we’re doing an OS upgrade and I didn’t want to wait 2h every time I spun up a new instance to test a change.
that’s the problem with the ‘its working’ argument.
if you hadn’t touched the working code you might have missed the performance issue to begin with.