Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Always Be Coding – How to Land an Engineering Job

medium.com

Post reply on HN
Print view View original

31–40 of 250 posts

Re: Always Be Coding – How to Land an Engineering Job

#32

Post by 31reasons »

davidbyttow wrote: post #30
31reasons wrote: post #25

Earlier quoted context omitted.

I feel exactly the same. I can master any and all graph algorithms under the sun if I want to but why? Just for a job? I would rather be building things.

The idea is to get in the door. Unfortunately, the bouncer is extremely flawed and often gets it wrong. But once you're in, you should refocus on building things.

I just don't have that much drive to get a job. Maybe I underestimate getting a job at google or similar company.

Re: Always Be Coding – How to Land an Engineering Job

#34

Post by javert »

> “On a scale of 1-10, 10 being the highest, how would you rank your knowledge of C++?” ... Bjourne Stroustrap himself would rate himself probably an 8 or less.

Is there a citation for this, or a citation for something similar, or is this just a guess?

If it's actually true, then score++ for people who complain that C++ is too complex.

Re: Always Be Coding – How to Land an Engineering Job

#35

Post by kamaal »

31reasons wrote: post #25
nbroyal wrote: post #16

To properly prepare for these interviews you have to invest quite a bit of time. At this point in my life (late 20s), my time is one of my most valuable resources. So, the last thing I want to do is spend that time effectively preparing for a data structures and algorithms exam. Each time I sit down to brush up on the details of Prim's algorithm or the exact implementation of quicksort, my eyes glaze over and I start…

I feel exactly the same. I can master any and all graph algorithms under the sun if I want to but why? Just for a job? I would rather be building things.

Adding to that its not ever worth that much trouble.

    1. Master algorithms.
    2. Get a job at .
    3. ???
    4. Get rich.
What exactly is 3) ???.

Really if you are joining a big company. Whatever that company is. Way to financial safety is not mastering algorithms and data structures. Its more like knowing how to do politics, being your manager yes men etc.

And very rarely are you ever going to get some work where its going to demand some algorithms mastery.

Re: Always Be Coding – How to Land an Engineering Job

#36

Post by wging »

davidbyttow wrote: post #31
pvdm wrote: post #29

Log(1)=0 If you interviewed once and got the job, your score would be 0.

Intentional. The idea is that 1/1 could be a fluke. :-)

For x == 0, this also blows up.

And for x > 1, which base you use matters. E.g. if x == y == 2,

    >>> from math import log,e
    >>> 100 * log(2,2)
    100.0
    >>> 100 * log(2,e)
    69.31471805599453
    >>> 100 * log(2,10)
    30.102999566398115
I'm aware it's meaningless, but which base did you intend? :)

Re: Always Be Coding – How to Land an Engineering Job

#37

Post by kamaal »

31reasons wrote: post #32
davidbyttow wrote: post #30

Earlier quoted context omitted.

The idea is to get in the door. Unfortunately, the bouncer is extremely flawed and often gets it wrong. But once you're in, you should refocus on building things.

I just don't have that much drive to get a job. Maybe I underestimate getting a job at google or similar company.

The only problem with big companies is, no matter who they are on an average large set ups are almost the same. There are some minor variations here and there. But your net experience will converge or move around the same point.

I don't know much about Google. But from whatever I've heard. The awesome projects where all this nirvana level work happens are very difficult to get into and bulk of the work is really maintaining legacy system.

Or in other words, its your usual large company. There is a possibility that the experience is marginally better. But as I said will on a average converge to any large corporate experience.

Re: Always Be Coding – How to Land an Engineering Job

#39

Post by 7Figures2Commas »

callmeed wrote: post #11
dsowers wrote: post #7

You can build a startup in the time it takes to thoroughly prepare for these interviews/positions. Willingly subjecting yourself to this rat race is essentially the same thing as stamping yourself as an "ibm man," in the words of Jobs. Who cares if you don't know the intricacies of all the hot algorithms of the day. Spend your time creating actual value for the world, instead of practicing just for the sake of impres…

This seems silly. If nothing else, following the advice here will help you hire better engineers for your own startup.

Really?

Most true startups are in need of developers who can actually ship something of value in an efficient manner. The last thing they need is an "engineer" obsessed with algorithms and data structures who turns a practical development task into a computer science challenge.

Post reply on HN