#9 End User Vagueness About Bugs

End users often come up with the bug report of the program as “It doesn’t work,” or “it’s broken, fix it!” and it becomes extremely vague for the programmer to decipher it. 

Instead the users should have told about the things like what screen they were on, what action they took, what action did they expected to execute and what actually happened, and what (if any) error message they got and also the what  browser and OS or platform, they were working on. With more information the users provide, programmers can fix the problem instead of going back to the users “Now what exactly were you doing?” query.

#8 Storing code in the database

Programmers generally have to write stored procedures and triggers and such, that is, putting code in the database. It made code debugging and maintenance too painful. It’s hard to beat running the good old find command, trying to track down the source of an error message, and being able to review file revision histories and such.

Also Read : 14 Most Dangerous Websites In The World and 20 Biggest Websites In The World