#Java developers question:
Having some order in a class where the public, private, static, non-static methods go, seems nice. At the last company I worked for, we had rules.
Yet. A method may easily ping-pong between static and non-static during development, from commit to commit, as the code evolves. Sometimes this is even true for public/private.
But moving the method around in the code will screw up the diffs, so this seems silly.
What is your strategy?