Why is the most important. In 6 months nobody cares about the how. If it was made you can see what it does. But not why is does this. In software development the how is automatically recorder. The why, unless explicitly given attention, will be lost.
If you spend more time on the why, you either have to record it, or it will better stick in your memory.
At some point during the how you might find out it's not going to work this way. If you don't have a good grasp on why you were doing it, then it will take more time to figure out a different how.
I'm a Software Engineer based in Dublin. I love crafting software and experimenting with languages and technologies. I'm a #DevOps advocate and continuous improvement pursuer.
I think you made a great point here. The how is automatically recorded by the implementation and that is the only useful way of tracking it and make sure it stays relevant. On the contrary, the why is hardly recorded and is harder to keep track of. Keeping track of the why might help deciding whether the current how is no longer relevant or not effective at delivering the originally intended value.
Thank you for your take on this 🙇
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Why is the most important. In 6 months nobody cares about the how. If it was made you can see what it does. But not why is does this. In software development the how is automatically recorder. The why, unless explicitly given attention, will be lost.
If you spend more time on the why, you either have to record it, or it will better stick in your memory.
At some point during the how you might find out it's not going to work this way. If you don't have a good grasp on why you were doing it, then it will take more time to figure out a different how.
I think you made a great point here. The how is automatically recorded by the implementation and that is the only useful way of tracking it and make sure it stays relevant. On the contrary, the why is hardly recorded and is harder to keep track of. Keeping track of the why might help deciding whether the current how is no longer relevant or not effective at delivering the originally intended value.
Thank you for your take on this 🙇