Too many chefs spoil the code.
What I learned from Steve Jobs
1. Experts are clueless.
2. Customers cannot tell you what they need.
3. Jump to the next curve.
4. The biggest challenges beget best work.
5. Design counts.
6. Changing your mind is a sign of intelligence.
7. “Value” is different from “price.”
8. A players hire A+
Steve Jobs talks about managing
The management of a company that makes furniture, doing well, took it into their heads to expand their line into pianos. Why not make pianos? They bought a Steinway piano, took it apart, made or bought parts, and put a piano together exactly like the Steinway, only to discover that they could only get
The interface inheritance enforce you to implement a method with a given signature, but it doesn't enforce you how to implement it or to use some default
I am rephrasing an old political proverb, but it's true. If a manager ask you to release four days earlier, after he has promised you to postpone the release date with a week probably the chaos is so big in teams with this kind of managers that you can't expect any quality from the
The real reflection of intelligence is to create order in the chaos despite of catastrophic
This week I have been explaining about cohesion using materials from Prag Pub Magazine and realized something ultra very simple. The definition of cohesion is proximity should follow dependency which make me see that cohesion(proximity) is function of dependency. So cohesion = f(dependency) and if we want to follow Single Responsibility Principle you can
If you only learn the minimum amount necessary to get over the next hurdle,
you'll fall behind.