Skip to main content

Travel tip for Kscope15 and Beyond: Bring a water bottle!

I encourage everyone attending Kscope15 to take a vow:

I will not drink water from a disposable plastic bottle.

It won't be hard to find them. I imagine the conference organizers will provide them by the bushel.

But remember: every piece of plastic you consume will haunt the planet for hundreds, probably thousands of years.

The worst thing to use plastic for is something disposable.

And bottled water? Much of it is not even cleaner or "better" than tap water (though it will almost certainly have filtered out the nasty chlorine taste). Much of it is actually nothing more than filtered tap water (for example, Dasani-Coke).

Instead, bring a steel water bottle (best not to drink or eat out of plastic altogether - there are many inexpensive such bottles available via Amazon and so forth). Refill it as needed.

If lots of us foreswore plastic water bottles at Kscope15, we could reduce landfill and waste by hundreds of bottles. ODTUG would likely even save some money.

And if you forget or can't get hold of a reusable water bottle, no worries! Drink the water from your first and only disposable plastic bottle - and then reuse it for the rest of the conference!

On behalf of Planet Earth and all of its inhabitants, I thank you!

Comments

  1. How about the Dopper (http://dopper.com/) bottle. It is supposed to be made out of recycled plastic and you can even send your broken bottles so they can recycle those.

    ReplyDelete
  2. Thanks, Patrick. Sure, that's better than ahem virgin plastic. But the plastic is almost certainly leaching out chemicals into your water. It is far less inert and safe than stainless steel.

    ReplyDelete
  3. They also have a stainless steel version: https://dopper.com/shop/dopper-steel/

    ReplyDelete
  4. Hi Steven!
    Really, really cool that You care!!! Nice 2 see that Your try to change something!!! It is always a pleasure to read Your posts!

    I also found a cool bottle for myself: https://www.soulbottles.com/de/

    Keep on posting! You are great!

    ReplyDelete
  5. I am very pleased to say that ODTUG included a very nice glass water bottle in their conference bag. I should have expected no less. Great conference so far!

    Especially proud to have announced the Oracle Database Developer Choice Awards. Check them out: bit.ly/OracleDevChoice

    ReplyDelete

Post a Comment

Popular posts from this blog

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...

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...