How to understand requirements as a software engineer
Hi everyone, my name is Douglas Acosta. I'm a backend software engineer. This is my first article in a series that will become my profesional portfolio. Given that my previous work is subject to confidential agreements, I have created this space to share insights and perspectives about software development. Hope this is useful for you, thanks for joining. Let's kick off the today one. Requirements Why requirements are key? The most beautiful and elegant solution isn't worth anything if: It doesn't provide value Isn't right for the given problem For the first point, I'm going to give details in a future article. Let's focus on the right solution for the problem. A problem can be solved in multiple ways. Don’t get me wrong, I’m not trying to say that there is only one way of solving something (Of course, optimal solutions are a different discussion
Hi everyone, my name is Douglas Acosta. I'm a backend software engineer. This is my first article in a series that will become my profesional portfolio. Given that my previous work is subject to confidential agreements, I have created this space to share insights and perspectives about software development.
Hope this is useful for you, thanks for joining. Let's kick off the today one. Requirements
Why requirements are key?
The most beautiful and elegant solution isn't worth anything if:
It doesn't provide value
Isn't right for the given problem
For the first point, I'm going to give details in a future article. Let's focus on the right solution for the problem.
A problem can be solved in multiple ways. Don’t get me wrong, I’m not trying to say that there is only one way of solving something (Of course, optimal solutions are a different discussion
What's Your Reaction?
