You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
If a third party writes buggy code and it involves a Keras model, that's not "a bug in Keras", for Christ's sake
Just for the record, trainable weight tracking in custom layers works fine and has always worked fine. You can test it yourself, it takes 7 lines of code. Custom layers with trainable weights are used in countless workflows. Can't believe I have to say this
That said, it's generally good practice to write unit tests for your layers, that test basic assumptions: number of weights, number of trainable weights, output shape, test that the layer produces the same output after deserialization, etc. It enables you to catch common mistakes
So do, in fact, check it yourself, via a unit test -- it's never wasted time. For any codebase that's actively maintained, you should always aim for 100% coverage
Unit tests are the most useful maintenance tool there is -- they enable you to make changes with confidence.https://twitter.com/fchollet/status/1273713171111440385?s=19 …
The curse of the platform developer.
its a bug that keras is complicit in, which is just as bad
Hey, that's just Keras' word against mine, man
Someone should write an AI tool that anticipates all possible programs it might be used in
I wonder what Turning’s Halting Problem proof in 1936 might say about this 
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
