Updated: Jan 12, 2021
Solving problems, designing solutions will be your mainstay at work. “Code first” is not a great strategy. Understand from our team how Mithi engineers approach problems, challenges and requirements and craft efficient, effective solutions, which our customers love.
In this session we will work you through solving a sample problem by demonstrating the approach and steps.
We will also show you how a problem can be solved in an ineffective way, leading to long term issues of scale and maintainability (not to mention the loss in customer experience)
Solving a sample problem
Show how a poor solution is built
How to build a (near) ideal solution following the approach
Tools you can use
Scope Foundational Series Are you ready
Questions asked during the webinar
What is the difference between use cases and test cases?
A use case is identified in the initial stage, where you get a requirement from the stakeholders and you define the scope of the project or programme, whereas test cases are made to validate whether you are covering the use cases and special cases that are being handled using code.
If I know the solution, do I still need to take the same approach?
The flow that has been shown in this presentation will help you write the code or solution better. We have found this approach very useful and we try to follow this approach for any problem irrespective of scale. ou need to understand how to break down a problem, after which you define the flow chart, you write the test cases to validate whether the approach is correct and at the end you write the code.
Are there any tools available to test a program?
There are several testing tools available to test a programme. The test cases shared in this webinar are manual test cases. To check the solution, you can write automated test cases as well, you can write unit cases, you can use JUnit for doing it in Java, you can use CUnit if you are doing it in C. You can use Jasmine to do web test cases.
How do the various programming languages differ from each other as more or less their core theme is the same. What common approach should one follow?
The flow chart, code, test cases will be common, what will matter is how you write the code. The basics of programming is the same, the difference may only be in the syntax, and how well the programme has matured or what programming libraries are available for that language. In this webinar, we demonstrated C code. In C we have to write many functions ourselves, we have to iterate words, break the sentence into multiple words.
Suppose we were writing this in Java, there are many libraries available, there are many in built functions available like StringTokenizer or Split which can be used to break the sentence into multiple words and it can easily find the length of the word and give you the solution faster. So this approach will work for any programming language as well as any problem, from something small to a bigger project as well.