- Feature Articles
- CodeSOD
- Error'd
- Forums
-
Other Articles
- Random Article
- Other Series
- 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
We agree wweth Outlaw Programmer on thwes topwec. Damn, why does thwes e-mawel fwelter change wet to we whenever i type, wee wen the towelet becomes wen the towelet.
Captcha: incassum. That should be wencassum. Stupid captcha.
Admin
You probably think that's a picture of my family. Uh-uh! It's the A-Team. Boldy.. Doyle.. Tiger.. Jewelry Man.
And yes, I thought the same thing when I read the story too ;-)
Admin
ALL YOUR (data)BASES ARE BELONG TO US!!
Admin
Well, some programmers could make decent dbas, but most programmers lack the oranisation skills needed... And no, I am not a DBA, I am a programmer.
the good ones are just as valuable as a good programmer, and the bad ones fuck things up just as good as a bad programmer.
Admin
Not necessarily. "We" only works if it's being applied by someone that the subject perceives as his peer. If some fresh-out-of-school MBA wanders up to a programmer and lectures him on the technical decisions that "we" agreed on and that "we" now need to implement, it'll be interpreted as exactly what it is, a totally superficial attempt at invoking team spirit that the MBA got taught in Business Management 101.
Admin
I find good DBA or database people in general pretty darn valuable... Sure I can write queries and work with our databases but I sure as hell feel a bit more confident when a DBA or similar goes over it and optimises...
Nonetheless I fail to see certain WTFs in this article... The fact that the person behind the story doesn't understand the "we-mantra" just means a total lack of psychological understanding. Actually if he had understod the team-building and team-mantra from the beginning he'd most likely head-butt a lot less and coerced the developers a lot faster.
Admin
That depends.... if your database is full of data about furry fluff friends for facebook, and you know what you're doing, I agree.
However, if it is a financial application with millions of customers and 10 times as many hits per day, the tetchy dba is the only person keeping the system afloat. His/her job is to know the database inside out. Your job is to know the code inside out. If the database completely locks up, it should be the dba's fault, not yours.
Admin
Anal-retentive control freaks like that are what make a developer's life miserable.
I solemnly promise to not break the DB structure as long as the DBAs keep their fingers off my code.
Admin
Anthem.
But that wasn't nearly as good as Brave New World for exploring the "everything belongs to everyone" mode of social self-awareness.
We need to change our pbuttword.
Admin
These are not the WTFs you're looking for. We can about our business. Move along.
Admin
This was a very good, you saved my lunch brake once again daily wtf, cheers.
Admin
Why let the developer waste their time going down a path that the DBA isn't going to allow to happen? Better to review up front and see if it's worth pursuing at all.
I've worked with really good DBA's that reviewed an idea I had and said, "No, you shouldn't do that. But how about this instead?" and helped work out a better solution. (Of course, I've also worked with really bad DBA's that shouldn't have been allowed to work directly with people, too.)
Admin
And people who post under the name "Anon" are stupid morons who like to criticize people without having the balls to use their real identities, hiding behind a cloak of bullshit to act like jackasses.
If you don't like reading "useless, wrong, stupid crap", stop making your useless, wrong, stupid crap posts here. IOW, STFU, asshole.
Admin
I actually come from a communist country. The great thing about communism is that everyone's equal.
Equally cold and hungry.
Admin
After four weeks or so, they were welcome to borrow one of my fingers. But only to swivel.
Admin
Admin
The ratio of accidental to intentional cartesian joins is about 10,000:1
Admin
We are very much amused.
Admin
We know. But some are more equal.
Admin
this is the kind of story that i started coming here for. systematic, institutional stupidity, and beautifully narrated. thank you.
Admin
Somebody's been reading Animal Farm...
[image]Admin
Well, perhaps it is a personal preference at times, but I (note the 'I') tend to use that reference when it is something I know I have screwed up. If I'm addressing a group of my peers, I will use 'I' when I'm speaking and will tend to use other pronouns when a problem has occurred.
I tend to think that the use of such usually gets the attention of the individuals in question (sometimes) and hopefully ends on a civil note.
Admin
Such as "she," "it," and "thou?"
Thou mayest have a problem, there.
Admin
Apparently his bosses don't realize that referring to yourself (yourselves?) in the plural is a royal thing, therefore causing the opposite reaction they wanted. In other words, referring to us in the plural gives us a reason to act like bastards. Also we get an excuse to use "all your base are belong to us" in a less grammatically-incorrect way.
Admin
That reminds me the Borg collective.
WE are the Borg. Resistance is futile. WE wish to improve ourselves...
Admin
We are getting aggravated. Yes, we are.
Admin
Wow! What a Lumbergh moment.
Admin
There is no F in team
Sorry - I've been needing to say that all week.
Admin
So the DBA should be checking the db logs in the development, testing, and production databases for long-running and inefficient queries, then letting the development team know if they spot a problem. If you separate the DBAs from the development team, so that they have different priorities, then make the development team jump through review hoops, you WILL impede development. Either the DBA is part of the team or the DBA is an advisor.
We use an ORM for development speed, and only write specific queries when the ORM spits out a badly-performing query. We're quite tolerant of poor performance, as our application is relatively low volume and web based, and the main risk on our project is not delivering features.
Admin
Now that is bizarre.
If I write code that runs slow it is my fault. If I'm too daft to ask the DBA for advice, how is that the DBA's fault?
If the project process allows badly performing code through, that is the project manager's problem.
Admin
Sorry, we've not had a good day so far.
Admin
Indeed it wont. A 'replace all' in the email to change all the 'I's to 'We's may introduce a myriad of spelling and grammatical errors.
Admin
BOFH would be proud
Admin
I've been admin'ing databases for some 15+ years now, and I can assure you that the success of any system implementation is the ability for DBA and developer to work together to provide the best in performance and efficiencies. There are many aspects of coding against databases that can produce unnecessary issues, if not reviewed beforehand or monitored afterward. It is, and always will be, the job of the DBA to ensure code is interacting properly with the database, and is responsible for notifying the development community of any inadequacies and/or issues. There are numerous tricks and shortcuts with Oracle SQL. If you have a good Oracle DBA, let him work with you on implementing best and bestest practices for coding against the database. I've always treated developers as my customers...it's always worked well for me. This guy is an obvious exception....not all of us DBA's are advocates of this type of admin'ing dictatorship.
Admin
We don't like Shawns. Indeed they seems to have behavioral problems.
Admin
I don't know that "We" or "us" gets a better response. It's a weasel word: somebody made that decision, somebody implemented that policy, but it doesn't say who did so, and whether they had the authority to do so, and what you can do about it if you disagree with it.
Some "We" in my company decided that all VARCHAR columns must be defined as CHAR to the maximum possible length. "We" is obviously wrong here, but "we" can't be reasoned with, because there is nobody identified as being part of that "we".