Just Tell Your Own Damn Story

Mikey Sanchez — Wed, 26 Jun 2019 05:59:15 +0000

A Mini-Manifesto

As a sort of “Mini-Manifesto”, I’m reminding myself that everyone has a different, valid and valuable take on just about anything.

This includes me.

This includes you.

As long as our discussions and contributions are productive, authentic, inclusive and non-intentionally offensive, then all hold a place and are welcome and encouraged in discourse regardless of skill level or experience.

Background

I’ve been a serial lurker in developer communities such as SlashDot, /r/programming, Stack Exchange, Hacker News, and of course, DEV for over a decade. I’ve gleaned so many amazing nuggets of information from the great people on these sites that I’ve always felt a sense of guilt for not reciprocating.

This is not to say that I have an over-abundance of confidence that my opinions, findings and experience is worth a damn to anyone besides me. I’m a serial drinker of the “Imposter Syndrome” kool-aid.

Yet in my voracious consumption of so many great tidbits of free knowledge I’ve come to realize that everyone who has been so generous in helping this silent, anonymous stranger is not so different from one another. We all suffer from imposter syndrome. We all are at different levels in our career trajectory, but we’ve all chewed the same dirt. We all appreciate the advice and guidance offered by one another.

Rationale

There are 2 big benefits I see in contributing to our ever-growing developer community:

It will help someone.

Whether you ever get any feedback on your contribution or not, be confident that it will have an impact. Someone is struggling with the same issue you’ve solved. Or someone has been waiting to read a different take on a technique. And that alone makes you and your perspective priceless.
It will help you.

The best way to further your understanding is to teach it. By breaking down a complex subject into more digestible chunks you benefit by reinforcing those concepts in your grey matter.

You may also get feedback which, whether positive or not, can reinforce your position or force you to rethink a long-held belief. Either way, you grow.

A Call to Action

Begin writing.

Anything.

In your own voice.

Today.

And publish it fearlessly because it matters.

What's the Title and/or Abstract of a Conference Session Proposal You Submitted That Got Turned Down?

Mikey Sanchez — Thu, 13 Jun 2019 15:34:39 +0000

I've had the privilege of presenting at Oracle conferences before, but it's not an easy process to first get approved. I've been denied (many) more times than approved.

So in the spirit of sharing disappointments, I'll go first. This was a session proposal I submitted for the IOUG Collaborate conference:

TITLE

Beyond the Backtrace: Using UTL_CALL_STACK for Easy PL/SQL Instrumentation

ABSTRACT

There are several open source libraries available for PL/SQL developers to easily instrument their code inside Oracle Database. Frameworks like ILO, Logger, and BMC_DEBUG are robust and stable offerings to get developers started with instrumentation. A common drawback in these libraries is their requirement to support older versions of Oracle, and thus don't take advantage of the new (in Oracle 12.1) package UTL_CALL_STACK.

The UTL_CALL_STACK package provides access to the Oracle stack that PL/SQL developers had to previously come up with clever workarounds to gain access to. This new API allows developers to easily know exactly where they are and where they were in the call stack, thus providing a way to wrap instrumentation code with calls to DBMS_APPLICATION_INFO and DBMS_MONITOR or DBMS_SYSTEM if needed.

In this session Mikey Sanchez will review the advantages of and ways to implement PL/SQL instrumentation in Oracle Database. A simple framework for utilizing UTL_CALL_STACK will be presented to make instrumenting existing PL/SQL code easy. He will also provide tips on how to use the UTL_CALL_STACK package to provide more insights than simple backtraces during exceptions.

DEV Community: Mikey Sanchez