A machine learning technique which boosts weak learners to strong ones by using gradient.
A simple explanation of the Hidden Markov Model
One of popular interview questions is: “please describe the four characteristics of object-oriented programming”. In my observation, not many candidates — even the senior ones — can explain well Abstraction, Encapsulation, Polymorphism, and Inheritance. Worse, little did they know the drawback of Inheritance.
Little did they know that the universe is four dimensional and even the orbit of planets is an illusion produced when straight motion in a four dimensional space is projected into three dimensions (or something).
immediately reminded me about projective geometry which is one of the most beautiful systems of mathematics.
So the universe is 4D? I don’t know. But if it was true then we could use the concepts of projective geometry to interpret something interesting.
Null is clearly evil. We as human tend to forget to check null, and boom … crash!!! Documentation may help, but again we still forget reading documents. Worse, not all documents are correct and up-to-date 100%. Even if we remember to do every null check, our code would be very messy.
So what is the solution?
Exceptions are a very common concept in most of languages nowadays. In this article we will discuss why exceptions are needed, checked vs unchecked exceptions, and why C# doesn’t have checked exceptions.
This article is about my personal explanation of the reputed design patterns: Model-View-Controller, Model-View-Presenter, and Model-View-ViewModel; followed by a judgement, and a discussion for the applying of those patterns to the Web.
Let’s start with Model.
Builder Pattern and Factory Pattern are pretty similar in a way: both of them encapsulate the details of object-creation processes. However, in cases there are many complicated processes to create various representations of objects, and those processes share a common trait, Builder Pattern is the better choice.
Object persistence — for example, saving/loading objects to/from a database — is easy, especially when using an ORM framework. It is easy because it breaks principles of OO design.
Have you ever hesitate between these two implementation of the Factory Pattern: