 |
|||||||||||||||||||||||||||||||||||||||||||||||||||
|
Uh... what are databases for, anyway? This bit of foolishness yesterday: as a matter of policy, we don't provide user interfaces that allow end-users to make changes in data stored in databases. Huh? Changes in database data are to be done by one of two methods. 1. An automated feed from another database. 2. A manual change via SQL typed by a DBA in response to a change order. I didn't ask if the policy applies to configuration files stored on a hard disk. What are these people thinking? Why are we paying Oracle for licenses on a powerful, flexible, transactional system that we can't use for transactions? Why are we using $100/hr programmers to take spreadsheet data entered by $35/hr clerks and slavishly copy it into databases that cost $60k/year to license and $20k/year to run? This is the sort of thing people in "big cubicles" do to people in "small cubicles" for reasons that probably made sense in one small situation. There is no mechanism for me to fix that situation, because in large companies, "policy" is made by people who have thousands of reports -- and bucking policy isn't something that gets you promoted, so most of those thousands just live with it. Until complaints about the policy come from more than one location, it won't be reexamined. I don't care if I'm ever promoted. I guess that means I'm going to be the lightning rod. Oh, sorry. I'll just sit here quietly for a minute until my blood pressure returns to normal. |
Last modified: Friday, October 31, 2008 at 9:19 PM.
Tech resources |
||||||||||||||||||||||||||||||||||||||||||||||||||
