A short review of a book by Nat Greene, describing 9 behaviors of great problem solvers.
Let's talk about a specific way that you can show a potential employer that you are a pretty good problem solver--and therefore you would be a good hire.
For everyone's benefit, there comes a time when we need to physically cut the cord.
If you want to be a Pretty Good Problem Solver, you need to avoid the trap of depending too much on your memory.
Technical folks are often driven by a strong desire to show-off their unique skills.
My wife and I took a trip-of-a-lifetime. One day I received a text message saying, "Call me when you get this." I had not seen the message for 8 hours.
When searching for your next job, you should ignore the negatives of previous work and focus on the positive aspects of new opportunities.
Videos are increasingly used to explain, teach, and entertain. Do videos meet the requirement to Write Stuff Down as part of solving problems?
Engineers are often called upon to explain the technical details of a problem and the available options for solving that problem. You need to organize your presentation and express it appropriately.
First impressions of a design can be wrong as I found out when fixing the LED backlight of a low-cost television set.
A recent article sparked a lot of discussion about the virtues or evils of automating some of your work.
There is a lot of great information and entertainment available on the web. Unfortunately, far too much of it is wrong.
Other folks can duplicate or check your work when you document that effort by showing every step.
Sometimes slowing down can help speed up overall project success. A little patience will definitely improve your project and product quality.
Bob’s frustration with some so-called leaders boils over.
Can a slip of paper inside of a cookie truly predict your future?
Human nature makes it far too easy to get lost in the little tasks and forget a larger goal.
When you are setting Priorities, sometimes you ask yourself, "Who is the Most Important Person?"
Despite our best efforts, we sometimes make the same error more than once.
In human and technical systems, difficult problems often occur at the interfaces.