Oh wow. This hits hard in the feels. Here's my personal submission for "UI problem that has existed for years on touch interfaces, plus a possible solution, but at this point I'm just shouting into the void": https://medium.com/@pmarreck/the-most-annoying-ui-problem-r3... In short, an interface should not be interactable until a few milliseconds after it has finished (re)rendering, or especially, while it is still in…
The curse of knowing how, or; fixing everything
171–180 of 458 posts
Re: The curse of knowing how, or; fixing everything
#172> Burnout does not just come from overwork. It comes from overresponsibility. I don't _think_ it is accurate. I think burnout comes from putting energy into things that don't have meaning. Case in point, this article: as you realize that fixing everything is a never-ending game with marginal ROI, you end up burning out. If overresponsibility alone caused burn out, I think that every parent out there would be impacted…
Re: The curse of knowing how, or; fixing everything
#173Earlier quoted context omitted.
> I have many ideas that I want to build, but I'd have to learn new languages, Why? Why, specifically, do you "have to learn new languages" ? So, sure, I can see that, for some product, you might need to learn a new tech (say ... some specific AWS/GCP/Azure service), or perhaps a new configuration language (YAML, TOML, whatever). And, sure, for some ideas (for example a mobile phone app) you're forced into that speci…
> There is nothing stopping you from implementing your idea in (for example) Python. Or Javascript. Or Java, C#, C++, etc Except there is, my brain :), that's one of the constraints I'm talking about, I'm a frontend web dev and I only know JS/TS, and like some frontend web devs, I'm enamored by Rust because it seems so different. I already use JS/TS at work so I want to use something else for my personal projects. So…
Re: The curse of knowing how, or; fixing everything
#174A good part of that is a disguised sense of superiority. Life becomes way lighter when you realize other people are also smart and what you’re “fixing” can very likely be: - something so unimportant that no one felt it was worthy working on - something that was supposed to work like that, and you simply don’t agree and want to make it your way
Or not. It can be the struggle of having higher than average standards.
Sadly, your list is incomplete without:
- something someone didn't bother to put any effort or thought into at all.
Re: The curse of knowing how, or; fixing everything
#175Oh wow. This hits hard in the feels. Here's my personal submission for "UI problem that has existed for years on touch interfaces, plus a possible solution, but at this point I'm just shouting into the void": https://medium.com/@pmarreck/the-most-annoying-ui-problem-r3... In short, an interface should not be interactable until a few milliseconds after it has finished (re)rendering, or especially, while it is still in…
This happened to my just the other day; I was purchasing something online with a slightly complicated process, from my mobile, I didn't want to f* up the process, and I was tapping occasionally to keep the screen awake while it was doing "stuff"; needless to say, something popped up, too fast for me to react, I have no idea which button I tapped if any, or if I just dismissed it, to this day no idea what it wanted but I know it was related to the payment process.
I've seen this solved in dialogs/modals with a delay on the dismiss button, but rarely; it would also make sense to delay a modal/dialog of some kind by a couple hundred milliseconds to give you time to react, particularly if tapping outside of it would dismiss it.
I find myself using Notification History on Android more and more often, but a lot of the time it's not even notifications, it's some in-app thing that's totally within the developer's control.
Re: The curse of knowing how, or; fixing everything
#176As a non-techie (retired M.D.) who wouldn't know source code from Morse code, reading these comments is extremely absorbing.
Re: The curse of knowing how, or; fixing everything
#177Oh wow. This hits hard in the feels. Here's my personal submission for "UI problem that has existed for years on touch interfaces, plus a possible solution, but at this point I'm just shouting into the void": https://medium.com/@pmarreck/the-most-annoying-ui-problem-r3... In short, an interface should not be interactable until a few milliseconds after it has finished (re)rendering, or especially, while it is still in…
I have another submission for most annoying UI problem: Trying to read a thing, but it's on medium.com. The sheer amount of popups and overlays I need to click away before I can actually read your thing, geez.
Re: The curse of knowing how, or; fixing everything
#178As a non-techie (retired M.D.) who wouldn't know source code from Morse code, reading these comments is extremely absorbing.
Do you perceive this as a tech-specific thing though? I'm a software engineer but this resonates with me more within other aspects of life in general than my professional background specifically.
edit. OK, I just went back and reread the parent post and now I understand what you're asking. I do agree with you, this is generalizable across the board: file under the old saw "Perfect is the enemy of good."
edit #2. Also applicable, from Alfred Korzybski's classic 1933 book "Science and Sanity": "When in doubt, read on." I've always generalized this statement (which I first encountered around 1968 while an undergraduate at UCLA when reading his book not for a class but because I had gone down a wonderful rabbit hole after learning about Korzybski and his huge influence at the time he was alive ) to all things that puzzle me or cause me to stop moving toward whatever it is I'm aiming at.
edit #3: PDF for Korzybski's book:
https://archive.org/details/alfred-korzybksi-science-and-san...
Re: The curse of knowing how, or; fixing everything
#179Oh wow. This hits hard in the feels. Here's my personal submission for "UI problem that has existed for years on touch interfaces, plus a possible solution, but at this point I'm just shouting into the void": https://medium.com/@pmarreck/the-most-annoying-ui-problem-r3... In short, an interface should not be interactable until a few milliseconds after it has finished (re)rendering, or especially, while it is still in…
I have another submission for most annoying UI problem: Trying to read a thing, but it's on medium.com. The sheer amount of popups and overlays I need to click away before I can actually read your thing, geez.
I consider UBO basically mandatory for browsing the web in 2025, too many sites are unusable and infuriating without it.
Re: The curse of knowing how, or; fixing everything
#180As I'm getting older, I want things to be as standardized as possible, and just don't worry about the details. I have learned from my mistakes The script I made for deployment, because existing solutions didn't "feel" right, required a lot of work and maintenance when we later had to add features and bug fixes. Another script I made for building and deploying Java applications, because I didn't like Maven and Puppet.…
I also think there is a profoundly non-linear relationship (I don't want to say negative-exponential, but it could be), between:
- The number of lines of code, or distinct configuration changes, you make to the defaults of an off-the-shelf tool
- The cognitive and practical load maintaining that personalized setup
I'm convinced that the opportunity cost of not using default configurations is significantly higher than we estimate, especially when that environment has to be shared across multiple people.
(It's unavoidable or even desirable in many cases of course, but so often we just reinvent hexagonal wheels.)