Eat your own dog food

When I was at Oracle, there was a big push to use Oracle software for everything and anything we did. It was commonly referred to as "eating your own dog food", which is just gross. As nasty as that may sound, the concept did make a lot of sense: if Oracle built software products that were supposed to be so good, then why were they not being used internally? And even better - if the products didn't live up to their promises, then we had no one to blame but ourselves, and we could actually fix the issues.

I've decided to adopt that concept of eating my own, er, well, showcasing the product which we specialize in. Starting today, I'm happy to announce that sumnertech.com is now running on APEX!

Why did it take so long? Two years ago, when I started Sumner Technologies, I didn't have a lot of time or resources to set up my own instance of APEX to host my web site on. Thus, I took the path of least resistance: static HTML. Also, time was (and still is) scarce. Client work had to come first, and with a new baby, that left little time for extra-curricular projects.

It's still very much a version 1.0 site, as there are a number of new features that we will be adding over time, such as the ability to sign up for public classes (coming in early 2008!), a tips & tricks section, and an entire view into our internal system for clients.

Please let me know what you think and if you have any ideas that you'd like to see.

Comments

Bit Bucket said…

How nice was the contrast from what they used to say within PeopleSoft 'Drink your own champaign'

October 12, 2007 at 4:26 PM

Scott said…

I would have been OK with "use our own software"... :)

- Scott -

October 12, 2007 at 4:29 PM

Unknown said…

Champaign / pet edibles - One thing I can say is that there are a lot of people within Oracle that are using Oracle Application Express for their own internal applications.

As for the new site I think that it looks great.

October 15, 2007 at 6:40 PM

Custom Export to CSV

It's been a while since I've updated my blog. I've been quite busy lately, and just have not had the time that I used to. We're expecting our 1st child in just a few short weeks now, so most of my free time has been spent learning Lamaze breathing, making the weekly run to Babies R Us, and relocating my office from the larger room upstairs to the smaller one downstairs - which I do happen to like MUCH more than I had anticipated. I have everything I need within a short walk - a bathroom, beer fridge, and 52" HD TV. I only need to go upstairs to eat and sleep now, but alas, this will all change soon... Recently, I was asked if you could change the way Export to CSV in ApEx works. The short answer is, of course, no. But it's not too difficult to "roll your own" CSV export procedure. Why would you want to do this? Well, the customer's requirement was to manipulate some data when the Export link was clicked, and then export it to CSV in a forma

Refreshing PL/SQL Regions in APEX

If you've been using APEX long enough, you've probably used a PL/SQL Region to render some sort of HTML that the APEX built-in components simply can't handle. Perhaps a complex chart or region that has a lot of custom content and/or layout. While best practices may be to use an APEX component, or if not, build a plugin, we all know that sometimes reality doesn't give us that kind of time or flexibility. While the PL/SQL Region is quite powerful, it still lacks a key feature: the ability to be refreshed by a Dynamic Action. This is true even in APEX 5. Fortunately, there's a simple workaround that only requires a small change to your code: change your procedure to a function and call it from a Classic Report region. In changing your procedure to a function, you'll likely only need to make one type of change: converting and htp.prn calls to instead populate and return a variable at the end of the function. Most, if not all of the rest of the code can rem

Logging APEX Report Downloads

A customer recently asked how APEX could track who clicked “download” from an Interactive Grid. After some quick searching of the logs, I realized that APEX simply does not record this type of activity, aside from a simple page view type of “AJAX” entry. This was not specific enough, and of course, led to the next question - can we prevent users from downloading data from a grid entirely? I knew that any Javascript-based solution would fall short of their security requirements, since it is trivial to reconstruct the URL pattern required to initiate a download, even if the Javascript had removed the option from the menu. Thus, I had to consider a PL/SQL-based approach - one that could not be bypassed by a malicious end user. To solve this problem, I turned to APEX’s Initialization PL/SQL Code parameter. Any PL/SQL code entered in this region will be executed before any other APEX-related process. Thus, it is literally the first place that a developer can interact with an APEX p

Scott Spendolini's Blog

Search This Blog