41

Dear Developers,

A. Please put your fucking functions in files with names related to the purpose of the functions.

B. Don't define your database management methods in your goddamn configuration file.

C. In addition, fucking document your shit at the top of the file if you refuse to abide by request A.

Someone is going to maintain or modify this code after you, and that person will have a hell of a time with it.

Comments
  • 2
    @kaqqao like sending query requests from ur app to a database server
  • 4
    I do this because the developer before me didn't give me any help having uncommented code with poor choice of naming conventions for both classes and variables, not to mention the random commented out code.

    My classes have some helpful comments, I try my best with the naming conventions, I've setup a git repo and I'll be adding in a pretty extensive readme.

    Just wish others would do the same :/
  • 0
    @kaqqao For example, defining your method to insert, select, etc from your database tables.

    Defining the connection settings in a config is great, but defining or including anything else is a huge hassle.

    Overall, projects that have an illogical flow irk me to no end.
Add Comment