3 ms·

Are you saying that using Google to answer a question is more exhausting than parsing a book? That makes zero sense

yamtaddle 3y ago
> Are you saying that using Google to answer a question is more exhausting than parsing a book? That makes zero sense My point is that we couldn't possibly do our jobs now without Google, but that we used to be able to do it just by knowing the stuff in a few books really well and knowing where—in the books or in e.g. manpages—to find what we didn't know. A small shelf of books is way better than Google, if you can be reasonably certain that the answers you need are in there. Yes, this situation is far more exhausting.
- dawatchusay 3y ago
  Yeah you couldn’t do you job without Google because it’s vastly superior to a shelf of 5 books
  - yamtaddle 3y ago
    That very much depends on what you're doing. The existence of Google has brought about the expectation that we do our work in a way that requires Google.
    - dawatchusay 3y ago
      I think Google is a net positive
  - zamnos 3y ago
    How much is on Google itself vs Google search linking you to, eg, StackOverflow. A side question: how much of your job could you do only referring to https://devdocs.io/ https://devdocs.io/ or other reference?
twh270 3y ago
For me, the part that's most exhausting is the constant struggle to remain competent with the ever-changing landscape of frameworks, libraries, and services that are used in modern software development. This is made worse by their size and scope. Spring Boot is a giant ecosystem, as is .NET, as is Azure, etc. Also, search results tend to be a sea of data which might, or might not, contain some crucial bit of information that will help. So, all too often, "using Google to answer a question" becomes a 2-hour or day-long research project to figure out how to solve some small, arcane problem like why the POST to some service doesn't have the Authorization header. And when there's internal and external pressure to be productive, meet deadlines, and not feel incompetent, sometimes it gets frustrating and stressful and tiring.

> Are you saying that using Google to answer a question is more exhausting than parsing a book? That makes zero sense My point is that we couldn't possibly do our jobs now without Google, but that we used to be able to do it just by knowing the stuff in a few books really well and knowing where—in the books or in e.g. manpages—to find what we didn't know. A small shelf of books is way better than Google, if you can be reasonably certain that the answers you need are in there. Yes, this situation is far more exhausting.

dawatchusay 3y ago
Yeah you couldn’t do you job without Google because it’s vastly superior to a shelf of 5 books
- yamtaddle 3y ago
  That very much depends on what you're doing. The existence of Google has brought about the expectation that we do our work in a way that requires Google.
  - dawatchusay 3y ago
    I think Google is a net positive
- zamnos 3y ago
  How much is on Google itself vs Google search linking you to, eg, StackOverflow. A side question: how much of your job could you do only referring to https://devdocs.io/ https://devdocs.io/ or other reference?

twh270 3y ago

For me, the part that's most exhausting is the constant struggle to remain competent with the ever-changing landscape of frameworks, libraries, and services that are used in modern software development. This is made worse by their size and scope. Spring Boot is a giant ecosystem, as is .NET, as is Azure, etc. Also, search results tend to be a sea of data which might, or might not, contain some crucial bit of information that will help. So, all too often, "using Google to answer a question" becomes a 2-hour or day-long research project to figure out how to solve some small, arcane problem like why the POST to some service doesn't have the Authorization header. And when there's internal and external pressure to be productive, meet deadlines, and not feel incompetent, sometimes it gets frustrating and stressful and tiring.