The first thing that users that recently switched to Keras mention to me is the productivity boost. In the time it would have taken them to debug their way through the implementation of one idea (`zero_grad()` anyone?), they can try out 2, 3 ideas.
-
-
Show this thread
-
It matters because trying more ideas (with fewer mistakes) means you will converge faster towards better ideas (thus winning competitions more often or increasing your paper acceptance rate). I'm thinking Kaggle kernels or Colab would be a way to gather hard data on this...
Show this thread
End of conversation
New conversation -
-
-
Hard to remove newbie correlation with poor tooling though ?
-
This Tweet is unavailable.
- Show replies
New conversation -
-
-
I think it’s all about there being enough documentation that highlights what a productive work flow looks like. This allows developers to iterate on what has worked well for others to find what works best for them. Your book Deep Learning with R/Python is a great example imo.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I found using high level framework ultimately you ran into a case where it doesn’t quite support it with ease. This is where a flexible versatile framework can distinguish itself. Easy of extension and good doc r two key things.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
In my own experience, productivity goes down in proportional to how novel your idea is. As you are get close to bleeding edge, you have to go under the hood, do lot of hacks, etc. A hard to extend framework will really drag you down. So it depends on where u “sample” this.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.