What line of code is written first in Software development? [closed]

Question

Closed. This question needs to be more focused. It is not currently accepting answers.

---

Want to improve this question? Update the question so it focuses on one problem only by editing this post.

Closed 3 years ago.

Improve this question

When building software, we usually go through the requirements phase to design and all the stuff but when we start writing the actual code, how do we decide on which parts of the software will be build first . What is the first line of code to be written? I think we should start by writing tests for the functionalities and then continue working on making each test pass rather that diving straight into coding the actual application. E.g. We write tests for a login controller first before implementing the controller. I don't expect anyone to agree with me. I'm just trying to learn. Your thoughts will be highly appreciated.

Answer 1

If you are designing the application from scratch, you would need to write your Login, Design your framework, decide on your technologies to use. However, I have only done that only a few times in my career.

Normally, I do get to start with a new functionality that needs to be added/modified. If all my requirements are done, I am usually trying to find my POCO/Domain objects. I am then writing my Interfaces to get a blueprint for getting my estimates and then I get to write my test cases. After I have done my test cases, I do get into the crux of code.

Hope that may have provided you some insight.