5 ms·
A favorite HN comment of mine from a few years back (https://news.ycombinator.com/item?id=21590482 https://news.ycombinator.com/item?id=21590482): > Outside of
by jonah-archive 3y ago
A favorite HN comment of mine from a few years back (https://news.ycombinator.com/item?id=21590482 https://news.ycombinator.com/item?id=21590482):
> Outside of fundamentally better workflow improvements, most professional fields don't randomly change their tools. If you gave a professional artist a new pencil that had to be gripped differently for no reason, they'd throw it in the trash.
>
> But in software, we tolerate buggy tools that change all the time for no discernible reason. We tolerate software that simultaneously targets professionals and casual users, serving both segments poorly. We tolerate software that can't be customized or adapted for specific workflows. It's tough to put into words, but if you watch a musician or a painter interact with their tools, there's a very clear difference that emerges, and over time you start to realize how much better all of their stuff is.
>
> In most professional artistic settings, workflow changes only happen because they have a clear benefit -- drawing from your shoulder instead of your wrist, changing your embouchure if you play an instrument. And even in those fields, it's generally accepted that over time people will end up with very specialized setups that are very consistent and refined and that remain constant for years and years.
>
> Only in the software industry would someone tell me that my professional tools should change because change is inherently good. Only in commercial software would an elegant, consistent interface like Markdown that allowed me to build up decades of muscle memory until my computer was an extension of my fingers and I didn't need to think about the way I typed -- only in software would that be considered a bad thing.
- jimbokun 3y agoThat also speaks to the enduring appeal of tools like vi and emacs.
- jimnotgym 3y agoThe converse story is all the people that complain about $enterprise_software saying things like, it hasn't had an update since 1996!
- kortilla 3y agoThose are people who don’t use it judging by superficial things.
- Gustomaximus 3y agoThere is middle ground between doing significant changes all the time and no changes in ~30 years. I was working at a software company years back that was doing this significant interface change. I suggested we have an 'end goal' interface and breakdown changes into multiple releases over time, organised it so each version change is easier to adapt to and educates somewhat in the changes as they occur, but this approach got no traction. I still wonder if its the correct approach or its better to get it over with in one go and then try to be stable.
- bombcar 3y agoAt least in my experience the “one and done” feels better, but make it so the new one is somehow faster or easier or something. (Not salesforce lightning, e.g.) The other ends up feeling like death by a thousand cuts.