yvsong

I wonder if the Feynman diagram is the supreme data visualization.

I should have limited my comments to mobile listeners with mid to low impedance headphones (which are the vast majority). I used to listen to iPhone with HD 580 (300 ohm) directly, with full volume and no amplifier/equalizer. It's loud enough for sensitive ears, and very enjoyable, better than HD 558. With amplifiers the sound is a little better, but not worth the inconvenience. For mid to low impedance headphones, amplifiers are often used to improve sound quality, not volume. Software equalizers (like those in Songza) would work well, and further shrink the market of amplifiers. Remember that in this mobile internet age, the American consumers have voted for Beats, I'm not sure what for, perhaps the overall user experience.

I learned a similar lesson in another domain.

Songza's headphone-specific equalizer made my Sennheiser HD 558 on iPhone much more enjoyable with the profile for HD 580. Hope they provide a profile for HD 558. Hardware headphone amplifiers are obsolete. Software equalizers are the solution.

Very impressive and helpful data/charts in the KPCB report. That being said, there is a saying on Wall St that if an economist (or anyone) could predict future, she wouldn't need any employment. One usually gets wiser as she ages, but I don't think predicting future is easier than 15 years ago.

The most influential Chinese entrepreneur Jack Ma (founder of Alibaba) commented recently in China that his primary impression of USA was the ability of strategic thinking. Being very familiar with both countries, I have the same impression. I used to call it rational thinking. In my observation, the best strategic thinkers will win the long term races of the countries, as well as businesses.

For commercial apps one needs to buy data. Personal projects can use free data from some websites. I have ideas (and others' suggestions) to improve the UI of the app, but decided to pursue other directions.

My biggest pain when programming servers in Go is when handling others' dynamic JSON. Multiple levels of switch-case to handle different types for the same JSON fields at different times. With the current eco systems, Objective C seems the best language, dynamic typing with optional static typing, or mostly static typing in the programs, with dynamic typing for cases like handling dynamic data. Other goods include ARC, Xcode, Apple's frameworks, etc. Concurrency seems to work well with dispatch queues etc. I wonder if Objective C could be as good as Go for servers.

Another thought: Is the distribution the consequence of natural selection/evolution? Does it mean that hackers are losers in the survival game?

Who are "hackers" here? Software engineers?

Curious about the type distribution of IT entrepreneurs (founders, co-founders, CEO's, and CTO's).