Skip to main content

Care to join "Team Feuerstein"?

So on March 17, 2014 I joined Oracle Corporation as an Architect.

Wow, do they have lots of things for me to do!

And I want to do my very best with all of it:
  • Publish articles, presentations, white papers that are accurate, are readable, and have no mistakes.
  • Share my PL/SQL utility and sample code (and make sure they are readable and have no mistakes).
  • Find - and notify developers - about useful blogs, code and anything else relating to PL/SQL.
It is quickly becoming clear to me that I can't do it all, all by myself. And everyone else at Oracle is just as busy as me.

So I have decided to create "Team Feuerstein" - a group of Oracle technologists who share, with me, a delight for PL/SQL and SQL, and a desire to help build our community.

While you will not be paid in hard currency for your efforts, I will be very grateful and you will get public credit for your contribution.

I plan in the future to provide a webpage where you can submit an application to join the team and list your specialties. But I've decided that there is no reason to wait until that is ready.

I can get started right away soliciting your help!

So if you are interested you can do one of two things:

(a) Send an email to steven.feuerstein@oracle.com asking for more information.

(b) Send an email to steven.feuerstein@oracle.com to volunteer as a team member and provide the following information:

  • Background on your Oracle experience: free form text, LinkedIn profile, etc.
  • Your technical strengths: for example, I can definitely use help with non-trivial SQL, regular expressions, XML, etc. Core PL/SQL knowledge is, of course, great, too!
  • Other skills of interest: I plan to record lots of videos and podcasts, so if you have experience with this (esp on a Macbook), I'd love to hear about it. Excellent English writing skills? That would be very useful.
  • How you would like to be identified publicly.
Many thanks in advance for considering this!
Steven Feuerstein



Comments

  1. Well, the bit about non-trivial SQL sounds much more interesting than trivial SQL ;-)
    Can you use a dane with no Macbook experience whatsoever?

    ReplyDelete

Post a Comment

Popular posts from this blog

Quick Guide to User-Defined Types in Oracle PL/SQL

A Twitter follower recently asked for more information on user-defined types in the PL/SQL language, and I figured the best way to answer is to offer up this blog post. PL/SQL is a strongly-typed language . Before you can work with a variable or constant, it must be declared with a type (yes, PL/SQL also supports lots of implicit conversions from one type to another, but still, everything must be declared with a type). PL/SQL offers a wide array of pre-defined data types , both in the language natively (such as VARCHAR2, PLS_INTEGER, BOOLEAN, etc.) and in a variety of supplied packages (e.g., the NUMBER_TABLE collection type in the DBMS_SQL package). Data types in PL/SQL can be scalars, such as strings and numbers, or composite (consisting of one or more scalars), such as record types, collection types and object types. You can't really declare your own "user-defined" scalars, though you can define subtypes  from those scalars, which can be very helpful from the p...

Three tips for getting started right with Oracle Database development

By "Oracle Database development", I mean, more or less, writing SQL and PL/SQL. I assume in this post that you have access to Oracle Database (which you can get via Cloud services, Docker , GitHub and OTN ). A. Use a powerful IDE, designed with database programming in mind. There are lots of editors out there, and many IDEs that work with Oracle Database. Sure, you could use Notepad, but OMG the productivity loss. You could also use a popular editor like Sublime, and then it get it working with Oracle. I suggest, however, that you  download  and install Oracle's own own, free, powerful IDE: SQL Developer . If you like to complement your graphical IDE with a command line tool (or OMG if you actually prefer  a command line tool to a graphical interface), you should also check out the relatively new and generating-lots-of-excitement SQLcl . B. Enable compile-time warnings and PL/Scope. The database has tons of useful functionality burned right into it, ready for...

Why DBMS_OUTPUT.PUT_LINE should not be in your application code

A database developer recently came across my  Bulletproof PL/SQL  presentation, which includes this slide. That first item in the list caught his attention: Never put calls to DBMS_OUTPUT.PUT_LINE in your application code. So he sent me an email asking why I would say that. Well, I suppose that is the problem with publishing slide decks. All the explanatory verbiage is missing. I suppose maybe I should do a video. :-) But in the meantime, allow me to explain. First, what does DBMS_OUTPUT.PUT_LINE do? It writes text out to a buffer, and when your current PL/SQL block terminates, the buffer is displayed on your screen. [Note: there can be more to it than that. For example, you could in your own code call DBMS_OUTPUT.GET_LINE(S) to get the contents of the buffer and do something with it, but I will keep things simple right now.] Second, if I am telling you not to use this built-in, how could text from your program be displayed on your screen? Not without a lot o...