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 agree, cs needs a split in roles kinda like nurse and doctor.
Everything I googled in a week as a professional software engineer
91–100 of 399 posts
Re: Everything I googled in a week as a professional software engineer
#92On 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.
Given the number of things that use different source vs destination with the same type, I just have trained myself to always look it up, even if I am 99% sure I remembered it correctly, because holy shit when you get it wrong sometimes it's bad. softlink dest file cp src -> dest std::memcpy dest java arraycopy src -> dest golang io.Copy dest etc etc I'm only 80% confident I didn't make an error in the above 5 example…
Re: Everything I googled in a week as a professional software engineer
#93Re: Everything I googled in a week as a professional software engineer
#94Re: Everything I googled in a week as a professional software engineer
#95This 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've met lots of younger devs who have varying degrees of impostor syndrome, so anecdotes like this probably help people like that feel less bad about not knowing everything.
Re: Everything I googled in a week as a professional software engineer
#96Earlier quoted context omitted.
Given the number of things that use different source vs destination with the same type, I just have trained myself to always look it up, even if I am 99% sure I remembered it correctly, because holy shit when you get it wrong sometimes it's bad. softlink dest file cp src -> dest std::memcpy dest java arraycopy src -> dest golang io.Copy dest etc etc I'm only 80% confident I didn't make an error in the above 5 example…
Intel assembly: mov dest, src AT&T assembly: mov src, dest Whenever I'm debugging at the assembly level I have to just write down the appropriate one on a piece of paper in front of me.
Re: Everything I googled in a week as a professional software engineer
#97The author states : What I’m trying to show with all this is that you can do something 100 times but still not remember how to do it off the top of your head.
My experience differs from this, if I were to rewrite it I would say something like:
"You can do something 100 times, and as long as you can look it up somewhere, it is okay to not memorize how to do it."
You have to evaluate the impact on your flow of stopping to look something up, you have to evaluate what you consider your 'base' skill set is to evaluate if you should memorize something.
Before Google, the canonical case here was arithmetic. Who needs to memorize multiplication tables if you have a calculator handy to do simple arithmetic. Basically if you cannot do basic arithmetic in your head, you are always going to be at a disadvantage with respect to someone who can.[1]
I have found a reasonable compromise, when I Google something like this, I write down the solution in an Evernote notebook that I keep for such things. So if the same question comes up I can always find the answer and don't have to have either the web page or Google around to get to the answer.
[1] And as a "magic trick" you can hand a cashier what appears to them to be an odd amount of money, only to have them discover when they enter it into their register the change is a minimal number of coins/bills.
Re: Everything I googled in a week as a professional software engineer
#98Earlier quoted context omitted.
Ahaha, if it were that simple...
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.
Re: Everything I googled in a week as a professional software engineer
#99That "Provisional headers are shown" Chrome message drives me crazy. Some time ago, I was able to disable some flags which made it go away temporarily, but now it's showing again, presumably after Chrome made some changes. It's a problem because it means that it's not showing the real request headers. Does anyone know how to fix this for good?
Re: Everything I googled in a week as a professional software engineer
#100This is a fun exercise, then ask the second question "How productive can I be in my job when the network is unavailable?" The author states : What I’m trying to show with all this is that you can do something 100 times but still not remember how to do it off the top of your head. My experience differs from this, if I were to rewrite it I would say something like: "You can do something 100 times, and as long as you ca…