141–150 of 399 posts
Earlier quoted context omitted.
I'm of the opinion that not googling stuff means you're not a proper engineer. And from what I've seen, those who don't google consistently also fail to understand the answers they find when they do google things. It is, in fact, an essential skill.
Why not Yahoo?
This 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…
> I don’t know a single developer that thinks “googling stuff means you’re not a proper engineer.” I see it at least a couple times a week on sub-reddits related to software development. Junior devs who are convinced more senior developers are super-geniuses who know everything from memory.
That 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.
That 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.
But I wouldn’t call myself an engineer for swapping a wheel on my car.
But I would call myself an engineer if I were responsible for a small business making car wheels, even if we were not doing any R&D.
My 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.
Earlier quoted context omitted.
Isn't that what a whiteboard interview is? Proving you can do things without google or else you aren't a proper engineer? (For the record I disdain whiteboard interviews as the accepted metric for testing one's ability)
Every engineer on HN (several threads that I've browsed) seems to have a serious disdain for coder-pad interviews/whiteboard sessions. And I think HN has a good representation of software engineers. So, who are these companies hiring?
> css and javascript > professional software engineer Pick one.
On 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'm honestly surprised about the help confusion though:
ln --help Usage: ln [OPTION]... [-T] TARGET LINK_NAME (1st form)
I often search for "X sucks" to see if others agree with me that X indeed sucks.
That 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.