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

The future of Oracle PL/SQL: some thoughts on Sten Vesterli's thoughts

Sten Vesterli published a very thought-provoking post on his blog: Please stop reading this post, and read that one. When you are done, come on back here for my thoughts on Sten's thoughts. OK. You read it. Here we go. First, thanks, Sten, for being such an interesting, wise, sometimes provocative voice in our community. Next, Sten writes: Now, on the one hand, I certainly agree that the vast majority of young developers are currently caught up in the modern version of a Gold Rush, which is: "Build an app using JavaScript, pay no attention to that database behind the curtain." But I can assure you that I still do meet young PL/SQL programmers, regularly, when I am at conferences and doing onsite presentations at companies. So, young person who writes PL/SQL: do not be afraid! You are not alone! And you are super-smart to have made the choice you did. :-) Next, Sten offers this advice to managers: I agree that PL/SQL is a "spec...
46 comments
Read more

Table Functions, Part 1: Introduction and Exploration

Please do feel encouraged to read this and my other posts on table functions, but you will learn much more about table functions by taking my Get Started with PL/SQL Table Functions class at the Oracle Dev Gym. Videos, tutorials and quizzes - then print a certificate when you are done! Table functions - functions that can be called in the FROM clause of a query from inside the TABLE operator - are fascinating and incredibly helpful constructs. So I've decided to write a series of blog posts on them: how to build them, how to use them, issues you might run into. Of course, I am not the first to do so. I encourage to check out the  documentation , as well as excellent posts from Adrian Billington (search for "table functions") and Tim Hall . Adrian and Tim mostly focus on pipelined table functions, a specialized variant of table functions designed to improve performance and reduce PGA consumption. I will take a look at pipelined table functions in the latter part...
31 comments
Read more