June 5, 2019 at 4:08 pm
When I worked in a larger company and had to do maintenance programming, I learned to write better errors because I hated this kind of thing. SQL Server gives you all the information you need to put out a helpful error.
June 6, 2019 at 1:00 am
Now THAT's funny. Talk about "Team Work", eh?
--Jeff Moden
June 19, 2019 at 6:18 pm
I came across a stored procedure recently where there were 2 developers clearly arguing we didn't have source control for sql at the time of the argument (way before I started) and all dev work was on the live server, so all code changes were commented out as a rollback strategy (sigh) the comments went something like this...
I dislike some sort of multiple comment discussion inline. I think this is better in a header (or as a commit in a VCS). I prefer that a comment inline is just about the current state of code and why something is implemented in a certain way.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
June 19, 2019 at 6:19 pm
I think it is a ridiculous waste of time when someone comments on the obvious, like: counter++; // increment counter Really??
I blame professors are unis for this. That's the type of nonsense they asked me to write, or they gave extra credit for including.
Follow me on Twitter: http://www.twitter.com/way0utwest
Forum Etiquette: How to post data/code on a forum to get the best help
My Blog: www.voiceofthedba.com
June 19, 2019 at 7:05 pm
mike.sortino wrote:I think it is a ridiculous waste of time when someone comments on the obvious, like: counter++; // increment counter Really??
I blame professors are unis for this. That's the type of nonsense they asked me to write, or they gave extra credit for including.
Heh... totally inappropriate comment... I'd have commented "Bump the Counter". 😀
Such seemingly ridiculous comments make it easy to find the obvious because you don't have to shift your mind from looking at comments to looking at code, especially when you're under the gun.
--Jeff Moden
July 15, 2019 at 7:24 am
Still using RPG. It's Alive and well. We're currently running RPG IV on an IBM Power System with IBM i 7.3
July 15, 2019 at 1:37 pm
Still using RPG. It's Alive and well. We're currently running RPG IV on an IBM Power System with IBM i 7.3
We finally decommissioned our last RPG programs within the last 2-3 years.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
Viewing 7 posts - 151 through 156 (of 156 total)
You must be logged in to reply to this topic. Login to reply