Everything I googled in a week as a professional software engineer
111–120 of 399 posts
Re: Everything I googled in a week as a professional software engineer
#112This 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…
I definitely felt proud of myself for passing, especially when the other 6 senior linux admins all failed because they were too arrogant to study or prepare.
Re: Everything I googled in a week as a professional software engineer
#113Earlier quoted context omitted.
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.
at least arm and mips both match x86 (right? unless I forgot. probably I forgot, it's been over a decade)
Re: Everything I googled in a week as a professional software engineer
#114Earlier quoted context omitted.
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.
at least arm and mips both match x86 (right? unless I forgot. probably I forgot, it's been over a decade)
Re: Everything I googled in a week as a professional software engineer
#115This 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…
Re: Everything I googled in a week as a professional software engineer
#116This is a really interesting peek into the developers mind. Right away I notice I google things differently than the author. I try and hit up phrases that match a question (which is why I probably over index on stack overflow). The author seems to hit up ideas that remind me of something that might be the title of a blog post or something. Also, my search is definitely more full of stack trace keywords. Probably 80%…
It's very barebones MVP at the moment, but you can expect more features very soon. Open to feedback!
Re: Everything I googled in a week as a professional software engineer
#117On 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.
touch
$EDITOR
mv
cp
scp
mount
The place you're putting something is last in each case; we can even include everything that doesn't modify its location.All I can think of that breaks the rule is `rm`, `unlink`, and `umount`. But they're hardly gotchas, and they're not reversing arguments they just don't have a 'destination'.
Re: Everything I googled in a week as a professional software engineer
#118This 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…