At my (current) workplace we have a webfiltering mechanism powered by WebSense. I’ve ranted enough number of times on twitter about websense’s stupid filtering mechanisms & the bizarre classification that it uses to classify websites.
The day finally came to launch the product but there was no fanfare. No big payoff. No feeling of fulfillment. It was merely a quiet launch with one beta customer. You didn’t know what to do with yourself so you sat there all day refreshing a view on the database to spy on what they were doing. Answer: not much. The things they did do, they did wrong. They found bugs. They found ways to circumvent all of your carefully constructed system rules and validations. Not because they were master…
Background: For the past few days weeks, I have been working on a way to export selective data from one schema to import into another. Now the problem is that “selective” data refers to the data as stored across various tables in the custom application that I’ve been working on, with elaborate relational links between the tables ( if you’re curious, the table count on the related data was about 65) – so it was not just couple of tables that I had to export.
Steven Feuerstein has a nice little presentation on some golden rules for developers. They aren’t anything new, yet not many people read/follow them 🙂
Toad (acronym for Tool for Oracle Application Developers) is arguably one of the most popular and best known tools used by most people dabbling in Oracle databases ( or for that matter, most relational databases anyway). Toad’s reputation is so good, I’ve known few people swear by it and don’t even bother looking at other software, no matter how good.