Is consistency better than best practices?
Scenario 1:
Codebase uses Util classes with static methods. In order to write unit tests for classes that call these static methods tools like PowerMock might be required. Is it worth writing the new "Utils" classes as spring beans with non static methods, which will make testing easier or keep it consistent?
Scenario 2:
"RESTful" API is not really RESTful. However, new calls are added frequently to the API. Do you make the new calls more RESTful or do you keep them consistent?
>>62218186
>15L whisky
I wonder if its any good...
>>62218202
It would probably be just as bad as every other whiskey
>>62218186
is this real?
>>62218620
This site is for those over 18.
>>62218202
it is. otherwise it wouldn't say premium quality
>>62219499
Can't argue with that.
Consistency over anything.
Nothing is worse than the API flipping shit around. I remember working with an API that returned 0 for true and 1 for false. Then their newer API commands returned "true" and "false".
So fucking annoying having to go read docs everytime because they couldn't just remain consistent. Is this command returning an integer or a string???????
https://www.youtube.com/watch?v=XehwSM9n_Ko