And yet there are coding interviews that expect candidates to write complex regex expressions from memory
Everything I googled in a week as a professional software engineer
41–50 of 399 posts
Re: Everything I googled in a week as a professional software engineer
#42In this type of job, at this level of complexity, we just can't hold it all in our minds.
It's too much, and it changes all the time. We need a near-telepathic reference to get the necessary info when required. Thankfully, we have that and it makes the job possible.
Re: Everything I googled in a week as a professional software engineer
#43On the list of things I always Google, is how to create a symbolic link under Linux. I just can't figure out a way to remember what comes first; the source or the destination. The man pages add to the confusion by calling the "source" the target. So, the rule of thumb I now follow is cp or mv semantics.
i've personally given up on this after googling it a dozen times and now i just cd into the target directory first and omit it
Re: Everything I googled in a week as a professional software engineer
#44this is shockingly relatable. not only the same type of things i google in an average day, but some of the exact same queries.
Re: Everything I googled in a week as a professional software engineer
#45My web search activity went up a lot with experience. Back in the day, almost all of my work consisted of cranking out stuff in the main language (PHP or Python), spiced up with SQL and occasional web or db server setup. I needed manuals sometimes, but not web searches so much. After the hipster-programming/devops explosion of the early 2010s and my dive into highly optimized heterogeneous solutions, the work switche…
Why would you learn Maven AND Gradle? Pick one.
Re: Everything I googled in a week as a professional software engineer
#46"Never memorize something that you can look up." -Albert Einstein edit- Had to look up who actually said this
"Unless you have a technical interview coming up" -me
IMO technical interviews should give you a terminal with Google. And ask questions that can't be answered without it. It's a more business-valuable skill than memorizing things / having had experience with some specific technology and its problems.
Re: Everything I googled in a week as a professional software engineer
#47That list of things reads like a bad cliche of the narrow view mindset in some of SV that doing web development somehow amounts to software engineering.
Web development, unless you’re doing something novel, is not software engineering. Getting some hodge-poge of react drivel to work is not engineering no more than configuring a router is software engineering.
Choose your words with more precision.
Re: Everything I googled in a week as a professional software engineer
#48I forget syntaxes of various languages or language features, so it's really handy that emacs can show them to me from stackoverflow with completion:
Re: Everything I googled in a week as a professional software engineer
#49On the list of things I always Google, is how to create a symbolic link under Linux. I just can't figure out a way to remember what comes first; the source or the destination. The man pages add to the confusion by calling the "source" the target. So, the rule of thumb I now follow is cp or mv semantics.
I couldn't remember also.
The way I finay did it was to memorize 'ln -s -T' -T stands for target that way... I know the next thing must be the target then the source.
Re: Everything I googled in a week as a professional software engineer
#50On the list of things I always Google, is how to create a symbolic link under Linux. I just can't figure out a way to remember what comes first; the source or the destination. The man pages add to the confusion by calling the "source" the target. So, the rule of thumb I now follow is cp or mv semantics.
[deleted]