For a long time, I like many other developers was in the habit of returning this from any method that didn’t need to return anything eg setters. I have stopped doing this and this is why.
For a long time, I like many other developers was in the habit of returning this from any method that didn’t need to return anything eg setters. I have stopped doing this and this is why.
This post is a quick writeup of the reasons behind password storage techniques, so I can refer to it instead of explaining a fresh every time. It is intended to be simple and easy so there is no excuse for not reading or understanding it.
As a developer, one of the things which consistently annoys me is hidden/none obvious dependencies. There are a number of reasons this annoys, me for starters it can really slow down writing tests (for example) when you have to manually trace through an object graph to figure out what you need to mock out. This need for manual tracing also impairs cognitive understanding increasing the time it takes to understand what is happening and quite often prevents your expensive IDE from helping you out. Code with hidden dependencies also has a high resistance to change with unintended consequences to minor edits popping up in seemingly unrelated areas.