agreed, as a person getting a bit older...I'm now having to (somewhat painfully) admit that physical screen size is more important to me than pixel density...
...don't get me started with text using tiny fonts on low contrast backgrounds
Agreed, my beats solo pros always worked fine, until the final firmware update which was conveniently right before they were no longer supported. Upgrade with caution.
I found the book maybe a bit overly optimistic/idealistic about how he thought infrastructure dependencies would impact the world, but a lot of the information was fascinating nonetheless.
"The upshot is: Food safety is a function of both temperature and time.
What the USDA is looking for is a 7.0 log10 relative reduction in salmonella bacteria in chicken. That is, a reduction that ensures that out of every 10,000,000 bacteria living on that piece of chicken to start, only one will survive."
If you are strong at product/program management, there are more technical versions of those positions at larger techs where being able to code, do some UX design, proof of concept work would be useful (i know people in those types of roles at Apple, Microsoft for example).
Or a "Solution Engineer" at an enterprise software/services company could be a fit. This is a role where you may not be working on the core platform, but custom solutions for clients built on top of the platform (hence PM, UX type skills are useful). Sometimes this is in service of sales pitches, other times you are actually implementing the solution.
I have hired for roles like this in enterprise world, but also even for internal platforms at a FANG, i've setup something similar before.
I myself am a sort of jack of all trades for ~20 years now and am a senior engineering manager at a FANG--I've never considered myself to be a particularly strong engineer, but I made up for it in other ways and am technical "enough" to be effective (at least people seem to think so). I've seen others like me be successful (e.g. they are more senior than me now), and some did not even have technical backgrounds, they just "faked it till they made it", but had a good sense of what was important to focus on and not be distracted by technical ratholes.
Like others said, a startup is a good option too--I have been in that type of role in several startups earlier in my career (and have had to hire those types of people before).
Steve Jobs told employees a short story when they were promoted to vice president at Apple. Jobs would tell the VP that if the garbage in his office was not being emptied, Jobs would naturally demand an explanation from the janitor. "Well, the lock on the door was changed,' the janitor could reasonably respond. "And I couldn't get a key."
The janitor's response is reasonable. It's an understandable excuse. The janitor can't do his job without a key. As a janitor, he's allowed to have excuses.
"When you're the janitor, reasons matter," Jobs told his newly-minted VPs. "Somewhere between the janitor and the CEO, reasons stop mattering."
"In other words,' (Jobs continued,) "when the employee becomes a vice president, he or she must vacate all excuses for failure. A vice president is responsible for any mistakes that happen, and it doesn't matter what you say."
https://www.youtube.com/watch?v=EUXnJraKM3k