- Feature Articles
- CodeSOD
- Error'd
-
Forums
-
Other Articles
- Random Article
- Alex's Soapbox
- Announcements
- Best of…
- Best of Email
- Best of the Sidebar
- Bring Your Own Code
- Coded Smorgasbord
- Mandatory Fun Day
- Off Topic
- Representative Line
- News Roundup
- Editor's Soapbox
- Software on the Rocks
- Souvenir Potpourri
- Sponsor Post
- Tales from the Interview
- The Daily WTF: Live
- Virtudyne
Admin
@Jeff S
I can totally relate to why Guayo briefly skims your posts and then responds on a whim. AS of late, the posts on the daily WTF have been rather extensive and very wordy IMO. There's not a lot there in terms of content, just a bunch of posturing and pontificating. "Look at me, I'm such a wonderful coder"...that sort of thing. I used to read through most of the posts. Nowadays, if it's over a couple sentences in length I briefly skim and move on. What they're saying really isn't that important after all.
Admin
It's great to skim long posts when browsing, but don't try to have an intelligent discussion with someone if you ignore most of what they say! (that applies to real-like conversations as well!)
Admin
Jeff S,
I feel for you, but ignore people's comments. A number of people here will shift the argument if they are incorrect or on shaky ground...
Admin
Cakkie, "but since the code only runs one time at a time, and already executes in less than 100ms," means that your code can only handle 10-11 connections a second. In other words, it is built with a growth potential severely limited - especially since it'll get even slower as more records are added. Once another department wants to start using it (or worse, it goes live on a webserver) you're only going to have to create these optimizations all over again. (A join like this can be a few milliseconds, more than an order of magnitude less than 100ms. How is that "negligible"?)
You are the WTF.
Admin
Well, easy :)
Currently the code is used by only one person, only once a week. They first have to check if the inputted data is correct (which they have to do manual (can take a few minutes per timesheet), and then it needs to be approved (what this code does) by a click on a button.
Say the number of people using this code at the very same moment doubles, no tripples, no tenfolds, then it would still run within 1 second. If they come bitching over that, I'll start complaining that it takes to coffee machine 15 seconds to prepare my coffee :p