If iam correct it is in this on wwdc[0] that one of the Swift engineers talks about how they implemented the Strings API for Swift and how it works under the hood. It is fun and interesting to watch. It starts around the 28 minute mark.
I read programming books just like normal books, and take time to examine the example code. I am currently reading a book about Swift design patterns. I dont try to learn how to implement it but instead on how to use a certain design pattern what it does etc. By the time I need it I look it up and implement it for my problem.
Is it possible to combine this with snips.ai? So you have voice control on the device it self or run snips on another device and let it send commands to the home assistant device?
You can flash our operating system Hass.io[1] to a Raspberry Pi, install an MQTT broker and Snips via the Hass.io UI, connect a microphone and speaker to the Pi, upload your Snips assistant and you should be good to go. See the instructions [2]
Not only easy in Javascript, it is easy in any language that has easy serliazation to JSON. I always use it for my own
hobby projects because I dont have that much SQL knowledge. Which makes Nosql easy choice for me, just serialize your object into json and push it to your DB.
Pushing a serialized object into a distributed hash definitely solves some problems.
And you have finite time, so if the choice is between that solution that you can do now and searching for another solution that may or may not be better, it's often reasonable to go with the known solution. In economics, this is known as "rational ignorance."
The value proposition of learning will change, though. You will find it's worth it, especially if you move beyond hobby projects and have to deal with any kind of business logic, to spend some time learning how databases work, and maybe even the math behind them, the relational model.
There are a lot of mediocre or awful references out there. If you need a good text on the subject, I recommend CJ Date's "Introduction to Database Systems." Note, though, I said good, not easy.
You might be "choosing" not to bother understanding the alternatives, but you're not making a choice between the alternatives because you don't know what they are.
I guess since you posted a comment twice. Not that familiair with HN unspoken rules. But I guess HN just like other forums don't appreciate double posts
That is a way of looking at it. Another perspective is that any attempt to deify a real human being is bound to be nonsensical, and we should always be wary of the complex human nature behind a carefully constructed "public figure".
At least hopefully nobody will somehow look at this as an excuse for their own racist agenda (i.e. look, such a greatly respected person has also been so racist, why can't I?). The simplistic attempt to instill one-dimensional interpretations of personalities in the public consciousness has to stop, and hopefully both the educational institutions and the media can always remind people of the complexities of every individual. Though this seems to be a tall order at least for now.
At least hopefully nobody will somehow look at this as an excuse for their own racist agenda (i.e. look, such a greatly respected person has also been so racist, why can't I?)
Lets hope it, although I am afraid, there will be persons who use it as an excuse or even some sort of scientific evidence or proof. I.e: "See even one of the smartest person walked on this earth finds Chinese gross this must proof something about the Chinese right?!"
Take a look at the youtube channel 2minutepapers [0], it covers various ML/DL papers and their results. The person creating the videos has a background in writing rendering software. He has various videos covering papers that use ML to improve rendering and graphics. Not long ago he created a own paper about teaching an AI the concept of metallic, translucent materials and more [1].
I really recommend checking his channel, videos are short and fun and easy to understand even without ML background. You can really sense his passion and excitement for this topic.
You are not alone, but I personally think (and I think many others) that AI will come to the point that you dont really need to understand how the math behind it works but only how it works. So for example you only need to know how back propagation works and what it does, but not the exact math formula for it. I think you can see it already happening with Keras. You would need to know the math and the nitty gritty if you want to build or research state of the art ML/DL
Well it is not intergrated in the language like i.e Java or C#. But Python does have the naming convention to mark vars that should not be touched with __ [0]
You and the article author both didn't seem to read that link.
A single leading underscore is a convention to mark a variable as private.
A double leading underscore "name mangles" the variable (adds the class to the name of the variable) and has a specific use case for inheritance. They're class level private, which is probably not what you want.
class Number:
def __init__(self, n):
self._number = n
self.__number = n
class NumberChild(Number):
def one_higher(self):
return self._number + 1
def two_higher(self):
return self.__number + 2
number_child = NumberChild(10)
number_child.one_higher() # This works
number_child.two_higher() # This raises an Attribute Error
That's just a single underscore for the convention. Double underscore actually mangles the attribute name (it prefixes it with the class name), so that's "really really don't touch this". It's hardly ever used though.
That's not. The use case for name mangling was "avoid the risk of conflict when designing classes for inheritance": if you're building classes for inheritance, subclasses using the same name for an internal/private attribute are not going to unwittingly collide with the base classe's.
Sure that was the idea, but I don't think I have ever seen any code use it like this.
A single underscore is something that's not part of the classes public API, any child classes may need to change attributes, and by using a double underscore you are saying "I know better than you, you won't ever need to change this", which is never true.
Python isn't like Java where you often have complex and often convoluted class heirachies, where truly private attributes might be more useful.
[0]https://developer.apple.com/videos/play/wwdc2017/402/