"Best" in this case depends on your needs and resources, not on standards or common practices. Flexibility and "getting the job done" are more important than what everyone else prefers. Do what works for you.
I don't understand the issue. If I ask a robot to get me a drink, how is that any different from me going and getting it for myself? Either way, it's my decision (bad as it might be), and I need to take responsibility for it. How does being disabled -- to whatever degree -- change that? If this were a mental or emotional issue, that might be different. But it isn't. Physical impairment doesn't change one's responsibility for one's own decisions.
Like most such things, it depends on who you talk to, and also your specific situation. I've had bosses that valued general skills and bosses that looked for specific toolsets. The good ones value what the job requires.
'Washington should be very thoughtful how they go forward here,' he said. 'This uncertainty is not good for investment, and it's not good for jobs here in America.'" It's SO nice to realize that they have their customers' best interests in mind...
I know, I know -- they have to make a profit. But it would be nice if someone would realize that net neutrality is about fairness to the consumer, not about maximizing corporate profits.
Bifocal and trifocal lenses were (and are )intended for situations where the eye is frequently shifting from near to far focal distances; the near focal range is at the bottom because, usually, the closer things are, the lower in your field of view they are likely to be. (Yeah, I know; "Tell me something obvious now.") Progressive lenses take this one better, in that they have a smooth change of focus as your eyes rotate up or down, rather than a step shift.
But in looking at a computer monitor, the whole view field is at a single distance, or at least nearly so; also, at least half of what you see is at or above the middle of your field of view, right where bifocals and trifocals go to "long distance" focus, so you find yourself tipping your head back to get the near focus, and your neck gets real tired, real fast. Best bet? Measure how far your monitor is from your eyes, in normal position, and tell your optometrist you want single-focus reading glasses adjusted for that distance, and don't let him (or her, as the case might be) talk you out of it. They'll cost less and work much better for you than progressive lenses -- but only in this limited case. So, once you have them, use them ONLY when working at your computer.
Most of the comments I see (level 4 or higher) talk about compensation. I come at this from another direction: Productivity.
I generally work hard enough (assuming there is work to do) that if I go over 45 hours a week, I start getting tired, leading to both slowing down and making more mistakes. In general, if I work 50 hours, I produce about the same net worth as if I had worked 40; if I work even more, it just gets worse. Fortunately, I've almost always had bosses who understood this, so it hasn't been an issue. I really feel sorry for those of you who can't say that.
After 10 years in IT, you should already have a good answer to your own question. If you don't, you may already be too far behind the curve. Look at your peers; in particular, look at what the successful ones know that the others don't.
You should understand how computers work. You should understand how systems talk to each other. You should understand how to communicate what you want to the computer. The more of this you do, in fact, know, the better off you'll be in the future. Try to learn it ALL; you won't, but the closer you get the better off you'll be.
Of course, when you start getting close enough to stand out, either you'll be running your own company successfully, or you'll be wondering why those whippersnappers around you are waiting for you to fall over dead. Whatever you do, don't spend your money just because you have it. Either gamble big and win (i.e., get the Big Bucks for designing and building the Next Big Thing) or save carefully so that you won't be depending on Social Security (or the current equivalent when you get that far) to pay for your food, clothing, and shelter.
This has been my experience as well -- although, to be fair, it's been a while since I actually got "RTFM" as an answer. (It's just as well; my response would probably have been, "That's fine, but which FM should I be R'ing?")
To answer the OP's question about what I do: I generally use Google, with as many key words as I need to use to refine the links returned. As an example, when I ran into a problem with not being able to enable my speakers, I Googled "[sound subsystem] speakers not found" and rummaged through the links returned until I found a workaround. That was a year or two ago, BTW, and the problem still hasn't been fixed properly, but at least the workaround is still good. And, yes, I did notify the package owner about what I found. Not only didn't he fix it, he never replied. But at least I had the satisfaction of knowing I'd done what I could.
To give you an idea of what I' want to do, I used to do graphical UI work for a small VAR company selling PC systems in the pre-Windows world;I really loved that, until they were bought out by a competitor and I had to switch fields (to telecomm, not that it matters). Now that I'm no longer doing telecomm, I'd like to go back to graphics, but everything I knew then is decades out of date.
What I'm really looking for is the Linux equivalent of the Microsoft Visual C IDE. I liked the way I could use it to create a window object, add the bells and whistles I wanted, and then pull up the code in the editor and start adding the "under the hood" code to do what I really wanted. I've tried a couple of Linux IDEs, but the ones I've used so far either are buggy, have little or no documentation, or otherwise leave me floundering helplessly. What I really need is a mentor of some kind, but not having any human ones around, I have to rely on software. Can anyone help me get started?