cool thing had the same idea but never published it, funny how often you google the same thing? like "explode in js" ;)... i never deactivated the complete history of google since it exists.
Everything I googled in a week as a professional software engineer
211–220 of 399 posts
Re: Everything I googled in a week as a professional software engineer
#212Re: Everything I googled in a week as a professional software engineer
#213This is great but the premise seems kind of straw man. I don’t know a single developer that thinks “googling stuff means you’re not a proper engineer.” Perhaps this is a reference to the interviewing process. Tests are a different thing, though. I’ve been on practical technical screens where you can google, because the test was about building a larger system, and they don’t care if you don’t remember this or that API…
Googling too much is an indicator that your environment or process isn't working well. It's not a point of pride if half your job requires looking up how to use tools you don't understand.
The problem is that people naturally blame themselves for not knowing everything rather than accepting that we have built monuments of trash code that nobody should be expected to understand and that therefore we should stop doing that and stop using that.
Re: Everything I googled in a week as a professional software engineer
#214Longer I work as a developer less frequently I google stuff. Most times I use google to find a project on Github and read docs. If I google for something specific then it is for finding better solution.
That implies you are not learning new things, or you are getting that info from books or some other source. Or you bookmark all docs pages or something?
Re: Everything I googled in a week as a professional software engineer
#215And yet there are coding interviews that expect candidates to write complex regex expressions from memory
Regex is one of those things I have memorised albeit without the back reference stuff I rarely use. I think it’s worth memorising and if you use it to help you find replace in your editing you soon will.
Re: Everything I googled in a week as a professional software engineer
#216This is great but the premise seems kind of straw man. I don’t know a single developer that thinks “googling stuff means you’re not a proper engineer.” Perhaps this is a reference to the interviewing process. Tests are a different thing, though. I’ve been on practical technical screens where you can google, because the test was about building a larger system, and they don’t care if you don’t remember this or that API…
Googling too much is an indicator that your environment or process isn't working well. It's not a point of pride if half your job requires looking up how to use tools you don't understand. The problem is that people naturally blame themselves for not knowing everything rather than accepting that we have built monuments of trash code that nobody should be expected to understand and that therefore we should stop doing…
I think compounding the issue is a lot of devs jump complex technologies pretty quickly so we're constantly trying to overcome a deficit in knowledge but never stopping long enough to do so.
Re: Everything I googled in a week as a professional software engineer
#217Earlier quoted context omitted.
Concrete example: I know gradle, and pretty well at that. I had to learn the basics of maven to develop a Jenkins plugin (at work). Developing jenkins plugins for a long time required using maven. Now there's the option for using gradle, but my recollection was that it was a sub-par experience.
Afaict, everything just relies on Maven and its packages as the backbone. At least, after any sort of Java-dev activity I risk discovering 1.5 GB of Maven's package cache in my home dir.
The maven package format is the defacto standard in the java world. Luckily gradle consumes and publishes in that format too.
Re: Everything I googled in a week as a professional software engineer
#218"professional software engineer"
> writing cookies
> string contains
> how to see request headers in chrome
I mean, obviously I'm trying to be snarky here, but I'm not sure how a professional "software engineer" focused on web development types such generic queries into the browser after working on it long enough to be "professional".
Re: Everything I googled in a week as a professional software engineer
#219I’ve been writing JavaScript for at least a decade now (way before all of these fancy frameworks, build systems, etc.), and yesterday, I googled “JavaScript addEventListener” so that I could remember how to use it. I’d love for someone to tell me that I’m not a “proper engineer” because of that!
Its forgivable because with software dev the gigabytes per year of new information to remember in your head is much higher than other disciplines. It’s darn ridiculous!
Re: Everything I googled in a week as a professional software engineer
#220This is probably a 10-50x fewer searches than I do in a week. I am assuming there are many searches left out. I'd be interested in seeing how the OP tweaks their searches as the results don't return exactly what they want. Here is an actual single search progression for me (In reverse order because copy/pasta :shrug: react context optimize rerender "props.children" react context optimize rerender react usereducer dis…
could you give an example of a complex search? I've never bothered using advanced Google search patterns
It is pretty dependent on what the search results look like after the first search.
In the above example, I would probably filter out results having to do with other react hooks so adding `-useState` would help accomplish that. If I am googling specific syntax or an error log, then wrapping it in quotes will do a phrase match and filter out results that don't contain the phrase.
I don't use the `site:` search pattern because just adding `github` does a good enough job and
Another pattern I use is `filetype:pdf`
:thinking: and lastly I nearly always use the tools to filter by results within the past year. That does an okay job filtering out older documentation, tutorials, articles etc