We had a small theater here in DE do that about 10 years ago. Never got a chance to go there before they closed down. The building is now a Hollywood Video store. Irony at it's finest!
I'm finished with theaters now. I just picked up a 40 LCD TV that runs at 1080i native resolution (...thanks IRS). With the new DVD player that does 1080 up-verting on a HDMI interface and my 5.1 sound system, why bother going to the theater. It's not just the picture. I find the sound is not loud enough in some theaters.
The best part is the on-demand intermissions you can make. That extra large drink does have a cost past what you paid for it.
It's true what you say about a DBA that can't design a piece of paper that needs to be folded in half. Those aren't DBAs. They're Data Monkeys. In the case of SQL Server, take away Enterprise Mangler;) and they're lost.
A DBA that can't bring a schema to third normal form and write good stored procedures should be woken up in the middle of the night. They probably screwed up something on the system to cause it. I've seen these people too and we never hired them at the companies I was at. This is like hiring a UNIX admin that can't write shell scripts.
A DBA in my view is a "Database Analyst". I like DBE, "Database Engineer". If the A is for Administrator, that's all you get. If you can't do it all on a database system, you won't be able to do what little you know well.
Developers like you make great DBEs. At least you'll have the knowledge on how to keep the database running and stable. You don't let just anybody design or code in the database. After that comes data warehousing where the real fun begins.
You get more code spread all over the place when it's imbedded in apps that no one shares the code for. Yes, there's code reusability, yet I've seen very little of it. With stored procedures I, as a DBA, get to control and manager distribution. Most of the database developers I've seen can't write good procedures, let alone a normalized data schema. The think that it's easier to put data integrity in the app. The one that can write them well become DBAs.
If you don't want a multi-tier app, then stored procedures are the only way to go. The front end app should be the data entry, validation and presentation layer. The procedures do a second data validation and process business logic. At one shop we created a standard database with procedures and tables that all applications could use. When there were changes made to the procedures, we still presented the result set in the same way so NONE of the apps had to change.
The was another instance where we were developing an app that was constantly changed to support new user requests. By keeping the data access in the procedures, we were able to keep multiple versions of the application running using the same procedures. Try doing that in just code.
The biggest benefit is security access. Once the user gets access to the procedure, you don't need to give them access to the tables those procedures use. Keeps the power users from mucking up the data using Excel or Access.
Single view of business processes, better security and simplified modification of processes without recompiles and distribution of code. That keeps me from loosing sleep at night.
I'm 53 and saw the start of the space race in the begining of the Sixties. When those missions started, we stopped everything at my school to watch them. I hope the schools follow this just as as mush as they did back then.
...You mean like a group of 10 songs that are run through a "Heavy Rotation" in a 4 hour time slot? This is along with the single song they'll play from "Selected Artists"?
Do shuffle right and you get the wide range of variety with suprises that ramdom playback provides. I setup an old system in my family room with over 2,800 song and set WinAMP to shuffle play. I haven't listened to radio at home for the last 8 months. No comercials, no DJ's flapping their gums and none of repititous crap. That amount of music gives me over 8 days without a repeat!
With the breath of music I have on it, the ramndom playback comes up with some interesting runs of music that no DJ can even come close to.
The OnDemand system is a streaming video application that lets you watch when you want. This is PVR (...or VCR) without the record part. People will want to watch when they want and then on to the next show. A disk now replaces the tape cartridge.
I have a ReplayTV and it's great not to hear "...Honey, what's on this Tape?". Real Men Don't Use Labels!!! Now it's just check the menu and watch. The OnDemand part gives you one unit to connect and use just like the satellite solutions. The simpler the better.
The issue arises when the content provider controls the playback device. That's what got Replay into trouble. It sided with the consumer in all different ways. From automatic commercial deletion to opening their interfaces. DVarchive is a great example of this on SourceForge. Why hack the Replay system when you can just offload the content to a PC and access it there.
I hope I can continue to use my ReplayTV the way it runs now. If it dies, I still have a 40Gig drive out of it.
Slashdot Mirror
http://www.freenas.org/ ...You know you want to anyway.
...The_Terminal_Man by Michael Crichton.
The thanks to them are for the tax laws that allowed me to get a shitload back!!!
We had a small theater here in DE do that about 10 years ago. Never got a chance to go there before they closed down. The building is now a Hollywood Video store. Irony at it's finest!
I'm finished with theaters now. I just picked up a 40 LCD TV that runs at 1080i native resolution (...thanks IRS). With the new DVD player that does 1080 up-verting on a HDMI interface and my 5.1 sound system, why bother going to the theater. It's not just the picture. I find the sound is not loud enough in some theaters.
The best part is the on-demand intermissions you can make. That extra large drink does have a cost past what you paid for it.
Kai-Fu Lee may have been very smart but didn't have the common sense God gave a turnip.
.. Don't forget that this is the same country that loves Jerry Lewis.
... No, they're called Roomba.
Go flux yourself!!!
...does Donnald Trump own them a licensing fee for using it while on TV?
I'm a Slashdotter, not a Doctor!!!
The AARP Winter Nationals!
Ted is Short for Teddy. Must be a Boston, Massachusetts thing.
Ashcroft: Hey Tommy, can you do me a favor?
Ridge: What can I do for you Ash?
Ashcroft: Ted Kennedy grabbed my parking spot in the parking lot at Justice. Anything you can do so I can get back at him?
Ridge: I've got a GREAT idea!!!
It's true what you say about a DBA that can't design a piece of paper that needs to be folded in half. Those aren't DBAs. They're Data Monkeys. In the case of SQL Server, take away Enterprise Mangler ;) and they're lost.
A DBA that can't bring a schema to third normal form and write good stored procedures should be woken up in the middle of the night. They probably screwed up something on the system to cause it. I've seen these people too and we never hired them at the companies I was at. This is like hiring a UNIX admin that can't write shell scripts.
A DBA in my view is a "Database Analyst". I like DBE, "Database Engineer". If the A is for Administrator, that's all you get. If you can't do it all on a database system, you won't be able to do what little you know well.
Developers like you make great DBEs. At least you'll have the knowledge on how to keep the database running and stable. You don't let just anybody design or code in the database. After that comes data warehousing where the real fun begins.
It is the ONLY way to go!!!!
You get more code spread all over the place when it's imbedded in apps that no one shares the code for. Yes, there's code reusability, yet I've seen very little of it. With stored procedures I, as a DBA, get to control and manager distribution. Most of the database developers I've seen can't write good procedures, let alone a normalized data schema. The think that it's easier to put data integrity in the app. The one that can write them well become DBAs.
If you don't want a multi-tier app, then stored procedures are the only way to go. The front end app should be the data entry, validation and presentation layer. The procedures do a second data validation and process business logic. At one shop we created a standard database with procedures and tables that all applications could use. When there were changes made to the procedures, we still presented the result set in the same way so NONE of the apps had to change.
The was another instance where we were developing an app that was constantly changed to support new user requests. By keeping the data access in the procedures, we were able to keep multiple versions of the application running using the same procedures. Try doing that in just code.
The biggest benefit is security access. Once the user gets access to the procedure, you don't need to give them access to the tables those procedures use. Keeps the power users from mucking up the data using Excel or Access.
Single view of business processes, better security and simplified modification of processes without recompiles and distribution of code. That keeps me from loosing sleep at night.
Oh, and one more thing. NO SQL INJECTION HACKS!!!
...and bow before him for he is the Alpha-Nerd!
I'm 53 and saw the start of the space race in the begining of the Sixties. When those missions started, we stopped everything at my school to watch them. I hope the schools follow this just as as mush as they did back then.
...advertising air ships just like in Blade Runner. Bio-manufactured organs are comming next.
Remember it's an Extra Value MEAL.
Big Mac = 600
Medium Fries = 350
Medium Coke = 210
-----------------------
Total = 1,160 Calories
One 12 track CD = 13,920 CALORIES!!!!
You can feed a third world county's village with that calorie count.
...And a Sticky Bit at that.
...You mean like a group of 10 songs that are run through a "Heavy Rotation" in a 4 hour time slot? This is along with the single song they'll play from "Selected Artists"?
Do shuffle right and you get the wide range of variety with suprises that ramdom playback provides. I setup an old system in my family room with over 2,800 song and set WinAMP to shuffle play. I haven't listened to radio at home for the last 8 months. No comercials, no DJ's flapping their gums and none of repititous crap. That amount of music gives me over 8 days without a repeat!
With the breath of music I have on it, the ramndom playback comes up with some interesting runs of music that no DJ can even come close to.
Radio Killed The Radio Star...
He probably recorded Gigli too.
Woody Allen should sue for copyright infringement.
The OnDemand system is a streaming video application that lets you watch when you want. This is PVR (...or VCR) without the record part. People will want to watch when they want and then on to the next show. A disk now replaces the tape cartridge.
I have a ReplayTV and it's great not to hear "...Honey, what's on this Tape?". Real Men Don't Use Labels!!! Now it's just check the menu and watch. The OnDemand part gives you one unit to connect and use just like the satellite solutions. The simpler the better.
The issue arises when the content provider controls the playback device. That's what got Replay into trouble. It sided with the consumer in all different ways. From automatic commercial deletion to opening their interfaces. DVarchive is a great example of this on SourceForge. Why hack the Replay system when you can just offload the content to a PC and access it there.
I hope I can continue to use my ReplayTV the way it runs now. If it dies, I still have a 40Gig drive out of it.