![Picture](/uploads/3/0/8/5/30851839/5929506.jpg?323)
Does it look familiar to you?
When I first learn coding, I though i is part of the syntax. because my teacher always use it in part of his for loop, make me scare of using other variable.
Then I learn Java and C#. I was told that "ALWAYS use Try Catch Exception in your code, to make your code look like a pro." But there is never a good tip or practice on what we should do with the exception. At top most is dumping the exception manifest in to log file.
Finally, Yeah I mean finally block syntax. Is your last chance to fix your crappppp! programmatically.
When I first learn coding, I though i is part of the syntax. because my teacher always use it in part of his for loop, make me scare of using other variable.
Then I learn Java and C#. I was told that "ALWAYS use Try Catch Exception in your code, to make your code look like a pro." But there is never a good tip or practice on what we should do with the exception. At top most is dumping the exception manifest in to log file.
Finally, Yeah I mean finally block syntax. Is your last chance to fix your crappppp! programmatically.
![Picture](/uploads/3/0/8/5/30851839/674690.jpg?323)
Why we always have this kind of Naming Convention our DB table with
Is this naming convention necessary in this context?
tbl ... and stored procedure sp...?
Is this naming convention necessary in this context?