25 ms·

Were you reading the same article as me?

ckdarby 12y ago
I don't think they were ._.
Rong1961 12y ago
I think they were. They're being sarcastic, and commenting on how the end of the article puts the coder into a junior position and puts the math expert into a senior position.
- lbarrett 12y ago
  I dunno, a programmer who can't think about algorithmic complexity isn't actually going to be all that useful.
  - waterlesscloud 12y ago
    How useful is the guy who thinks about algorithmic complexity but doesn't code? At the end of the day, someone's got to write the code that runs on your servers. It doesn't magically transfer from that paper covered in pencil markings. The actual conclusion of the piece made sense to me- all 3 were worthy of offers, for different reasons. Not hiring all three has less to do with how good the economy is (that was a non-sequitor) and more to do with the needs of the particular company at this particular moment. Right now they need people to design algorithms and to code. They need both, and their company doesn't advance if they only have one and not the other.
  - Shivetya 12y ago
    depends on what they work on, business applications in large organizations we tend to direct programmers through reams of project documentation, from top level to familiarize them with what the overall direction is to technical documents which specify exactly the formulas to be used at all levels of calculation. These formula and related specification does include the number of decimals to use within calculation, rounding, and resulting decimal precision. yeah its nice if they understand it all but programming isn't all shoot from the hip, many work in very structured environments which is more true when projects can have more than a dozen programmers on just one machine. Throw in three or more touch points and I am more concerned you follow the technical than branch out with your own ideas
ilikevideos 12y ago
That's the same interpretation I had. Because the guy didn't know quant he would therefore be in a junior role for something unrelated to quant.

I don't think they were ._.

Rong1961 12y ago

I think they were. They're being sarcastic, and commenting on how the end of the article puts the coder into a junior position and puts the math expert into a senior position.

lbarrett 12y ago
I dunno, a programmer who can't think about algorithmic complexity isn't actually going to be all that useful.
- waterlesscloud 12y ago
  How useful is the guy who thinks about algorithmic complexity but doesn't code? At the end of the day, someone's got to write the code that runs on your servers. It doesn't magically transfer from that paper covered in pencil markings. The actual conclusion of the piece made sense to me- all 3 were worthy of offers, for different reasons. Not hiring all three has less to do with how good the economy is (that was a non-sequitor) and more to do with the needs of the particular company at this particular moment. Right now they need people to design algorithms and to code. They need both, and their company doesn't advance if they only have one and not the other.
- Shivetya 12y ago
  depends on what they work on, business applications in large organizations we tend to direct programmers through reams of project documentation, from top level to familiarize them with what the overall direction is to technical documents which specify exactly the formulas to be used at all levels of calculation. These formula and related specification does include the number of decimals to use within calculation, rounding, and resulting decimal precision. yeah its nice if they understand it all but programming isn't all shoot from the hip, many work in very structured environments which is more true when projects can have more than a dozen programmers on just one machine. Throw in three or more touch points and I am more concerned you follow the technical than branch out with your own ideas

ilikevideos 12y ago

That's the same interpretation I had. Because the guy didn't know quant he would therefore be in a junior role for something unrelated to quant.