Google/Trax – Understand and explore advanced deep learning

Re:Google/Trax – Understand and explore advanced deep learning by WnZ39p0Dgydaz1 on Monday February 17, 2020 @03:29AM (#22346326)

The error message have always been an issue, even with early releases. That being said, it was much easier to trace errors when there were fewer high-level functions and you had to build the layers yourself. You fully understood what the graph looked like, and it was mostly obvious where something is likely to go wrong.

Sure, it's a bit more work, but in the long run it saves times because it avoids the situation where you need spend half a day trying to understand opaque TF code touched and extended by 100 different developers.

EDIT: Also, I LOVE the Github issue you posted. It's such a beautiful example of complexity cost when a large number of people is working on a project and there's no longer a single person that fully understands how code interacts across modules.

[ Parent | on HN ]

Re:Google/Trax – Understand and explore advanced deep learning by logicchains on Monday February 17, 2020 @03:50AM (#22346403)

I'd love to know what the solution is to prevent that eventually happening to a project, if one even exists. PyTorch seems to be doing better, but maybe that's just because it's a younger project. I'd be interested to see a blog post comparing Facebook's incentive structure for maintaining products to Google's.

[ Parent | on HN ]