"My conclusion is that situation is an existential threat that requires strong, bordering on ruthless, leadership from highly technical people with authority over product decisions."

"In defense of Haskell, the goal is to understand the problem well enough to come up with an as elegant solution as possible. It is a worthy goal, and can be a useful constraint, but a lot of programming falls outside of that goal."

I am not/surprised at how lame the search feature is in Netflix.

Some so-called progress is, I think, not really so much.

https://blogs.gnome.org/mclasen/2013/08/05/scrolling-in-gtk/

I truly, truly despair that we use file name extensions to determine how to interpret the data inside.

If you are making a user interface for a high stress, high throughput situation, where the users are not trained to use your stuff, it would be nice if:

1. When I press on the first button to get started, you don't put up a progress/loading spinny saying "loading". Pre cache the entire UI or at least the first and second pages.
2. When the process of doing whatever it is I have to do is done, you did not then put up 2 pages of loading/finishing before indicating me I can move on in life / the next person who uses the terminal won't get my data (at least in theory, anyway).
3. When you offer controls for modifying hardware, you do not have both virtual and physical buttons and only the virtual buttons work.