Skip to main content

My resolutions for 2016: a short, sweet, focused list

Oracle Database Insider newsletter asked me to do another round of resolutions for the coming year. Since I love it when other people act as though they are interested in what I have to say, I told my manager I would have to clear my calendar for a couple of days and get this done. He agreed - so long as I did it during my week off between Christmas and New Years.

Oh, OK.

Before getting to the resolutions, I encourage you to subscribe to this very interesting and useful newsletter.

Here goes....

 1. Finish what I and we started. 

I have a long-standing and bad habit of getting all excited about new stuff: new programs, new applications, new websites, new programs…go, go go! But I am not so good at making sure that all the existing and really great stuff is “finished” (as useful and usable as it could be).

So for 2016, I resolve to consolidate what is already in place and make sure our users can get the most out of it. I am thinking about websites like Ask Tom, LiveSQL, PL/SQL Challenge, Oracle Learning Library, the Oracle Database Developer Choice Awards and…

2. Don’t let the screen own me.

Without a doubt, I spend waaaaay too much time in front of multiple monitors and screens (but at least I don’t do anything with my smartphone besides phone calls, texts and photos - and I do not own a tablet). 

Of course, I need to do that for my job, but I hereby resolve to get away each day, multiple times a day, to go outside, no matter the weather, feel the sun and wind on my skin, breathe deeply and celebrate the natural world.

Along the way, I will as a result think more clearly and write better code.

 I think.

3. Teach my granddaughter, Loey (age 4), to write code.

Nah, just kidding. 

I believe children should be kept away from computers and technology for as long and as much as possible (and that includes television). They will have loads of time to get sucked up into the Borg known as Civilization. Take your children outside instead, encourage them to play in the dirt (side benefit: boosts their immune system as they grow up into - possibly - a world without effective antibiotics), appreciate trees with them, explore the real world, not a world made of code.

4. Identify and help “raise up” the next generation of PL/SQL experts.

I might not look it, but I am old. Well, 57, anyway. :-) PL/SQL is going to be around - and utilized heavily - for many years to come. We need “young blood” - people under 40, I am thinking - to understand and champion “the hardest working language in software.” (I just made that up, by the way).

The Oracle Database Developer Choice Awards program is designed to do this, broadly, but I will also complement it with a focused effort.

 Of course, you could make it easy on me. Are you young(er), experiencing JavaScript framework whiplash, feeling like "Dang, those databases sure are important and sure should be utilized more than they are these days"?

 Then get in touch. Let me know you are interested in getting more involved with application development on Oracle Database - and perhaps PL/SQL more specifically.

 ........

 I could go on (anyone who's familiar with my books will attest to that). So tempting, but I will end with just one more:

 5. FOCUS

 I will keep my lists short and my priorities clear.

 So that's it.

 I hope you all have a very healthy and productive 2016.

 Spend as much time as you can with family and friends.

 Write code those same family and friends would be happy to maintain for you (!).

Comments

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...
24 comments
Read more

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...
8 comments
Read more

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...
4 comments
Read more