meandthewallaby

They're all easily solvable problems. The issue, as GP mentioned, is that the pennies are just stopping without the thought through these problems and planning for the solutions. This was done via a social media post, not a well thought out transition like Canada had.

I assume you're just correcting capitalization, but for clarity's sake, the aforementioned Bitcoin mines are in west TX, the region with oil derricks, wind turbines, and tumbleweeds, and not West, TX, the town with the Little Czech Stop and delicious kolaches.

I'm a fellow Kingdom resident -- there are plenty of ski hills between here and Boston. The ones closer get more play. Stowe is a bigger resort, and it gets more play. Less so between here and Montreal, but there's ski hills north of Montreal that are closer. A place like Littleton, just beyond Cannon Mountain, _is_ brimming with customers every long weekend. Jay (and Burke, which is _really_ a locals' mountain) are very much in the in-between.

Because of the curse of the autodidact, do note that "ennui" is pronounced "on-wee," as it comes from French ("ennui" is "boredom" in French). It is not, as I found out rather embarrassingly, "en-you-eye".

Incidentally, I agree with you. While there could be some editing for length (oh well), the point was well made with a great example to start out with, and a bit of a discussion about some of the effects of being trapped in the Ennui Engine. It definitely hit on something I've noticed about myself.

I have a pile of books I've been meaning to read but haven't gotten to. I have lots of articles that I'd like to read but haven't made time yet. But I'd pull up Reddit and just scroll there. I deleted Twitter when Elon bought it and decided to burn it to the ground, and I'll be deleting Reddit now. Not so much to make a stand, but really just using this opportunity of upheaval as a way for my old head to extricate itself from the Ennui Engine.

The article states that if there are multiple moves the engine recommends, that they all count as the "optimal" move, even if there's an indication of preference by the engine.

Like with most things, it depends! Maybe it's a default value; maybe it's a null; maybe it's a special value that triggers a workflow on insert. I'm an evangelist for RDBMSes, and they can do so much, so let them help you!

Maybe you have a state column that's derived that you cannot move to another step in the workflow until all nulls are filled in, but you've let the UI save what data it knows about and move on. It totally depends on what the user is doing and why we're skipping steps/data.

In my experience, the software development profession could spend a long, long time doing some self-reflection about this one. It's eloquently stated, and something a lot of developers could learn. Too many times, I've seen overly restrictive inputs cause users to hate and distrust the software. Ironically, overly restrictive inputs cause users to think that the software doesn't properly understand the domain, which is the root of mistrust.

We should be very liberal with accepted inputs. I call them "Fuck It Buttons." There are lots of cases where you want a "Fuck It" button to just go around all the data entry and get an answer or move on with minimum info. Warn that the data isn't complete and we're using defaults, and don't just make output look the same as a complete workflow, but let them go through, nonetheless. Health care is just one example, but "Fuck It" comes up in every industry.

This is the UI/UX equivalent of knowing which hills to die on.