Why PeteWhoDidNotTweet?

Well you can blame DBAKevlar.com for that! Plus the fact that I really just don’t get Twitter.  If I’m gonna say something that’s of interest, it’s gonna take me a lot more time than that silly 140 character limit (so there, you’re forewarned!) So when I refused to let people know what my Twitter handle was (yes, I did have one, but only for work!), Kellyn shared that wonderful hashtag with me – #PeteWhoDoesNotTweet. 🙂

Then I changed roles at Oracle. My new role combines many years of work in both the database and Enterprise Manager arenas to being a database architect in the Database as a Service / Database Lifecycle Management group in Enterprise Manager Product Management. I’m also the primary product manager for both BI Publisher and jobs in EM, so you can expect to see material on those areas on this site. The job also involves being the social presence for the group, both virtually as well as physically at conferences, as well as writing whitepapers, presentations and so on to exploit database features in DBaaS / DBLM.

And of course, if you are going to be the social presence for a group, then I guess you gotta tweet. So that noise you hear is me being dragged, kicking and screaming, into the TwitterSphere, and as a result I’ve reluctantly changed the domain from petewhodoesnottweet.com to petewhodidnottweet.com. 🙂

2 Comments:

  1. christopher peterson

    Pete, we have run into an issue when STIGing against the ORACLE 12c STIG checklist provided by DISA. it seems that there are no longer an scripts or automated process available to check the compliance of our various 12c databases. we have several sites world wide and are trying to develop a baseline DB that can go out, with an automated tool that various site personnel can use to check for compliance. I was wondering if Enterprise Manager had been updated with the 12c automated scripts and sql commands. Respectfully, Chris

Leave a Reply

Your email address will not be published. Required fields are marked *