201–210 of 399 posts
1) What ‘level’ of engineer do you consider yourself to be, and does your employer consider you to be? (for example, do you have employees who are junior to you) 2) What’s your income from that job? 3) Do you think that income is fair and appropriate?
Apologies for the deep-dive in to details you may be uncomfortable sharing, they are important context that very few people share.
Earlier quoted context omitted.
> how to create a symbolic link under Linux. I just can't figure out a way to remember what comes first Remember it like this: It's the same syntax as "cp". To copy a file you use "cp source dest". It's the same for ln: "ln -s source dest"
I always think of links as pointing from source to destination. Your way would break that intuition for me. It would be the source of the address and the destination for the address to be copied to.
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.
I’ve asked pre-internet programmers and they said they used to keep reference books at their desk or even a small library/book room at their employers. I’ve heard some government contractors can’t google because they work on non-internet connected computers. They probably keep a lot of books.
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.
Well, you're linking TO something and not FROM something so target seems more accurate(they are essentially pointers). I'm honestly surprised about the help confusion though: ln --help Usage: ln [OPTION]... [-T] TARGET LINK_NAME (1st form)
This 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…
could you give an example of a complex search? I've never bothered using advanced Google search patterns
Example: site:news.ycombinator.com -inurl:item google operators
Earlier quoted context omitted.
> But having a deep understanding of data structures (not just arrays and maps) and algorithms really gives you a mastery of your craft, especially around performance and scalability. Can you give an example?
Ok.. Find all the words that match a search string prefix. I.e. you have a search field and want to show the possible matches as you type. With each new char you’re calling this search and getting back a list of words. The dictionary is in memory in whatever data structure you choose. You only have to return matches if the search is 3 or more chars long. Now, how does your implementation scale when the dictionary has…
Of course that doesn't mean you shouldn't know how advanced data structures work and be able to work with them, it just means you shouldn't reach for say, a fibonacci heap before you just use an array.
This 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…
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.