So no one is going to talk about how the Model is a mathematical model which follows Bayes Theorem in it's core. It updates it's priors based on new evidence presented every day.
The whole point of the Model is to detect things which are uncertain by nature. Being wrong is not bad, it's good TBH.
Did some Program Manager needed a promotion at Google? Looks like it.
I personally dislike such changes, which no one asks for.
Either people are just pushing their BS through Google higher ranks or they have no clue how their users actually feel and use their core product.
The amount of wastage I see in online store returns is mind boggling.
I recently ordered something from a manufacturer on Amazon. After couple of days, they dropped price on product by $20. So I called up Amazon for price adjustment. I was politely asked to return it to manufacturer and order a new one.
Seriously, Amazon cannot work with manufacturers to just refund price difference instead of returning the product and ordering it again. It is wasteful at so many levels.
There should be integration tests along with some property based tests and fuzzy tests. Usually catches a lot of things.Invest in monitoring and alerts too.
TDD is like relying on debugger to solve your problem. Is debugger a good tool? yes,it is a great tool. But using it as an excuse to avoid understanding what happens under the hood is plain wrong.
The problem lies in industry where software engineering is not given any value but whoteboarding and solving puzzles is.
Software engineering is a craft honed over years of making mistakes and learning from them. You want code asap, kick experience engineers get codemonkeys in and get a MVP.
Quality is not clever algorithm, but clear conscise logic. Code should follow the logic, not the other way around.
Smart local students go to in state public schools to avoid crippling debt.