-
Notifications
You must be signed in to change notification settings - Fork 7
Prep: Engineering Topics
all1124 edited this page Sep 28, 2019
·
3 revisions
- Read the problem completely twice.
- Make sure you completely understand the problem
- Can you explain the problem to someone else?
- Solve the problem manually with 3 sets of sample data.
- When you are solving the problem manually, recognize what your brain is going to solve the problem
- Write out everything that is going on in your head
- Optimize the manual steps.
- Figure out if there is another way you can solve the problem easier, or if there are some steps you can cut our or simplify
- Write the manual steps as comments or pseudo-code.
- Capture all the steps we created and now either put them into our editor as comments or write them as pseudo-code that we can translate to real code
- Replace the comments or pseudo-code with real code.
- Take each comment and convert it into a real line of code.
- Optimize the real code.
- Take a look at your code and figure out if you can cut out a few lines or do something simpler.
- Make sure all your variables are named with meaningful names
- Understand
- Know what is being asked
- Write down the problem, make a diagram, tell someone about it
- Plan
- Plan your solution
- Give your brain time to analyze the problem and process the information
- Divide
- Break the problem up
- Solve each sub-problem one by one. Start with the simplest.
- Once you've solved every sub-problem, connect the dots
- Stuck?
- Debug: Go step by step through your solution trying to find where you went wrong.
- Reassess: Take a step back. Look at the problem from another perspective. Is there anything that can be abstracted to a more general approach?
- Research: Google. Find other people's solutions/approaches and learn from them.
- Practice
- SOLVE LOTS OF PROBLEMS
- A questioning process
- By repeating why five times, the nature of the problem as well as its solution becomes clear.
- The five whys are used for drilling down into a problem and the five hows are used to develop the details of a solution to a problem.
- When we want to push a team investigating a problem to delve into more details of the root causes, the five whys can be used with brainstorming or the cause-and-effect diagram.
- Draw a box at the top of a piece of flip chart paper and clearly write down the problem or solution to be explored.
- Below the statement box draw five lines in descending order.
- Ask the “Why” or “How” question five times and write the answers on the lines drawn from number one to five.
- It may take less or more than five times to reach the root cause or solution.
- Most people prize being busy
- But for most people, this “busyness” is nothing more than distraction and procrastination from what really matters. They just like feeling busy.
- Deep work means absolutely not tolerating distractions and producing monumental quality and quantity in a very short time.
- This is how you can complete far more with focused efforts than unfocused efforts with far more time.
- Every time you say yes to something, it means you’re saying “no” to a dozen other opportunities.
- The world’s most successful and extraordinary people say no to almost everything, but yes to a few things.
- Really successful people say no to most things, because most things won’t get them to where they truly want to be.
- Value your time at what it deserves to be
- You probably need to say “no” more.