Brain pain

The textbook Iโ€™m reading now.

This is my leisure reading at the moment. Itโ€™s a good break from routing protocols. Some major parts I only understand about 50% of. Thatโ€™s ok. I donโ€™t plan on actually being a biomedical engineer. And Iโ€™ve never taken any course or read any lower-level textbook on this.

I just like to know things.

The parts on kinematical gait analysis are the most interesting so far, though I only understand about 20% of the math in that particular section. If I had any ability at all at math I wouldโ€™ve been truly intellectually formidable. But, alas, and such.

For some lighter reading, I also read the Southern Reach trilogy recently. Itโ€™s worth reading, but it didnโ€™t go far enough or deep enough with what it was attempting to do.

โ€œThe biologistโ€ is a great character, though. Both of them.

Youโ€™ll see what I mean if you read it.

Icons

Computer geeks like to claim that they use icons in the interfaces these days instead of words because โ€œicons are universal.โ€

The problem is that icons are not universal. Very much not. When Iโ€™ve done intensive tech support in the past most users had no idea what 99% of icons meant, while they could almost always pick out key words like โ€œPrintโ€ and โ€œSave.โ€

The real problem is laziness and management attempting to save money by avoiding translation of an interface into many languages.

Icons are only universal among the 1-2% of very tech-savvy users out there.

For others, they are almost all indecipherable and probably always will be.

This โ€œicons are universalโ€ claptrap is one of the biggest myths in UX, and a persistent one at that, because it allows executives to skimp on good design.