12 Years of WaterProgramming: A Retrospective on >500 Blog Posts

Just over 12 years ago, on January 9th 2012, the first WaterProgramming post was published. It was written by Joe Kasprzyk who is now an Associate Professor at CU Boulder, but at the time was a graduate student in the Reed Research Group. The post reads, in it’s entirety:

Welcome!

This blog shares tips for writing programs and running jobs associated with using multiobjective evolutionary algorithms (MOEAs) for water resources engineering.  It will be informal, with posts on a number of topics by a number of folks.

Since that first post, there have been 538 posts on the WaterProgramming blog!

Since that time, the content and style of posts has naturally evolved alongside the groups research foci and training needs. As we transition into a new year, I wanted to take the opportunity to look back and study the 12 years of activity on the WaterProgramming blog.

In preparing for this post, I have downloaded the entirety of the WaterProgramming blog archive and performed some fun analysis to look more closely at what has been made over the years.

To those of you who are regular readers of the blog, thank you for the continued interest! To those who may be less familiar, I hope this post helps to give you a bigger-picture of what goes on in this niche corner of the internet.

New tools to support the blog, and our top posts of all time

Before going any further, I want to point out a few new tools we have developed to support the blog content and anyone who is interested in our training activities. Given the number of posts on this site, it may be difficult to navigate the different posts and topics.

To make learning with the blog easier, we created the Reed Group Lab Manual (which was highlighted in Andrew’s blog post last fall) that includes:

Now, to kick us off, I want to highlight our five most-popular blog posts to-date. The top five posts of all time, based on total views are:

  1. PyCharm as a Python IDE for Generating UML Diagrams by Tom Wild
  2. Converting Latex to MS Word docx (almost perfectly) by Bernardo Trindade
  3. A quick example code to write data to a csv file in C++ by David Gold
  4. Types of Errors in Numerical Methods by Rohini Gupta
  5. Running a Python script using Excel macros by Lillian Lau

Post length over time

Perhaps one of the most obvious changes which has taken place over the last 12 years is the change in average blog post length. The figure below shows the length of each individual post (blue) with the annual average post length overlaid (yellow).

At the start of it’s life, WaterProgramming posts could be characterized as bite-sized tips-and-tricks which were often 200-500 words in length. In the first year along, there were more than 80 WaterProgramming posts!

In more recent years, the style of post has evolved to be quite a bit longer often coming in at 500-1500 words. Consequently, the posting frequency has been reduced (see figure below) and we have stabilized to an average of ~40 posts per year (with there being 35 posts in 2023).

Our most common topics

While the original Welcome! post emphasized our focus on “writing programs and running jobs associated with using multiobjective evolutionary algorithms” there has been a large variety of different posts since then.

Here, I took a look at all of the blog post titles over the years, and have identified the most frequent words (see figure below).

Looking at this plot, one thing stands out very clearly: we like working with Python! The most-frequent words reflect the “WaterProgramming” title and are: Python, Data, Analysis, Borg, Code.

However, I also want to highlight the frequency with which our posts provide some sort of demonstration and/or training activity which is a focus for our group. This focus on reproducibility and open-science is shown by the fact that some of the other most-frequent title words include:

  • Training
  • Interactive
  • Example

Another theme revealed here is that we aim to keep the content accessible across audiences, with titles frequently including the words “introduction”, “basic”, and “simple”.

And lastly, I will employ a highly sophisticated (/s) data visualization technique to help illustrate the key WaterProgramming themes in a more appealing way: the word cloud.

Conclusion and Thank You

As I was getting established in the Reed Research Group, I personally found the WaterProgramming blog to be a priceless resource. Now, I am very glad to able to contribute to this site, be part of the community, and support others in their learning.

I want to close out with a big THANK YOU to all of the contributors over the years. You all rock. In the table below I want to acknowledge anyone and everyone who has contributed to this blog in this past, along with a link to their top blog post. The majority of these folks have moved on from the Reed Group (or were external contributors) who are off doing great work; the table below does not include their impressive titles or accolades.

In no particular order:

AuthorTop-Post
Joe KasprzykUsing a virtual machine to run 32-bit software on a modern PC
Jon HermanRunning Sobol Sensitivity Analysis using SALib
Julie QuinnFitting Hidden Markov Models Part II: Sample Python Script
Jazmin ZatarainVisualization strategies for multidimensional data
Bernardo TrindadeConverting Latex to MS Word docx (almost perfectly)
Keyvan MalekTaylor Diagram
David GoldMake LaTeX easier with custom commands
Rohini GuptaTypes of Errors in Numerical Methods
Lillian LauRunning a Python script using Excel macros
Antonia HadjimichaelNondimensionalization of differential equations – an example using the Lotka-Volterra system of equations
Andrew HamiltonBivariate choropleth maps
Tom WildPyCharm as a Python IDE for Generating UML Diagrams
Trevor AmestoyMarkdown -Based Scientific and Computational Note Taking with Obsidian
Jon LamontagnePlotting geographic data from geojson files using Python
Tina KarimiParallel processing with R on Windows
Jared SmithPackages for Hydrological Data Retrieval and Statistical Analysis
William RasemanMultivariate Distances: Mahalanobis vs. Euclidean
Jan KwakkelScenario Discovery in Python
Andrew DirksRemote terminal environment using VS Code for Windows and Mac
David HadkaIntroduction to OpenMORDM
Travis ThurberContinuous Deployment with GitHub Actions (or, What Gives Life to a Living eBook?)
Peter StormLaunching Jupyter Notebook Using an Icon/Shortcut in the Current Working Directory Folder
Calvin WealtonCustom Plotting Symbols in R
Anaya GangadharVisualizing large directed networks with ggraph in R
Josh KollatAeroVis Documentation
Tori WardCompiling shared libraries on Windows (32 bit and 64 bit systems)
Charles RougeEvaluating and visualizing sampling quality
Sara AlalamIntroduction to Borg Operators Part 1: Simplex Crossover (SPX)
Gregory GarnerSurvival Function Plots in R
Veysel YildizHow ChatGPT Helped Me To Convert a MATLAB Toolbox to Python and Learn Python Coding
Michael LuoRuntime Visualization of MOEA with Platypus in Python
Ryan McKellyCommon PBS Batch Options
MattConverting an SVG to EPS
Nasser NajibiWeather Regime-Based Stochastic Weather Generation (Part 2/2)
Yu LiUse python cf and esgf-python-client package to interact with ESGF data portal
Ben LivnehInterpolating and resampling across projections and spatial resolutions with GDAL
Raffaele CestariLegacy Code Reborn: Wrapping C++ into MATLAB Simulink

WordPress: How to post a Screenr/YouTube video

Update: As of October 2015, Screenr has been discontinued.

As a guide for other folks trying to post videos on this blog (and, I suppose, on WordPress in general), here is the workflow:

  1. Create an account on screenr. In order to make a video, simply press Record and follow the instructions.
  2. After your video is done, it will give you a link to a screenr video. You can simply post a link to this video and have the users navigate to it on their site. The cooler thing to do, though, is to embed the video on YouTube. So…
  3. Create an acccount on YouTube. Nowadays you can link your Google account so it’s very seemless.
  4. Back in Screenr, click Publish to YouTube. It will ask for your YouTube name and password. The video is automatically sent to YouTube, and you have to navigate back to the YouTube page to manage it. As it explains on the screen, it may take a few minutes for the transfer to complete.
  5. In YouTube, navigate to My Videos to manage your new video. One suggestion is to make the video Unlisted, which means that you need a direct link in order to watch it. In the Advanced tools, make sure Enable Embedding is clicked.
  6. Click Watch on Video Page to see what the video will look like inside YouTube. Then, click Share, and then Embed to get the Embed code. Copy it to the clipboard.
  7. Now we’re ready to make our WordPress post. Log in to WordPress. Navigate to the WordPress “dashboard” to create a new post (you want to be in the Dashboard to get all the advanced settings for a full post, not just the quick post editor). Type a description of your video. When you’re ready to put the YouTube embed code, open the “Text” tab in the editor and paste the embed code.
  8. Publish the WordPress post and you’re done!

Some WordPress Tips

When you log in to wordpress, there should be a gray bar at the top that has your username. If you click your username, you’ll be taken into a screen that has all sorts of helpful links on the left hand side. Here you can create posts and edit existing ones. The editor that you reach from this menu seems better than another editor I’ve seen pop up, so use this one.

A few helpful features:

  • “Upload/Insert” allows you to post pdfs, pictures, powerpoints, you name it.  You can upload documents you’ve already written, such as software documentation for example.
  • In the “Publish” box on the right hand side of the editor, you can set the visibility of a post to private.  Once the blog goes public, this will be important.
  • Please set “Categories” for your posts which will help organization later on.  You can add a new category, or use existing ones.  There are also “Tags” for more specific content organization, but we haven’t really decided how to use one versus the other yet.
  • The following page talks about posting source code on WordPress.
  • If you have changed a page (like I did with this one) and want to move it up to the top of the blog, just change its publishing date to today’s date!
  • Tags allow us to be more easily found through WordPress.  Try to add them if you can!

As usual please feel free to add more WordPress tips to this post as we go along!