It's amazing, that they still expect you to know stuff from memory when you go for those stupid coder-pad interviews or whiteboard sessions
Everything I googled in a week as a professional software engineer
51–60 of 399 posts
Re: Everything I googled in a week as a professional software engineer
#52My 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.
Ahaha, if it were that simple...
Re: Everything I googled in a week as a professional software engineer
#53On 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.
It is like `cp`.
It isn't just like `cp`, on some systems `ln` is just a symlink to `cp`! `cp -s` does the same thing as `ln -s`, although the other flags are generally different.
Re: Everything I googled in a week as a professional software engineer
#54On 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.
What came first: the file or the symlink? Of course the real file came first! Mnemnic that helps me: IN SYMLINKS, REAL FIRST! ln -s REAL_FILE link_name
[deleted]
Re: Everything I googled in a week as a professional software engineer
#55On 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.
fwiw, I always say outloud in my head "thing that exists first" -- but I did need a mnemonic. Somehow I didn't realize it was just cp semantics.
Re: Everything I googled in a week as a professional software engineer
#56I love this.
It funny how much background knowledge is required to know what to google.
Re: Everything I googled in a week as a professional software engineer
#57Everytime I try to google what I need, I end up with postgres documentation about SQL features. But I'm in the guts of the C API. So off to postgresql sourcecode I go
Re: Everything I googled in a week as a professional software engineer
#58That 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.
Ironically, your comment is an example of a narrow view mindset that software engineers who work on React and Javascript are somehow not equivalent to "real" engineers. I don't think that's a balanced view in an industry where a large percentage of companies have web-related products and employ engineers to work on them.
Re: Everything I googled in a week as a professional software engineer
#59Surprisingly educational, in a way.
Re: Everything I googled in a week as a professional software engineer
#60That 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.
I notice that developers do you really like to mention quite often that they are "engineers".