I am not a bookworm, no way! But I have interests in some subjects which led me to read some really really great books. So, I am starting a new series on the books that I have read and would like to recommend to my friends and colleagues. They cover different subjects such as Software engineering, Team management, Personal development, Psychology, Strategy and Management, autobiographies, etc.
There are some underlying theories behind software architecture and structure that every software engineer must know. On the face of it, a developer may not face a situation where this knowledge is applicable, but there are situations in development where one may have any idea where the problem exactly hides. If you really want to know why overdriving yourself and your team is not helping you to get things done and dusted, I recommend you to study some subjects.
I am borrowing an example from Tom Mitchell’s video lecture to share some ideas on how we can effectively and objectively use MAP. Here goes the equation for outcomes of coin flips where our coin may not be an ideal coin (that’s the only reason we are making an intelligent machine to find probabilistic outcomes):
θMAP = arg maxθ P(D|θ) P(θ) = (α1 + β1 – 1) / (α1 + β1 – 1) (α0 + β0 – 1)
How we choose β values from our previous knowledge of coin can have interesting facts.