5 ms·

when you make a post about software quality but did not test it on enough browsers to realize your constant width font ascii art is not rendering correctly in f

when you make a post about software quality but did not test it on enough browsers to realize your constant width font ascii art is not rendering correctly in firefox or chrome, so the user has to grab an invisible scrollbar to see the picture... zooming out of course doesn't work.

adityaathalye 3y ago
One of the little ironies of life. I know about this (and some other annoying problems), and have been meaning to fix the typography on my site for a long while. But that would draw me into a rabbit hole of some other improvements I want to make to my site maker. And that will be, well, there's an xkcd for it. Two actually. Automation: https://xkcd.com/1319/ https://xkcd.com/1319/ Efficiency: https://xkcd.com/1445/ https://xkcd.com/1445/
- adityaathalye 3y ago
  P.S. Also, I did not tell them to make invisible scroll bars (nor have my CSS rules, as far as I can tell)!
  - mdaniel 3y ago
    I think some of the bad outcome may be due to macOS being sneaky with the scrollbar display <https://support.apple.com/guide/mac-help/change-appearance-settings-mchlp1225/mac#:~:text=Show%20scroll%20bars https://support.apple.com/guide/mac-help/change-appearance-s...>, but your style.css for sure isn't helping matters with its overflow: specifications. The tradeoff, as best I can tell, is whether macOS folks get hidden scrollbars (I don't know anything about the zoom complaint, since I'm on desktop) versus omitting the overflow: and having the asciiart clip outside of its bounding box due to some other CSS interaction that I didn't bother to track down https://www.evalapply.org/static/css/style.css#:~:text=overflow-x%3a%20hidden https://www.evalapply.org/static/css/style.css#:~:text=overf... and https://www.evalapply.org/static/css/style.css#:~:text=overflow-x%3a%20auto https://www.evalapply.org/static/css/style.css#:~:text=overf...
    - adityaathalye 3y ago
      Thank you for taking a look. I will take a look at overflow behaviour, which I don't understand too well. I think I need to take a step back and work out responsive behaviour in general. Sadly management's hands have been tied and there is not time to make small useful improvements :)
  - doubloon 3y ago
    ok well this is why quality sucks in software, you dont have to theorize, you have an example right in front of you that you personally are involved in. same with me and everyone else who writes code. i have stuff i know i should fix but it would lead me down a rabbit hole so i dont. so where is this experience in our theoretical framework?
    - adityaathalye 3y ago
      Purpose matters, I suppose. I write for myself. My site is a public extension of that writing (there are so many notes on my computer I may never publish). I've made no promises about the quality of work to anyone, and I get by just fine with what I have. It is available on a "take what is useful, discard the rest" basis. If I were writing for an audience I might prioritise things differently.

adityaathalye 3y ago

One of the little ironies of life. I know about this (and some other annoying problems), and have been meaning to fix the typography on my site for a long while. But that would draw me into a rabbit hole of some other improvements I want to make to my site maker. And that will be, well, there's an xkcd for it. Two actually. Automation: https://xkcd.com/1319/ https://xkcd.com/1319/ Efficiency: https://xkcd.com/1445/ https://xkcd.com/1445/

adityaathalye 3y ago
P.S. Also, I did not tell them to make invisible scroll bars (nor have my CSS rules, as far as I can tell)!
- mdaniel 3y ago
  I think some of the bad outcome may be due to macOS being sneaky with the scrollbar display <https://support.apple.com/guide/mac-help/change-appearance-settings-mchlp1225/mac#:~:text=Show%20scroll%20bars https://support.apple.com/guide/mac-help/change-appearance-s...>, but your style.css for sure isn't helping matters with its overflow: specifications. The tradeoff, as best I can tell, is whether macOS folks get hidden scrollbars (I don't know anything about the zoom complaint, since I'm on desktop) versus omitting the overflow: and having the asciiart clip outside of its bounding box due to some other CSS interaction that I didn't bother to track down https://www.evalapply.org/static/css/style.css#:~:text=overflow-x%3a%20hidden https://www.evalapply.org/static/css/style.css#:~:text=overf... and https://www.evalapply.org/static/css/style.css#:~:text=overflow-x%3a%20auto https://www.evalapply.org/static/css/style.css#:~:text=overf...
  - adityaathalye 3y ago
    Thank you for taking a look. I will take a look at overflow behaviour, which I don't understand too well. I think I need to take a step back and work out responsive behaviour in general. Sadly management's hands have been tied and there is not time to make small useful improvements :)
- doubloon 3y ago
  ok well this is why quality sucks in software, you dont have to theorize, you have an example right in front of you that you personally are involved in. same with me and everyone else who writes code. i have stuff i know i should fix but it would lead me down a rabbit hole so i dont. so where is this experience in our theoretical framework?
  - adityaathalye 3y ago
    Purpose matters, I suppose. I write for myself. My site is a public extension of that writing (there are so many notes on my computer I may never publish). I've made no promises about the quality of work to anyone, and I get by just fine with what I have. It is available on a "take what is useful, discard the rest" basis. If I were writing for an audience I might prioritise things differently.