# Problem Solving Technique – Divide & Conquer

do u often find that when you try to SOLVE PROBLEMS in your life, be it at WORK, at HOME, at SCHOOL, or at PLAY . . do you often find yourself STUCK and OUT OF IDEAS, Not knowing what further step you should take to tackle the problem ???

Well . . ONE of the most powerful approaches you can take is to DIVIDE and CONQUER the problem. Decompose the PROBLEM down to its individual constituent parts (in simpler English, divide the problem into its SMALLEST BASIC parts) . . after that, you should then examine each of these smallest-basic parts individually and try to determine WHICH ONE is faulty or which one looks ABNORMAL, DAMAGED or somewhat IRREGULAR

i have discovered however that this is NOT ALWAYS an elegant approach, when you DIVIDE something (a problem), you often end up looking TOO DEEP and FOCUSING on the SPECIFIC fine-grain details once you are examining the individual basic (decomposed) parts of the problem. this leads to a syndrome that i call “the Box-mentality syndrome”. it is a serious mental syndrome that has kept people STUCK FOR DAYS and MONTHS in the end trying to overcome COMPLEXITIES in certain types of ADVANCED problems, therefore this technique of Divide of Conquer can lead to troubles when applied on problems that are weird and Not clearly-structured or on problems that CANNOT be divided or broken down into their basic small parts

the other shortcoming of this technique is because some of you assholes when i tell you to decompose (break-apart) something . . OUT OF IMPATIENCE and FRUSTRATION, you assholes end up RUSHING to pull the thing apart, and due to your IMPATIENCE, many of you end up either breaking-the-thing badly or you forget to WRITE DOWN or MARK where the various pieces originally CAME FROM, so you are NOT ABLE to put the BLOODY THING BACK TOGETHER to return it back to its ORIGINAL form once you’re finished solving the underlying problem ! you mess it up so much when you try to REASSEMBLE it . . that it ends up NOT properly packed back to its original look, the result of this is that some part of it is either skewed or unbalanced and after a while it FALLS APART dramatically leaving you with a bigger disaster !

if you assholes could learn to FIRST OBSERVE and then carefully MARK or LABEL or NUMBER every piece so that you KNOW WHERE you pulled it from and how it was ORIGINALLY positioned **before** you DISASSEMBLE the whole composite, you would be in a better position when you later REBUILD and REPACK the ENTIRE COMPOSITE back to its original form. you would repack it with 100% CONFIDENCE because with MARKINGS and NUMBERING . . NOT ONLY will you know and remember WHICH PART was the FIRST/LAST ONE you REMOVED (Numbering!!) . . . you would also know with absolute confidence WHERE THAT PART WAS ORIGINALLY located/positioned BEFORE YOU REMOVED IT. Even small things such as SCREWS when you disassemble your FLAT SCREEN PLASMA TV . . if u learn to NUMBER THEM and LABEL them  **BEFORE YOU REMOVE THEM**, you can use the divide and conquer strategy to TAKE the WHOLE TV apart, take a look inside it, replace that blown/burnt fuse, and then PUT the TV BACK TOGETHER with 100% confidence that it is BACK in its original packed form, and even if some of the screws LOOK identical, you would be able to put EACH INDIVIDUAL SCREW back into the EXACT place from which you PULLED it out EARLIER !! that’s it for today . . . tomorrow i will share with you my OTHER problem-solving technique that does NOT involve the use of the DIVIDE and CONQUER method. this other technique of mine is a KILLER TECHNIQUE based on a method that is **OUT OF THIS WORLD** and that is only ever discovered and applied by a FEW people who know what it REALLY means to think OUTSIDE THE BOX

# Problem Solving Technique 2 – Advanced

yesterday i shared and explained in detailed one of my favourite and effective problem solving technique, called the Divide and Conquer strategy. i also highlighted the serious shortfall that this technique suffers

as opposed to the DIVIDE and CONQUER method that i shared yesterday, today’s problem resolution technique involves the use of a novel approach that i discovered over my years and years of suffering as i tried to deal with COMPLEX problems that are Not clearly-structured and that cannot be easily decomposed (broken down) into their basic individual parts

some problems are so COMPLEX and so iLLusive that you can try to divide the problem down to its basic simple parts and you would STILL NOT be able to solve it. in this case, i usually teach my mentees to tackle the problem by examining and questioning its CATEGORY.  examine and question THE CATEGORY in which the PROBLEM falls ! inn what CATEGORY of PROBLEMS does this problem belong ?? the trouble for most people is that they are viewing or conceiving the problem in CATEGORY that is TOO SPECIFIC !!!!

sometimes you are looking at a problem from a perspective that is TOO NARROW or TOO SPECIFIC !! you have zoomed in TOO DEEP and you’ve gone TOO SPECIFIC deep inside the problem as you try to find its root cause, and due to your DEEP ZOOMING or your tendency to be TOO SPECIFIC when you examine the problem, you have now inadvertently LOCKED YOURSELF inside the [proverbial] box !!! this is a BIG problem and a serious MENTAL BLOCK for most people because once you are looking TOO CLOSE and you have gone TOO DEEP and TOO SPECIFIC in your examination of the problem, it becomes literally IMPOSSIBLE for you to look for a SOLUTION **OUTSIDE** that DEEP and SPECIFIC perspective you are in !

you must STEP OUT OF THE BOX and try to look for the solution OUTSIDE of the BOX. but what do i mean when i say you must STEP OUT of the BOX ???? many people NEVER REALLY explain this concept of the “BOX-mentality syndrome” . . they just mention it casually in passing or proverbially as a cheap regurgitated motivation-line, as a result, it often remains POORLY UNDERSTOOD ! TODAY i will explain the “BOX-mentality syndrome” to you FROM MY PERSONAL APPLICATION of it

when i say you must JUMP OUT OF THE BOX, what i mean is that instead of working with the problem or treating it as a problem that exists inside its  **SPECIFIC**  CATEGORY, you must now TREAT the problem as a problem that exists in an OUTER or MORE GENERAL CATEGORY to which it applies. LOL . . i know some of you people now got TOTALLY-LOST by that preceding statement 🙂 🙂 what i mean in Layman’s terms is that for example, if you have problem such as the Diabetes disease and you’ve been looking for a solution to cure it, you will often dive  **TOO DEEP**  into the analysis of what causes diabetes and what its symptoms are. once you’ve learned about these SPECIFIC CAUSES of it, you then ACCIDENTALLY LOCK YOURSELF inside these SPECIFIC DETAILS ! you lock yourself SO DEEP INSIDE your analysis of specific that you eventually remain PARALYZED and PERPLEXED by the SHEER AMOUNT of DETAILS that you are going through, and this only serves to LOCK YOU INSIDE THE BOX. becuz you’re now STUCK INSIDE THE BOX, it NEVER occurs to you that you should take these SPECIFIC DETAILS that you know about the causes and symptoms of diabetes and rather than examining them at their MOST SPECIFIC LEVEL, you should try to REVERSE SLOWLY and STEP BACKWARDS . . . . . look at the OUTER or GENERAL CATEGORY into which these specific problems BELONG !!!!! when you now look at these PROBLEMS as PROBLEMS of a MORE GENERAL NATURE, and you treat them at the OUTER LEVEL or GENERAL CATEGORY into which they belong . . . it is THEN that you are SUDDENLY able to UNLOCK DOZENS of OTHER POSSIBILITIES to overcome the diabetes problem 🙂 🙂 🙂 when you NO LONGER try to solve the problem as a purely Diabetes-specific problem, but you look at Diabetes as a diseases that falls within a BROADER category of OTHER RELATED diseases, you will often find that when you apply solutions that are meant for the GENERAL OUTER category or solutions that are known for the BROADER category of OTHER diabetes-RELATED diseases, THESE BROADER SOLUTIONS are the GOLDEN KEY that finally OPENS UP HIDDEN POSSIBILITIES FOR YOU that reveal how you can easily tackle and SOLVE the bloody problem 🙂 🙂

it is AMAZING when you discover things that have always been there UNDER YOUR NOSE but because you were looking TOO DEEP at the specifics of the problem, you NEVER noticed these BROADER SOLUTIONS that surround you and you WONT believe it when you later also realize that you NEVER conceived the problem as a MORE GENERAL PROBLEM due to you tendency to overly-focus on its DEEP & DETAILED SPECIFICS 🙁  🙁  !!! . . therefore you could NEVER UNCOVER these seemingly-iLLusive solutions that sit around u cause you were just TOO DEEP and too SPECIFIC in your conception of the problem !

in closing, a testimonial might serve to illustrate my point : i have seen German car mechanics with 30 years of engineering experience recommending that i replace an alternator in my car at a cost of R8500 when the problem in my car was in fact an issue involving a R250 roller-pulley !! but because these arrogantly-experienced engineers could NEVER BE TOLD anything about CARS, they would simply listen to the noise in the engine and from a distance . . they would conceive and diagnose the problem at its MOST-SPECIFIC LEVEL, they would say the noise is an ALTERNATOR NOISE becuz an alternator makes the EXACT SAME noise as a roller-pulley when it is faulty . . but these highly-experienced engineers would be TOTALLY WRONG in their diagnosis . . becuz sometimes it is just a roller-pulley that is faulty (making the exact same alternator-like-noise) and this INCORRECT DIAGNOSIS they give . . results in an EXTREMELY WASTEFUL expenditure of the customer’s cash !! needless to say, AFTER spending the R8500 on a brand new alternator, the car  CONTINUED to have the EXACT SAME PROBLEM, leaving the problem UNSOLVED and the noise in the engine continued EXACTLY as before ! another engineer 5 months later replaced the roller-pulley for R250 and SUDDENLY the noise disappeared completely . . the PROBLEM GOT SOLVED at a measly cost of R250 ! i’ve got DOZENS of OTHER personal real-life testimonials !

# Clean Up

When you prepare an automated process, such as a computer program or a machine that you invented yourself, always remember that once it starts to perform its automated operations, it will probably repeat/loop a certain part of its operation over and over. If the repeated part is something that adds-up or accumulates as time goes on, then you need to ensure that the machine/program is able to detect when it is full and therefore it must be able to clean-up after itself, so that it can continue working over a long period of time. If the machine or program CANNOT clean-up, then you might really hit a problem when something fills up inside it and causes the machine/program to hang ; to be UNstable or even to mess itself up. NB: Look for all areas in the machine/program that do some kind of Adding-up or Accumulation or Looping/Repeating/Repetitive operations that have a potential to Leave things behind lying around. Ensure that those areas will actually throw away or delete the things that are No Longer Needed as the machine/program continues to do its work in a cyclic pattern.

# Computer programming, development, coding

Computer programming, development, coding programs, designing code

Resilient to failure, run everything in TEST MODE (always suspect failure!). What if the user was to open a particular dialog box/window, only to leave the window temporarily and go in the background to DELETE a folder or something that will impact the current STATE of the program ??????
Be persistent over power failures
Be able to RESUME after power failure (save state constantly!)
Be able to resume after program crash (can happen anytime!)
Auto Save, save the current state as regularly as possible (all the time)
Allow user to resume where he left off when filling a form (consider connection failures/temporary disconnections while user is busy!!)
Avoid annoying stubborn repetitive pop ups, watch out for loops !! Avoid indefinite loops !!! Set a reasonable max LIMIT for each loop !
Most loops have too much of a chance to run indefinitely because they are initially evaluated on a lazy assumption that the repetition should NOT have or does NOT need a maximum limit.
One popup initially or first 3-5 times is OK
After that.. user must be able to disable popup or popup MUST STOP itself (auto-ignore)
Program must keep going forward, must Never wait endlessly on any dialog
a multi-threaded design is much better than a single thread by far, although it carries the disadvantage of complexity and hard-to-diagnose bugs. Because of this complexity, it can sometimes be a very BAD idea ! The program can hang or appear to be running while it is in fact stuck/hanging in the background in a zombie state !
Scheduling ability is very powerful, users should NOT be forced to always run something by clicking on it or by sitting there physically in order to trigger the job/process/application interactively.
You should highly consider a structural / hierarchical arrangement (folders, parent folder, child, child of child/etc). If possible, allow the folders in the hierarchy to be searchable themselves! This is very very useful and powerful. Often search features are restricted to Contents only and consideration is NEVER given to the metadata or Containers ! This is a serious weakness on the part of designers!!
Allow to Copy/Paste the folders/items/child from ONE group into another, or a drag-n-drop AT FOLDER LEVEL!
Clone and Adapt – Allow the possibility to clone a successful case (record) and resubmit it or reuse it but with slightly modified details. This is yet another EXTREMELY POWERFUL feature that many designers carelessly ignore. If people can clone, touch-up and resubmit any record or data, can you imagine the MULTIFOLD increase it will have on SPEED and PRODUCTIVITY , not to mention the substantial improvement in user-convenience as the users will save HUGE amounts of time from useless repetitive typing and repetitive clicking of something that differs by only a small fraction from the PREVIOUS one that has just been successfully completed !
Templating – ability to take a successful/baseline case and make a template out of it. A very innovative feature that is based on the Clone & Adapt concept above.
The testing should ideally be done by users who will give the application non-sensical input
The principle of proximity states that humans perceive a
relationship between objects that are closer together. Use this
principle by grouping functions together. This will make it easier
to learn and understand your application
Try to show the CURRENT status/state of key indicators, for example, show as much as possible whether something is ON or OFF, and whether certain features are enabled or disabled, status is up or down/etc. Don’t make the user have to close and reopen something in order to tell whether the change he effected on it was DONE/Accepted/Activated successfully or Not !
use hierarchy/tree if possible in order to arrange a complex set of related items/things
The visibility principle states that visual cues should be
present to assist users in understanding the status of the
application
if you have a hierarchy, make the tree itself to also be searchable, NOT just its contents!!!
The principle of visual feedback states that an application
should respond to the user by signifying that an input has been
received. Applications should also indicate to the user when they
are processing a request

Progressive Disclosure
Progressive disclosure is a great way to help users understand
what features are available to them within your application. By simply
hiding options that are not possible, you can reduce users’ cognitive
progressive disclosure principle is a rather easy thing to employ and is
especially useful in more complex applications with feature-laden

Consistency
The principle of consistency may seem obvious, but I’ve seen it
overlooked by many developers. This principle maintains that users learn
and understand applications more easily when they are consistent with
what they already know. I’ve seen developers introduce new methods for

Affordance and Constraints
Many objects, such as tools and household appliances, are designed
to afford us their proper use and constrain us from using them
improperly. These are the principles of affordance and constraints. An
example of this is the three-pronged electrical plug and outlet. These
objects are designed to not only complement each other, but also work
one way. It’s virtually impossible to plug in a three-pronged electrical
plug, shown in Figure 7-8, the wrong
way. With its flat prongs and round post, the plug makes it immediately
clear to people how to use it. And if it’s not clear, it prevents them
from plugging it in wrong and hurting themselves! At the hospital we have a saying: “Make it easy to do the
right thing and difficult to the wrong
thing.”

Confirmation
One way to prevent users from doing the wrong thing is by asking
for confirmation. The confirmation principle states that an application
should prevent undesired actions by requesting verification, as
demonstrated in Figure 7-9 with a confirmation dialog box
Hick’s Law is a prescriptive model that’s used to determine
the time it takes to select an item based on the number of items
available to choose from. The more items you include in a menu,
the longer the response time is for the user
Fitt’s LawFitt’s Law can help you determine the size of target elements,
distance a user’s pointing device must travel. This prescriptive model
is expressed in movement time, or MT, and proves that the farther the
user must travel between two elements, the less precise the user will be
reaching the target. If your intention is to have a user click on a
button, the size of that button will be dictated by the distance between
the button and the user’s cursor

# Inventions

If you are inventing a new product, always make sure that it behaves like a human being or at least it is aware of human behavior. This will expand the lifespan of the product and it will become very popular and likeable. For instance, the product must always ensure that it does NOT lockup or hang without saying anything to the user/customer. The product must NEVER assume that its surroundings are PERFECT. It must always use them in test mode, it must always test first and if the thing to be used fails the test, the product must report to its user that the environment is failing a **certain** test, then the user can take a decision or appropriate action to correct and assist :))

Have you ever tried to learn something that’s made up of many components, such as electronics, processes, project management or another discipline? I know it, believe me, it’s terrible sometimes!! The problem normally comes because “you” can’t put it all together. Sometimes the book is arranged in a way that is very confusing and you just can’t get to see how it all fits together, because the author started with something that should come right at the end of the book ! You see, you’ve got to be able to live with it, unfortunately it’s like that. The best way to deal with component based learning is to try and find out what is the BASIC thing that is at the center of the whole story. You must find out what is the PRIMARY thing or MAIN thing that is being talked about. Once you know it, you can then try to see how the other “smaller” things help to make the primary thing work. Normally, you’ll find that there is only ONE main thing about the whole idea, and then there are many small components that work together with the main thing in order to complete the idea. You must try to avoid concentrating too much on the smaller things alone, because many times you’ll find that they Don’t work well on their own. They only work well when you attach them to the basic/main thing. That’s the way you must play this game, believe me, it works!

But I need to make one small clarification regarding this technique. Some things Don’t need to be combined with others in order for them to work. Sometimes you’ll come across something that works perfectly on its own but then when you combine it with others, it fails or it does Not work so well ! So you need to be very careful about this technique, sometimes it can be troublesome if you try to apply Old Knowledge onto new things ! So how do you solve this issue? . . . . Well, I think you have to ask yourself whether this thing can work perfectly without being connected or combined with anything else. If it can, then it’s best to carefully Note down that “this thing can work perfectly on its own” and keep this note in the back of your mind. If it CANNOT, then obviously it means that you MUST combine it or connect it with something else in order to make it work. Sometimes you could even find out later that even if something works perfectly on its own, it might also still work perfectly when it’s combined with other things 🙂

If you are trying to learn something and it gets too difficult somewhere along the way, then you must start USING YOUR OWN MIND to break it apart. You must try to break it apart in your own mind. In this manner you ask yourself why the person who wrote it is saying what he wrote, or why he is putting the story in the manner that he is. At first it will be HARD to conceive it in your mind, but sooner or later as you keep flipping it in your mind you will slowly start to see how the writer of the book was thinking when he/she was trying to explain his/her story to you in writing (in the book). You will also get to see just how much sense it makes in real life. The writer can’t sit and write a long story about something that has No purpose or No reason ! There can only be something that you’re carelessly missing in his story or he is just talking in a way that you are Not familiar with. Just stop for a while and start thinking deeply about what he is trying to say to you in each paragraph that he has written. Sooner or later you will quickly start to figure out what’s actually happening. Some things are harder to explain on a paper (in writing) than when you actually see them. Some things are much easier when you actually think about them than when you listen to someone trying to explain them to you in a book or on paper.

# Use a Framework, Template and Abstraction

You have to be able to work with something that was NOT originally made by you. You have to be able to build on top of something that is NOT your original idea. You must be able to take something that’s a basic idea and transform it into something much bigger or much smarter. Even if you Don’t understand how that thing works inside itself, you should try to find a way to still use it in your own ideas as long as you have been told what its purpose is. Once you’ve learned what its purpose is and you understand its purpose, it should be clear to you whether you’re gonna need that thing at some point in your own ideas in the future or Not.

So, you want to learn how websites work ? Or do you perhaps want to learn

How To Make A WebSite , or
How To Create A WebSite , or
How To Make Your Own WebSite

if you’ve been asking yourself any of these questions above, then you have come to the right place to learn all this stuff

people have been begging me to put back the web tutorials that I used to have at my old website since I decided to close down that website. After a lot of resistance, i finally decided to put back these tutorials here online on this website for the benefit of those who were following this stuff.

You may CLICK HERE TO BEGIN my tutorials on how to make your own website. Among other topics, my tutorials will teach you :

01 – About Website Web Server Web Hosting Webpage Etc
02 – About Registering A Domain Domain Names And Dns Servers
03 – About Email Server Email Hosting Emailbox Etc
04a – How To Connect Your Outlook To Your New Mailbox – For Windows Users
04b – How To Connect Your Outlook To Your New Mailbox – For Apple Users
05a – How To Use Gmail To Send And Recv Emails Over Your New Mailbox
05b – How To Use Hotmail Or Live To Send And Recv Emails Over Your New Mailbox
05c – How To Use Yahoo To Send And Recv Emails Over Your New Mailbox
06 – My WordPress Blogging Basic Quick Reference Guide
07 – The Web Mastering Process   From A To Z

# Limitations when you Innovate

when u innovate, DONT start by thinking of current limitations or current negative barriers of the existing underlying environment … think as if it can be done with currently available (Limited as it is) resources or technology. think as if it could be done on top of the currently limited underlying environment/platform

short and sweet – that’s ALL im gonna say in this article !