4 ms·

I've been following the technology my whole career. I am still employable, but it gets old. My advice to younger devs is to focus on general computer science

by snarfy 10y ago

I've been following the technology my whole career. I am still employable, but it gets old. My advice to younger devs is to focus on general computer science fundamentals and application development skills. Those are the only skills that stay with you and grow as your career advances. The technologies always change so don't memorize them. Keep a reference around instead. Memorize things like design patterns and sorting algorithms.

Thaxll 10y ago
Sorting algorithm you serious? No one uses that in his carreer.
- metaobject 10y ago
  While this is for the most part true, questions regarding sorting algorithms and data structures (debug this left-rotate function that operates on binary trees) still come up during interviews.
- nsxwolf 10y ago
  You need them for those whiteboarding tech interviews.
  - BipolarElsa 10y ago
    Why the fuck is the hiring culture in programming to test candidates on something they rarely use if ever over the course of their career? What kind of insanity is this? Do they ask psychiatrists how to perform surgery during hiring interviews? Give me a break.
  - amyjess 10y ago
    I misread that as "waterboarding tech interviews", and I thought it was commentary on how whiteboard interviews feel like torture.
- sulam 10y ago
  I mostly agree, however there are exceptions that prove the rule. Some engineers are working on standard libraries. (someone has to write that code!) Some people are taking advantage of their data set to write special-purpose sorting algorithms that blow generic algorithms out of the water. (guilty!) Some people are putting stuff together in interesting ways that requires them to understand and sometimes even re-implement the standard algorithms to take advantage of internal data structures or other interesting effects. (It's bad practice, but knowing the order a map will iterate things in can be helpful if you don't expect it to change -- and make sure to have a unit test that proves it!)
- dgacmu 10y ago
  Just to prevent rampant over-generalization in an article whose subject is the topic of bias: We've implemented various special-purpose sorts at least three times in the last five years. Here's one example: https://github.com/efficient/cuckoofilter/blob/master/src/packedtable.h#L95 https://github.com/efficient/cuckoofilter/blob/master/src/pa... Yes, this is all in a very high-performance (sometimes insanely so) context, but it does happen. Most of them were like this - unrolled special-purpose versions derived from a sorting network. Some were for GPU.

by snarfy 10y ago

Thaxll 10y ago

Sorting algorithm you serious? No one uses that in his carreer.

metaobject 10y ago
While this is for the most part true, questions regarding sorting algorithms and data structures (debug this left-rotate function that operates on binary trees) still come up during interviews.
nsxwolf 10y ago
You need them for those whiteboarding tech interviews.
- BipolarElsa 10y ago
  Why the fuck is the hiring culture in programming to test candidates on something they rarely use if ever over the course of their career? What kind of insanity is this? Do they ask psychiatrists how to perform surgery during hiring interviews? Give me a break.
- amyjess 10y ago
  I misread that as "waterboarding tech interviews", and I thought it was commentary on how whiteboard interviews feel like torture.
sulam 10y ago
I mostly agree, however there are exceptions that prove the rule. Some engineers are working on standard libraries. (someone has to write that code!) Some people are taking advantage of their data set to write special-purpose sorting algorithms that blow generic algorithms out of the water. (guilty!) Some people are putting stuff together in interesting ways that requires them to understand and sometimes even re-implement the standard algorithms to take advantage of internal data structures or other interesting effects. (It's bad practice, but knowing the order a map will iterate things in can be helpful if you don't expect it to change -- and make sure to have a unit test that proves it!)
dgacmu 10y ago
Just to prevent rampant over-generalization in an article whose subject is the topic of bias: We've implemented various special-purpose sorts at least three times in the last five years. Here's one example: https://github.com/efficient/cuckoofilter/blob/master/src/packedtable.h#L95 https://github.com/efficient/cuckoofilter/blob/master/src/pa... Yes, this is all in a very high-performance (sometimes insanely so) context, but it does happen. Most of them were like this - unrolled special-purpose versions derived from a sorting network. Some were for GPU.