Skip to main content

When we don't see the sun, we see other stars


What are your motivations for creativity?

- I want to make a change.
- It makes me happy! It is a need of my mind.

How to be creative for a thing?

There are two steps:
- See the thing as every people see it
- Think about a new different thing from it

How to think about a new different thing?

There are two ways:
- Forget all things you have already known.
- A whack on the side of your head. ;)

This was what I have learned from the following great book:

source: Amazon.com
Well! A physical whack on the side of your head is needed sometimes but the meaning behind is that you need to break these 9 following locks on your mind. Remove them!

The lock #1: "The correct answer"

We all learn from schools that there is only one correct answer to a question. For example, a proposition is only true or false in Algebra. In reality, there are always some answers to a question basing on a point of view. For example, number 6 becomes number 9 if you look it in the opposite.

The lock #2: "That is not logic"

There are two kinds of thoughts: soft thinking and hard thinking. Soft thinking focuses on finding a relationship among things. On the other hand, hard thinking focuses on the differences between things. The metaphor is a technique of soft thinking which needed for creativity.

The lock #3: "Follow the rules"

Sometimes, creativity is not always a contribution but a damage. However, in order to create a new model, we need to break an old model. Break the rules!

The lock #4: "Be realistic"

Answering the question "if...then what happens?" is useful somehow. For example:

- Imagine if what other people (your inspirational ones) will do in your situation. E.g: I sometimes say to myself when I face an issue: "What will Mr. A do in this situation?"

- Imagine if you are what you think. E.g: Imagine you are a paper; what are your characteristics to make you more convenient for users?

- Imagine an idea which is obviously not realistic. According to this idea, you can come up with a better realistic one. E.g: original idea: the Government will give money for whom put trash into trash bins. Improved idea: every time people put trash into trash bins, they will receive a random fun from the trash bins.

The lock #5: "Play is frivolous"

"If necessity is the mother of invention, then play is its father". There is no doubt about it!

The lock #6: "That is not in my field"

Specialization is necessary in most of the cases; however, bringing a knowledge from a field to another field is really useful as well.

The lock #7: "Don't be silly"

Actually, a comedian is smart. He/she always thinks in different ways. It is like a movement of a car, sometimes it needs to go back in order to go straight.

The lock #8: "Avoid ambiguity"

People avoid ambiguity because it results in the misunderstanding in communication. However, just keep listening to your dreams and playing with it.

The lock #9: "Mistakes are wrong"

In most of the case, a mistake can result in a very bad situation. However, a mistake sometimes helps you come up with some new approaches.

Reference:
[1]. Roger von Oech, A Whack On the Side of the Head

Comments

Popular posts from this blog

Resolution for 2016

HCM full stack developer Meetup This is the topic of HMC full stack developers' meetup this time. We have shared our ideas and discussed about them. Most of discussions is focused on career path for developers in Vietnam and what next we will do in 2016. I have a problem with my career path in Vietnam. I seem to get lost my motivation because I don't like to become either a manager or a TA (such as Technical Assistant, Technical Analysis, Technical Architect). But, why only are there either manager or TA in Vietnam? How about a 60-years experiences developer? Salary is actually an issue. I admire several great developers in the world such as Jeff Atwood ( stackoverflow.com founder), John Sonmez ( simpleprogrammer.com fouder). They created very great and valuable stuffs for the community and they are free of finance - of course, I think. Why can't I follow that way? I would like to not only create cool stuffs but also get high salary. I love to becom...

JSF, Primefaces - Invoking Application Code Even When Validation Failed

A use case I have a form which has requirements as follow: - There are some mandatory fields. - Validation is triggered when changing value on each field. - A button "Next" is enable only when all fields are entered. It turns to disabled if any field is empty. My first approach I defined a variable "isDisableNext" at a backend bean "Controller" for dynamically disabling/enabling the "Next" button by performing event "onValueChange", but, it had a problem: <h:form id="personForm"> <p:outputLabel value="First Name" for="firstName"/> <p:inputText id="firstName" value="#{person.firstName}" required="true"> <p:ajax event="change" listener="#{controller.onValueChange}" update="nextButton"/> </p:inputText> <p:outputLabel value="Last Name" for="lastName"/> <p:i...

BarcampSaigon 2015

Barcamp Saigon is one of my most expected events of the year. This year, it took place at RMIT university. As usual, it brought many useful topics to the community. Here is all topics that I have attended. Scale it! - Lars Jankowfsky Lars is founder of 8bitrockr.com How do we make a decision correctly? It is hard to know that until we try and measure it. He gave an example about how good an app was. And, most of people thought that the app with nice user interfaces is good at the first look. But it is not correct because it is only true until we try to use it, even the nice GUI app sometime is not good at UX, functionalities, etc. The key of success for working in team is collaboration. We can not only base on the experience of members likes: "In my opinions| As I know.... this is the best way..bla..bla.." but we should test it. Therefore, manually testing as well as automation testing is more and more necessary nowadays. "Don't think, just try...

My 2017 Review

Passion for System Design After finishing a one year project, my longest stable team (lasted for 3 years) was separated into two smaller teams. Sadly, but that was a good chance for me to become a key member in my new team. My preferred skills were about system architectures; therefore most of the tasks of building the application structures were handled by me. In order to enhance my design system skills, I have spent much my time for reading books closely after work. These following books help me a lot. - Object-Oriented Thought Process | Matt Weisfeld - Head First Design Pattern  | Elisabeth Freeman and Kathy Sierra - Java 8 in Action: Lambdas, Streams, and Functional-style Programming | Alan Mycroft and Mario Fusco Junior Technical Architect I was requested to join a technical architect team (aka Team. Alpha) where I actually had gained experiences almost on interviewing candidates for my company (lol). Besides, I noticed myself must improve the skills of convinci...

A User Guide To Working With Huong

  Introduction I write this user guide to help us (you and me) have a good collaboration at work. I hope you also share yours. How I view success We all feel passionate and happy at work. We all enjoy discussing transparently. We take it easy to give and receive feedback. After all, we together develop and bring valuable applications to users. How I communicate I mostly prefer a face-to-face conversation. Just leave me a message on Slack if you don't want to come to my desk. For a big topic which takes more than 30 minutes, we should have a meeting. Only send me emails only if stuff is very formal or out-of-office hours Things I do that may annoy you I do practice the Pomodoro technique so that sometimes you see me in the "do not disturb" mode. Often to make things clear, I am at ease talking   frankly   with you. What gains and loses my trust It is easy to gain my trust when you commit to what you say. You show your passion and endeavors to achieve that. It is easy to lo...