Simplified Thinking Like a Software Engineer part 1

  • automotive knowledge,
  • diagnosis,
  • replacement equipment,
  • and common shop tools.

Golden Rule 1, know if you have the talent of the general problem solver, and develop it

  • If you are a talented problem solver, it means that you have:
    1. the talent and the eye to detect the critical details of general life problems.
    2. You already were and still helping your family or friends with solving their problems.
    3. You are seeing the details that no one is looking for or no one notices it.
    Here if you already have it, you should know it’s your way is programming solve more and more, here know that you are the closest one to winning the problem-solving competitions, so give this path more time as much as you can and try to develop it.
  • If you think that you don’t have it, maybe you are right or you have the talent but you have never been tested, so I’d recommend you to have the mindset of the beginner scientist, this mindset means:
    1. Asking for more and more, the real problem solvers are looking for a lot of answers to a lot of questions
    2. Even if they don’t have the questions and they just have a word or keyword to look for, that would be good for them to search and deep dive into that topic and know things they have no idea about it.

Golden Rule 2, Hava a paper when you are thinking

Golden Rule 3, Abstract the problem

Rule 1, Understand the problem and its type

  1. the direct steps solution
    like solving The Fox, the Goose, and the Corn problem, it’s direct steps without any probability, here it’s easy to know what is the most effective solution.
  2. the probability steps solution
    like sliding puzzle, or chess movements that are large enough that it is difficult or impossible to plan out a complete solution algorithms that will be the most effective one with all situations

Rule 2, Know the types of the Data:

Rule 3, How much data that the algorithm (the solution) should deal with?

Rule 4, See the constraints:

Rule 5, Look for the most constrained part of the problem

Rule 6, Always Have a Plan

Rule 7, Divide the Problem

Rule 8, Start with What You Know

Rule 9, Reduce the scope of the problem

Rule 10, Look for Similarity

Rule 11, Sometimes it’s better to do some experiments

Rule 12, Finally, push your code to GitHub

--

--

--

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

Nazar Recognized as Advanced Technology Partner by Amazon Web Services

Hi, My name is Alex Oyebamiji an intern at the ongoing HNG program https://zuri.team,

Building NVIDIA Triton Inference Server from Scratch for TensorFlow Backend

Terraform Azure DevOps Build and Release pipelines

Refactoring MGPUSim Work-Group Dispatching Mechanism

GCP’s Standard Tier networking performance

The concepts of Kubernetes and creating a GKE cluster on Google Cloud Platform (GCP)

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
AndReda Mind

AndReda Mind

More from Medium

Stack: Data Structure

Working with Programmers

How To Effectively Use LeetCode

Software Development Vs Software Engineering: Understanding The Key Differences