From 169431c7a5493d0104612d6f4e62b41c6bf03934 Mon Sep 17 00:00:00 2001 From: Ambg05 Date: Mon, 10 Oct 2016 13:11:08 +0100 Subject: [PATCH 1/2] Update and rename Creating A Problem To Find Good Solutions.md to Creating a problem to find good solutions.md --- .../Misc/Creating A Problem To Find Good Solutions.md | 11 ----------- .../Misc/Creating a problem to find good solutions.md | 11 +++++++++++ 2 files changed, 11 insertions(+), 11 deletions(-) delete mode 100644 content/21.From-Audio/to-fix-transcription/Misc/Creating A Problem To Find Good Solutions.md create mode 100644 content/21.From-Audio/to-fix-transcription/Misc/Creating a problem to find good solutions.md diff --git a/content/21.From-Audio/to-fix-transcription/Misc/Creating A Problem To Find Good Solutions.md b/content/21.From-Audio/to-fix-transcription/Misc/Creating A Problem To Find Good Solutions.md deleted file mode 100644 index 96effb4..0000000 --- a/content/21.From-Audio/to-fix-transcription/Misc/Creating A Problem To Find Good Solutions.md +++ /dev/null @@ -1,11 +0,0 @@ -**Creating A Problem To Find Good Solutions.** - -One of my favorite ways to solve a hard problem is to put myself, or my team in a situation where we have to solve a problem. And in a way those are good problems to have because they force you to solve good things, they force you to actually understand what is going on, they force you to really think about how to address it because you are not thinking theoretically about a particular issue or what will happen if this happens, what will happen if that happens. You actually have a real problem with real scenarios, real outcomes, real feedback that you are basically dealing with. - -So in a way the closer you can be with the problem that you are solving, the more you can experience, the more you can visualize it, then most likely the solution you are going to come up with is a much better solution. - -How many times you've heard of cases where a particular feature only was added when one of the key engineers or architect actually went on the road, met some customers and then they showed him some stuff and he says, "Ooh, that kind of sucks, I can do something better". - -In a way that is far too late, that is ridiculously late, you want those feedback loops much close to home because it basically means that you want people to be solving the right problems. - -And that is why feedback loops are so important because the faster the feedback loop you have, the easier it is to understand the implications of changes, the easier it is to find good solutions that are sometimes good enough for the problem that you are trying to solve. Which also prevents over engineering and over complexity. \ No newline at end of file diff --git a/content/21.From-Audio/to-fix-transcription/Misc/Creating a problem to find good solutions.md b/content/21.From-Audio/to-fix-transcription/Misc/Creating a problem to find good solutions.md new file mode 100644 index 0000000..3673e00 --- /dev/null +++ b/content/21.From-Audio/to-fix-transcription/Misc/Creating a problem to find good solutions.md @@ -0,0 +1,11 @@ +**Creating a Problem to Find Good Solutions.** + +One of my favourite ways to solve a difficult problem is to put myself, or my team, in a situation where we have to solve the problem. This approach forces you to understand what is going on, and it forces you to think how you will address the problem. By doing this we are not thinking theoretically about a particular issue. We are dealing with a real problem with real scenarios, real outcomes, and real feedback. + +The closer you can be with the problem you are solving, the more you can experience, the more you can visualize, and the better the solution you will devise. + +How many times have you heard of cases where a particular feature was no sooner added to an application than one of the key engineers went on the road, met some customers, and when they gave some feedback the engineer realised, "Ooh, that isn't working as well as it could, I can do something better". + +That is a ridiculously late stage to receive that kind of feedback. You want those feedback loops much closer to home because you want to be solving the right problems. + +That is why feedback loops are so important. The faster the feedback loop you have, the easier it is to understand the implications of changes, and the easier it is to find good solutions for the problems you are trying to solve. This also prevents over-engineering and over-complexity. From 7ec1a61ba2448a1bbd0bf32ce39e644493e98a83 Mon Sep 17 00:00:00 2001 From: Ambg05 Date: Mon, 10 Oct 2016 18:04:10 +0100 Subject: [PATCH 2/2] Update Creating a problem to find good solutions.md --- .../Misc/Creating a problem to find good solutions.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/21.From-Audio/to-fix-transcription/Misc/Creating a problem to find good solutions.md b/content/21.From-Audio/to-fix-transcription/Misc/Creating a problem to find good solutions.md index 3673e00..3665edd 100644 --- a/content/21.From-Audio/to-fix-transcription/Misc/Creating a problem to find good solutions.md +++ b/content/21.From-Audio/to-fix-transcription/Misc/Creating a problem to find good solutions.md @@ -1,6 +1,6 @@ -**Creating a Problem to Find Good Solutions.** +### Creating a Problem to Find Good Solutions -One of my favourite ways to solve a difficult problem is to put myself, or my team, in a situation where we have to solve the problem. This approach forces you to understand what is going on, and it forces you to think how you will address the problem. By doing this we are not thinking theoretically about a particular issue. We are dealing with a real problem with real scenarios, real outcomes, and real feedback. +One of my favourite ways to solve a difficult problem is to put myself, or my team, in a situation where we have to solve the problem. This approach forces us to understand what is going on, and it forces us to think how we will address the problem. By doing this we are not thinking theoretically about a particular issue. We are dealing with a real problem with real scenarios, real outcomes, and real feedback. The closer you can be with the problem you are solving, the more you can experience, the more you can visualize, and the better the solution you will devise.