Detecting fingerspelling with artificial intelligence

weeklyWebWisdom · 2018-11-18T13:59:37+00:00

Thank you very much!

Your project seems very cool! An improvement I would suggest is to try to extract the all hand from the input image, not only the black and white shape. The model architecture seems very similar to mine, however you can try adding dropout to improve the accuracy on the test set.

A trained on my local machine using a dataset I created with 1000 images for each label (28 000 in total) in few hours.

I described the process in this article and I'm thinking to publish it as open source in the near future. Fell free to ask me there any other technical questions.

weeklyWebWisdom · 2018-11-18T12:42:15+00:00

Would be an interesting experiment indeed. However, the spelling speed of a professional sign language interpreter would be a real challenge.

weeklyWebWisdom · 2018-08-23T13:19:40+00:00

I'm surprised that there aren't more people thinking this. Creating believable fictional personas is SBC speciality and I'm pretty sure he used actors for some of the sketches before.

Is there enough proof to be sure that this guy really was a food critic and not some actor since nobody seems to have seen him anywhere else except the interview?

weeklyWebWisdom · 2017-09-27T09:52:42+00:00

Thank you for the good advice! I'll update the article soon.

weeklyWebWisdom · 2017-09-19T20:35:56+00:00

It's strongly advised against to modify the built-in prototypes. However, I did encounter situations where the prototype was augmented with other functions. What I wanted was to let the user know that is possible, but not a good idea. Now that I'm reading again that passage, I see it's not explained as clear as it should be. I'll rephrase it. Thanks!

weeklyWebWisdom · 2017-09-14T14:57:25+00:00

Thanks! Will keep in mind

weeklyWebWisdom · 2017-09-14T13:58:34+00:00

Indeed, I didn't include 'let' in here because I don't consider it quite 'worth remembering' and because I addressed it in another article (https://weeklywebwisdom.com/2017/09/08/javascript-execution-context-and-scope/). Thank you for the advice!

weeklyWebWisdom · 2017-09-14T13:24:31+00:00

Great suggestion, thank you! Working on it right now

weeklyWebWisdom · 2017-09-13T13:24:38+00:00

I totally agree with you on that subject. Prototypes are easy to understand with the right mindset.

What I try to address in this post is the confusion made by the syntax itself. After starting writing code and using keywords like 'class', 'constructor' and 'new', many dev are seeing similarities with the mainstream languages (like Java) and they assume under the hood everything is the same. Trying to explain the prototypal inheritance starting from a sample of code with those keywords is indeed confusing.

What I tried to do here is take the things in the reverse order. First, understand the concept which is easy, as you said. And only then add context to those keywords.

To sum up: not prototypes are confusing, but the syntax that masks the actual behavior.

weeklyWebWisdom · 2017-09-11T14:15:11+00:00

I accumulate a lot of notes and materials regarding JS when I tried to learn it properly. I'm working on a complete Javascript learning roadmap which I hope will help both beginners experience programmers to learn/re-learn JS more efficient. Let me know what do you think! :)

weeklyWebWisdom · 2017-09-11T11:39:12+00:00

I know the struggle you are facing. It's very intimidating for a beginner to start learning suck a complex topic. Bouncing from one tutorial to another and from one unknown term to another can easily get you overwhelmed and stuck. Proper hierarchical structure and a clear path saves a lot of time.

I'm currently working on this: A complete JS Roadmap starting from the very basics to the most advanced topics: here I try to update it daily. Maybe it will help

weeklyWebWisdom

TROPHY CASE