5 ms·
> should never update a user interface without allowing the previous one to be used as the default I don’t understand why people are so precious about their UI
by chrisseaton 6y ago
> should never update a user interface without allowing the previous one to be used as the default
I don’t understand why people are so precious about their UI and workflow. They obviously managed to learn and adapt to the current UI. Why can’t they adapt to a new one?
If you’re super sensitive to something as trivial as a change to a menu location maybe that’s a sign you should be automating whatever your workflow is.
- egypturnash 6y agoI don't understand why programmers are so precious about their choice of text editor. They obviously managed to learn and adapt to their current choice. Why can't they adapt to a new one?
- chrisseaton 6y agoWell I guess you’re trying to mock me but I also agree with this.
- egypturnash 6y agoI was attempting to reframe your question to apply to a rough guess of who you are, and what tools you spend most of your life using, based on the fact that you are (a) commenting on HN, and (b) display no sympathy with the plight of a user who's had the UI they stopped having to think about ages ago suddenly change out from under them. Probably with deadlines looming that have no room for "everything takes twice as long for a while while we get used to the new setup and the fact that one key we regularly hit as part of the process now deletes half our work". Is that mocking you?
- smabie 6y agoI mean, a lot of programmers have spent their entire lives either using Emacs or vi keybindings. It's pretty unreasonable to ask them to change. Mentally switching to an entire different set of editing commands is incredibly difficult and time consuming. I've been using Emacs for over 15 years and I don't know any other keybindings. If I had to switch to vim, it might take me years to get comfortable.
- pseudalopex 6y agoThat's the point.
- hyperman1 6y agoFunny. I'm trying to adapt my Java workflow from eclipse to idea. Again. And I know that almost everyone agrees idea is better than eclipse. And some of eclipse's major features are broken enough to actually hamper me professionally - looking at you, maven integration. And both tools seem at least equally capable, just everything is named different and placed somewhere else. But eclipse is now about 20 years ingrained in me. So every 1-2 years I try to live with idea for a month or so. Sometimes even compromising by switching to the eclipse keybindings. And I know my productivity will drop while adapting. So I sweat on that bloody superior idea interface for 2 weeks, then some super hot emergency drops in, and I do 'only this one' in eclipse. Then switch back to idea. After 2 of 3 emergency's, I give up and go back to eclipse. See you next year, idea. I know this is stupid. I'm happy using emacs, vscode, notepad++, even vi, for almost every other programming language, except Java. This can't be healthy. And yet...
- saagarjha 6y agoFor me InyelliJ just can’t get it quite like how I have Eclipse set up, and it’s somehow uglier than Eclipse…
- apricot 6y agoHey, you know your car that you brought in for an oil change? I switched the turn signal controls with the wipers. No charge, and no givebacks.
- chrisseaton 6y agoI really think I could adapt to that easily and wouldn’t mind.
- thedanbob 6y agoThen you are in the minority. Most people like having certain predictable arrangements in their life and get annoyed when they have to adjust to a new arrangement arbitrarily. Maybe that's actually not the case for you, but I suspect it is more than you think, and I guarantee it is for 99% of people in general.
- smabie 6y agoHow about gas and break being switched? That really wouldn't cause problems for you?
- nottorp 6y agoYou may remember when you don't need to pay much attention, but will fail in a complex situation where you neeed the turn signals most. Because you're paying attention to other things in traffic.
- apricot 6y agoI didn't choose my example at random. See, I drove a rental car in Japan once. Since they drive on the left, I knew the driver seat was on the right, but what I didn't expect was the controls also swapped sides. I had, without a doubt, the cleanest windshield in all of Hokkaido.
- II2II 6y ago> They obviously managed to learn and adapt to the current UI. Why can’t they adapt to a new one? Let me put it like this: would you rather relearn the same skill over and over again, or build upon existing knowledge by learning new skills? Watch an experienced vi user make changes to a document. That's not magic that you're seeing, it's someone who is modifying a document as fast as they can think because they are proficient with the software. That's true of pretty much any software that was designed with productivity in mind, it's just that vi users like to show off. :) Some software is also impossible to learn in depth if you take a learn today, gone tomorrow approach. Consider a rather popular application like Microsoft Word. There was a lot of resistance to the transition to the ribbon bar. A good number of people who resisted the change did so because they spent a great number of years learning the program in depth. There's a lot of stuff crammed in there that the vast majority of people aren't even aware of and even experienced users will only touch on every few years. With timescales like that, a sufficient number of changes to the UI means that the skill is useless once it has been learnt.
- fogetti 6y agoImagine that they upgrade the touch UI in your car, and it's a complete redesign, but only on one specific screen in a sub-sub-sub-menu which you usually only open while driving. Now you are speeding with 150km/h down the highway and voila, the screen is gone (it's there in fact, but it's not the same screen any more). Have fun poking with this new updated UI and workflow. BTW, this example is exaggerated of course, but not completely unrealistic, and it's easy to find similarly disruptive situations triggered by a UI or workflow change.
- jacquesm 6y agoOh, you are far closer to reality than you think, this isn't all that exaggerated. One particularly memorable instance of this was OTA update of on-board controller in a vehicle, while in motion! Fortunately we spotted it during DD, the consequences could have been terrible.
- spaetzleesser 6y ago"I don’t understand why people are so precious about their UI and workflow. They obviously managed to learn and adapt to the current UI. Why can’t they adapt to a new one?" Why constantly adapt to a new UI that does the same thing in a different way? That causes a lot of mental churn without any benefit.
- scintill76 6y agoWell, why don't you automate this? https://twitter.com/ChrisGSeaton/status/1234924701513900032 https://twitter.com/ChrisGSeaton/status/1234924701513900032 You're annoyed about "[using] up precious minutes of [your] life" when you're in the middle of typing a command and have to context-switch to skimming some barely-related information to accomplish something that should be simple. That's how many of us here feel when we're trying to get a familiar task done, but the UI is frequently reorganizing itself, so we have to stop and look around for something that should be simple. (Let it be a sign of how bothered I was by your cavalier attitude, that I dug through tweets.)
- chrisseaton 6y ago> by your cavalier attitude I’m literally a cavalier so that’s fine by me.
- taneq 6y agoSomebody sneak into this guy's office and move his 'debug run' key from F5 to F9.
- chrisseaton 6y agoI don’t use keyboard shortcuts TBH.
- ziml77 6y agoIf you're not using keyboard shortcuts, then there's much less ingrained in your muscle memory. You're using more conscious effort to perform tasks which means that when something changes you don't need to put forth extra effort to override the subconscious. That gives you more adaptability, but the downside is lower efficiency in terms of both speed and energy expenditure.
- chrisseaton 6y ago> That gives you more adaptability Right and also less time rote learning cryptic key combinations like I’m learning a book of spells. > but the downside is lower efficiency in terms of both speed and energy expenditure Thinking time is 99% of computer time in my experience. Keep brain space for that rather than the magic key spells, is my philosophy.
- deleted 6y ago[deleted]
- smabie 6y agoHow do you program without any keybindings?
- taneq 6y agoVery slowly, I assume. From their profile, they do research so maybe they do spend all their time thinking about code rather than writing it, which is great for them, but doesn’t reflect what the vast majority of devs do.
- FpUser 6y agoBecause for the most cases it is just a friggin' tool and routine the user had accustomed to. I do not want to hunt for the same item in a different place. Think of it as if your screwdriver used daily will have suddenly started to change shape every once in a while.
- chrisseaton 6y agoMost people aren’t really complaining the new UIs are worse - they just don’t like any change at all. It’s silly stubbornness.
- beckingz 6y agoIf the UI is just different and not substantially better, that is bad. Learning a new interface takes effort.
- qu4z-2 6y agoThe GP isn't saying the new screwdriver handle is worse either, just changing repeatedly.
- PeterisP 6y agoYes, that's kind of the point - we're not saying that the new UI is worse, we really are saying that without a good reason/benefit, we don't like any change at all. By default, changing the expected behavior is bad, there needs to be some benefit that justifies the change. It's not silly stubborness, it's pointing out that it is harmful and counterproductive to disrupt people's workflow. Variety is nice in food and entertainment, but in productive workflow predictability, reliability and lack of variety are very, very valuable. Saying "the new UI isn't worse" is not sufficient - is the new interface significantly better? Was the change required to enable something that I want which wasn't possible with the old interface? In that case, sure, make the changes - but not otherwise. Every change in the interface that's not 100% backwards compatible incurs a nonzero cost, effort and inconvenience. Sure, people can and will adapt, but requiring them to adapt requires them to spend a scarce, valuable resource - attention. If a tool doesn't do the expected thing right away because it has changed, then it has failed, it has distracted the user at a time when they wanted to do something else instead of playing with the tool. That's the key difference between a toy and a tool; a toy is useful for it's own sake and should draw attention to it, while a tool is useful for doing particular things and must get out of the way, allowing the user to focus on the job or the product instead of the tool.
- EvanAnderson 6y agoWhen a new UI trashes my workflow-- particularly when the new UI is slower / lacks keyboard shortcuts / causes my old workflow to do something different and unexpected-- I feel exceedingly disrespected by the programmer. I'm the user. I matter. Without users your software means nothing. Don't be a jerk to your users.
- Multicomp 6y ago> I don’t understand why people are so precious about their UI and workflow. We develop such strong preferences with workflows because for these programs, we are using the computer not to be amazed and dazzled with the device itself (like we are with blu-ray movies, PC games, the Mystery screensaver), but to get things done. From programming, to CAD, to video editing, to writing, to budgeting and more. Would you like it if your car buttons moved around on the dashboard for no reason? Rebuttal: Tesla has most stuff in dashboard, controls move around. Counter-rebuttal: that guy who crashed his car trying to figure out how to turn on the wipers. Would you like it if your thermostat settings were not remembered? Rebuttal: updates don't necessarily mean that settings are lost. Counter-rebuttal: I concede that, but often them being lost is the case. Would you like it if you learned to play a musical instrument and one day you picked it up to find out it had added/removed/multiplied/moved valves/strings/keys/reeds?
- ericbarrett 6y agoThe UI is a physical interface between human and computer. It's a representation of tools. A direct analogy here is to physical tools. Imagine you were a carpenter, on a tight schedule and with commitments to deliver. Every few months, you walk into your workshop, and not only have your tools been rearranged, some have been swapped out for different sizes, and some even removed outright. How is "automate it" a good response here? Also, what automation would you propose that handles these changes without introducing its own update requirements? If it's a macro tool separate from the application, the macro targets may well have changed, had additional parameters added or removed, etc. You'll have to run through them all to ensure they still work, with test cases ready ahead of time, or else you've lost just as much time. And if it's automation in the program itself, like a scripting language, said automation may just as easily be broken or removed by the updates.
- qppo 6y agoThe problem is not changing the menu location but telling people where the new location is while incurring the lowest operational overhead. Teaching people new things is expensive, especially if you already taught them how to do it a different way. Think of all the support tickets that come in with a menu change and the fact that even minor UI updates will require updates to training documents or e-learning materials. Yea it's easy for one person to learn and move on. It's expensive for hundreds of people to do the same thing at the same time because you moved a form to a different tab in the dashboard and no one reads docs.