Have you actually worked in a programming role before? Googling things is absolutely the norm. Most people don’t know every single in and out of every library/framework they’re using, especially when learning new ones. This goes double for more complex or sprawling frameworks where it may be less than obvious how to perform a particular task from the documentation alone or when running into undocumented limitations or bugs (although admittedly an in-IDE assistant won’t be too useful for that anyway).
what have you worked in the same language for twenty years? I don’t have all the libraries memorized and not only do new ones get created but formats change. Unless I have been using something recently I always check.
There are a lot of offline doc downloaders, man pages, books, even raw repositories to make sure that you’re independent and can work offline or without a VPN to the company.
And again, I was only saying that only juniors do google searches all the time. When you get some experience, you have broader tasks like adding features, debugging, handling the architecture, or refactoring that require less google stuff.
I mean debugging and adding features is coding and debugging im even more likely to look up the things im looking at since I did not write it myself. I honestly rarely use man pages except for linux commands when im at the command line atm. Architecture usually is usually has its own team outside of the lowers.
Have you actually worked in a programming role before? Googling things is absolutely the norm. Most people don’t know every single in and out of every library/framework they’re using, especially when learning new ones. This goes double for more complex or sprawling frameworks where it may be less than obvious how to perform a particular task from the documentation alone or when running into undocumented limitations or bugs (although admittedly an in-IDE assistant won’t be too useful for that anyway).
I’ve been coding for more than 20 years. Googling things is the norm but not the job. You should have all your docs and API stored offline anyway.
The guy said going back and forth with a search engine. That’s what juniors do, not software engineers.
what have you worked in the same language for twenty years? I don’t have all the libraries memorized and not only do new ones get created but formats change. Unless I have been using something recently I always check.
There are a lot of offline doc downloaders, man pages, books, even raw repositories to make sure that you’re independent and can work offline or without a VPN to the company.
And again, I was only saying that only juniors do google searches all the time. When you get some experience, you have broader tasks like adding features, debugging, handling the architecture, or refactoring that require less google stuff.
I mean debugging and adding features is coding and debugging im even more likely to look up the things im looking at since I did not write it myself. I honestly rarely use man pages except for linux commands when im at the command line atm. Architecture usually is usually has its own team outside of the lowers.