December 5th, 2014
Have you seen a great company started by ten founders which voted to decide what problems should their company solve?
Have you seen a great product where ten product managers voted on features to be implemented?
Have you seen a great design done by ten architects voting on how to build architecture?
December 5th, 2014
One of my common interview question is writing a function which takes a string like “2+2″ and returns an integer result.
I asked to do that for quite big set of rules initially (support several operators, multiple digit numbers etc.). However, it was overwhelming for candidates. As result I scaled it down to several simplistic cases.
I ask to write a method which can calculate “2+2″. And it takes them 30 seconds to do that. I ask them to change a solution to handle “2+2+2″. It takes them 3-4 minutes and next thing I ask to do “12+2+2″ (support of multiple digit numbers) or “2+2-2″ (support of operator minus). And boom… It takes them 30 minutes to do this.
The question is “Why?”
People are wired to always push forward. As result, they take their previous solution and try to hack it into a new one which will support this new requirement. As result, the solution become so messy and complicated by second or third time around that it’s impossible to update it.
However, all they need to do is to step back for one second and think about new problem and new solution (vs trying to hack the old solution).
November 21st, 2014
Disclaimer: I am not a financial advisor or an accountant. Please go ahead and use this graph as the only source of information If you really want to shoot yourself in the leg,
And here is the graph which has almost everything what you need to know about ISO’s to get rich and famous.Click on the graph to zoom.
I really appreciate Hans Reichenbach’s help proofreading the text on the graph.
November 2nd, 2014
Once upon a time, software engineers were a rare breed. There are dozen of millions of sw engineers now.
Once upon a time, you had to compete only with local software engineers. You are competing with people in Kuala Lumpur and Tunis now.
Once upon a time, you had to learn two programming language on one operation system and you was set for life. New languages, frameworks and tools pop up each year now.
Once upon a time, the information was a secret passed from masters to apprentices. A 12 year kid has access to the same info which has veteran engineer with 20 years of experience now.
You can be smart, but there will be millions smarter than you. You can be experienced, but there will be millions who are more experienced than you. You can work hard, but there will be millions who will worked harder than you.
So, what are you going to do?