@TwoScoopsOfHot said:
Sounds like the CTO we had here a while back who said: "And software development is nothing, it's just typing."
And half the words are misspelled.
@TwoScoopsOfHot said:
Sounds like the CTO we had here a while back who said: "And software development is nothing, it's just typing."
@ender said:
Don't they only output crappy waveform while on battery?
Actually, don't answer that. The fact that anyone is treating the original comment as something other than a joke is making my brain hurt.
@Delve said:
We have a vendor right now that has quietly chosen to use an Access database (which is effectively free in an institutional context that relies on MS Office). I love that vendor. I have a picture of their staff on the wall. Complete with dart holes.
NCR provides a query tool called Teradata SQL Assistant as part of their Teradata database software. It's a pretty useful little program; one of its features is that it keeps a history of every query you've ever run--the date and time, the datasource, rows returned, processing time, and the SQL that you sent.
The tool only shows the most recent 200 queries. I went looking for where the data was stored to see if I could find an older query than that. Turns out they keep it in an Access database.
I'm not sure why this amuses me so much, but it does.
@mott555 said:
It was on TV, it must be true!
It's worse when the particular item in question, they're right about. Because you're torn between correcting their global ignorance, and giving them the real facts about the particular instance and reinforcing their global ignorance ... The below is virtually verbatim from an e-mail exchange a few weeks back:
My director: "It's bugging me that [subsidiary] is saying they can't get us that data because it's in an encrypted Access database, and only the fired employee knew the password. I see hackers on TV bust through password protection on all sorts of things in seconds! Somebody must know ways around that security, right?"
Me: "Well ... you shouldn't believe everything you see on TV about computers. That said, though--the encryption in Access prior to the 2007 version is very easy to crack. If you can get them to send me a copy of that .mdb file, I should be able to get into it without problems."
So, now my director has real-life evidence to support his impressions of the abilities of hackers from the media. Not to mention that he probably thinks I'm a hacker. I probably should have kept my mouth shut.
@b-redeker said:
well known business anti-pattern.
Wow--I think I need that book. In one of the reviews, I see my previous employer is amongst those whose mistakes are being analyzed as a warning to others.
It's amazing what executives can overlook from inside their cocoons. When I was about to be laid off from there in one of several rounds of downsizing, my manager (who had slithered off to a division that [i]wasn't[/i] being shut down) called me & said he was sure he could find me a spot in his new area. I pondered for approximately 1.5 milliseconds before telling him that I was planning to just accept the severance package, but thanks anyway. The death spiral was plainly obvious, and I really didn't want to prolong the inevitable. (Didn't hurt that this was ~7 years ago, when the job market was much better.)
@Jaime said:
@belgariontheking said:
When looking through explain plans, it looks like actually translates BETWEEN straight into its <= and >= counterparts.
BETWEEN was faster in the early '90s. I think I still have an install disk for SQL Server 4.2, I wonder if it will install on anything? There is a lot of twenty year old database advice floating around the Internet that doesn't apply anymore. I also know a lot of people who still make choices ignoring the fact that SQL Server has been doing ad-hoc batch caching for fourteen years.
Yep--gotta specify database & version on a question like that ... I just got an explain back from a Teradata 3 server that shows BETWEEN getting translated the same way, so there's another DBMS where it doesn't matter.