thothsscribe

If they use any table or any of the features where there are a group of objects (pages) that have different status or properties, they are using databases.

It's pretty much something you accidentally create and use in notion without knowing unless all you are doing is writing documents.

Definitely back-end and it is exciting to see all that UX is bringing to CLIs, but relative to a full front end GUI it is much more straight forward. (Not to discount the hard work CLI developers do since it is still plenty complex)

That was a well written and entertaining article. A bit long for my taste and I feel like it could have been said in fewer words, but like I mentioned, it was entertaining.

What this makes me wonder is how much effort should go into each User Interface. You describe a web GUI (in this domain) to be a good place for people to learn about something new and maybe kick the tires. It can also speed up their interactions via visual tricks. However, you mention that productive, at scale, and "more money" use occurs more in the CLI. Does that mean companies should make their UI better at educating the CLI and worry less about doing things in it and make the CLI be the encouraged primary form of "Doing"?

On top of that, making a GUI requires front end/backend development, UX, visual, research, and a whole lot of time while a CLI requires UX (maybe) and backend development and is overall simpler. I feel like the positives and negatives described in this article don't really support making a UI do anything more than discovery and education on the CLI. And CLI are finally attempting UX improvements like your example from Yeoman. They are taking the best bits from the Usability of GUI (color, shapes, iconography, recommendations, etc)and putting them in the CLI. Does that diminish the relevance beyond education and marketing of a GUI in this domain even further?

Based on this description, why did you spend that much money for an apple watch? Pebble time gives to everything you just said, but saves you 100 bucks and you have to charge it once a week.

My history may be flawed, but doesn't IBM have a strong history of working for human rights from women to disabled to whatever race?

They recently updated their design thinking process. Pretty much the same thing, but more focused on iterative approaches?

So IBM just happened to target the same guy three times? Not disagreeing that IBM has had issues with hiring/firing, but three times seems like an insane coincidence.

IBM has hundreds, if not thousands, of products that they own and maintain. Understand that the research for a design, designing it, and then developing it takes months to years to accomplish. IBM won't be able to update all of their products, but they will work on the ones that they can and then carry design consideration to all new products. Thats all a company can do. Same goes for Microsoft, Google, etc. IBM is a bit late to the game is their only issue.

Also consider, how are they going to get designers/people who care about design if they don't advertise it first. Yes there are products that need work, but to fix that issue they need to say Design 37 and more times just to get the attention of the right people. I am sure in your line of work as well, things don't just happen immediately because you want it to and sometimes to solve one problem you need to solve two or three others first.