Author Archives: ingvald

SMART goals reduce creativity and innovation

from lmsgoncalves.com/2013/01/14/defining-objectives-is-really-productive/

During my Christmas holidays I read a great book – “Drive”.
….
Part of the book talks about goal setting
….
How many of you heard that goals must be SMART? Do you actually think it is a good definition for goals? SMART stands for Specific, Measurable, Achievable, Realistic and Time-scaled.
….
According to the studies discussed in the “Drive”, goals tend to narrow our focus. This does not sound too bad, right?
….
in reality this is good only for activities that use the left part of the brain, i.e. for simple tasks that do not require creativity. But, as Daniel warns in his book, for complex and conceptual tasks giving a specific and measurable objective can blinker the wide-ranging thinking that is necessary to come up with an innovative solution.
….
Another problem with specific and measurable goals, in my opinion, is that reaching them becomes the only thing that matters.
….
On a larger scale, this may cause systematic problems for the organization
….
“Give a manager a target and he will do everything to achieve it. Even if he has to destroy the company in the process” by W. Edwards Deming

 

rushing without automated tests is a business mistake

excerpts from article by Joseph Puopolo, An impassioned plea to other Start-up founders to use automated tests.

Working on the business side of the shop, I have fought against automated tests for a while. That all changed recently
….

The conclusion I reached was that automated tests save developers time and let you deliver more. This was a painful admission, but a correct one.
….

I have been in multiple start-ups where automated tests didn’t exist, and let me just say the QA overhead was astronomical.
….

While it seems counter-intuitive, building tests saves you time in the long run. The knee jerk reaction is to spend your time building new features. I have had this reaction many times
….

One of the biggest time sinks in development is finding the problem. With proper tests in place you can isolate and figure out where the issue is.
….

With automated tests in place, it is easier for new developers coming into the system to understand code that they didn’t write.
….

automated tests save time and help you get to market faster. If your goal is to rush to MVP without putting in place a scalable infrastructure that allows you to grow your code base, you are not only making a technical mistake but a business mistake.