Hacker Newsnew | past | comments | ask | show | jobs | submit | tempw's commentslogin

where is the "PowerPoint" though?


  Location: Western Europe (EU).

  Remote: Yes/Enjoy in-office but remote preferred if possible.

  Willing to relocate: Open to discuss.

  Technologies: Focused on Machine Learning Python based frameworks/libraries as TensorFlow and NumPy.
  I have experience as well in Full-Stack development mostly in React/Node/MondgoDB.

  Résumé/CV: Please request via email. You can find some of my work/code on github.com/carmezim.

  Email: hackernewshire@gmail.com


Based on your reasoning PyTorch is copying TensorFlow static optimizations and production capability with JIT and ONNX then? I've seen many folks requesting an imperative API.

You can't please everybody, as if they listen or not to users people still complain. If both are making effort to improve themselves though, the community has only to benefit from this competitiveness.


Which license is PyTorch?


PyTorch itself isnt, But the multi-GPU version requires Gloo which is BSD+PATENTS

https://github.com/facebookincubator/gloo/blob/master/PATENT...


PyTorch uses NVIDIA NCCL for multi-GPU communication (under BSD license). Gloo is only one of the three backends that can be used for distributed communication out of the box.


Thanks!


It's sad one needs to reinforce the teaching of concepts rather tricks.

Even worse is when you have all the proof based and concept oriented course and are tested on trickeries on exams.


I believe this is a huge shortcoming of how math is taught. You can bet your last dollar that the teacher doesn't think it's about tricks. But the students are convinced that it is. Students and teachers are both exposed to the exact same material but end up with diametrically opposing conclusions.

Disclosure: I taught college freshman math for one semester, long ago. It was a course where I was supplied with a syllabus and exams, and the students could buy a packet of exams from previous years.

The tricks are what you remember from doing problems over and over, and recognizing patterns. There is also a higher level pattern that isn't mentioned in class, but is vital to solving problems: You learn to identify each problem with a particular chapter or section in the textbook, and then solve the problem by recalling the methods in that section. This is of course a grotesque distortion of what math is, but will get you through the lower level college math courses with good grades.

The other skill is being able to perform the manipulations quickly enough that you can try one or two before hitting on one that works.

Disclosure: I taught college freshman math for one semester.


My high school calculus teacher was really great at this. He didn't just teach a bunch of transformations to memorize. That was part of it, naturally, as you aren't going to use the definition of limits and the FToC in all your problem solutions. He actually made us construct volumes from pieces of poster board, measure the segments and calculate the Riemann sum. When we did function analysis, he didn't allow us to use the Cartesian plane at first. We had to show visually how a function deformed the one-dimensional real line. How x^2 squished values between -1 and 1 toward 0 and stretched the other values toward +infinity.

It gave me a good "visual" grasp of the concepts and made most of my higher math classes much easier.

I do agree diff eq instruction sucks. I got an A in that class and didn't understand a thing. "This equation has this form; this is the canned solution."


This is true, a lot of short term "friends" you make along the way but a few days later each one goes their way and also it becomes a bit of a repetitive process and can be quite exhausting. It'll depend on your personality mostly but for an introspective it can get tiring. Helps if you visit friends/family from time to time.


my bad, ESL, thanks for your "grammatical" rewording though.


Nah no worries, we're delighted that HN has users from many nations. And it wasn't my rewrite, I stole it :)



I am not the author, just to clarify that.

I think the point here is more about how experienced programmers track records are not enough to prove they can do the work sometimes.

Using whiteboard questions to prove ones competency can backfire as well in cases candidates are not really prepared but learned to game the system.


The real problem with whiteboard tests (and it's close cousin, the live coding test) is there is no correlation between being able to pass that test and being able to do the job. Companies that rely on it to determine programming ability are like the drunk looking for his keys under the street lamp because that's where the light is.


"no correlation"? Nonsense. If you can't program a computer, I'll find that out. And if you can't program a computer, you wouldn't be able to do the job.

The point of my coding interview isn't to give a positive result if the candidate can program a computer. It's a test that's looking for non-programmers.

There might be "false positives", but if I avoid well-known memorizable questions, there won't be "false negatives".


There will be false negatives too, but most likely not related to the skills but something else, like mental health or work ethic.


On the fast ring Go 1.8 and Haskell are running okay as well as inotify working.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: