South Table Mountain Fire
This post is an attempt to document the South Table Mountain fire in Golden, Colorado. I have spent considerable time hiking on this particular mountain and have surveyed and updated a significant portion of those trails within OpenStreetMap.org (OSM). In fact, I was just up there a couple weeks ago starting to update OSM to include the most recent changes that Jefferson County Open Space had made to the trails.
Before I go any further, I want to give a huge shout-out to all the crews that responded to this fire and effectively controlled the burn area. 9News.com reported close to 70 firefighters from 25 organizations came together to battle this blaze. I'll call out @WestMetroFire because that's the main one I had seen posted, but I know they're far from the only ones out there.
As Golden residents, we thank you for your service and dedication!
There was news that one firefighter was injured while fighting this blaze. I hope that the injuries were minor and that individual is doing well!
Whenever I see news of a fire, I always want to see a map that represents the general area of the burn and what is around it. So this time I decided to take a swing at creating that visualization myself.
Note: These images are high resolution. Open the full image in your browser to zoom in and see the full detail.
My Journey Begins
I began an educational journey, with only a vague idea of my destination, and no road map to lead me where I wanted to go. My “journey” involves learning how to design and manage relational databases. Unfortunately, taking college level courses about database design only scratched the surface. I’ve heard the phrase, education can seem “a mile wide and an inch deep.” This statement reflects my experience in the majority of my classes. The depth of knowledge was simply not provided by most of my instructors. Time after time, I experienced a lack of responsiveness from my instructors. They either had good technological skills or good people skills, but rarely did they have both. They and the course material did not prepare me for working in the real world.
I have discovered database design is challenging and rewarding work. It is worth all the effort it takes to succeed. I realized the best way for me to succeed was to find a person working in database design who appreciates hard work and good questions. My challenge was to find that special person and create a relationship.
PostgreSQL vs. MySQL: Why we use PostgreSQL
I fully believe that PostgreSQL is the best choice for a reliable and high performance database. This post was inspired after reading a post on Udemy concluding with MySQL being better than PostgreSQL. There are a number of points I disagree with in that post so I decided to make my case of why I think PostgreSQL is a better choice in most situations. In this post I start by countering a few statements from the Udemy post, providing examples from my experience and other resources. Towards the end I go over a few of the PostgreSQL features that I believe makes it truly stand out.
If all you need is to support 3rd party software that supports MySQL (and not PostgreSQL), then you obviously don't have a choice and this discussion is irrelevant. On the other hand, if you're looking for a powerful, reliable, and open source relational database platform:
PostgreSQL is my recommendation.
Testing PostgreSQL Unlogged Tables for Performance
"Data written to unlogged tables is not written to the write-ahead log (see Chapter 29), which makes them considerably faster than ordinary tables. However, they are not crash-safe: an unlogged table is automatically truncated after a crash or unclean shutdown."
It's important to note that unlogged tables shouldn't be used for storing critical data. My use case for them is to quickly load data to staging tables before cleaning and reorganizing. I end up importing large amounts of data on a regular basis, so this is of interest to me. I decided to test regular tables vs unlogged tables by importing 6 months of NOAA's hourly weather data. You can read about my previous tests with this data here.
Revisting my Tool Set
It's been over two years since I first wrote about the tools I use regularly as a programmer. Some things have changed, others have persisted. In this post I go through my current tool set with some explanations of why things have either changed or stayed they same.
Some tools haven't changed a bit. Git, SourceTree, VirtualBox and Jenkins are four tools that I still can't live without. Also, my MacBook is now even older, but with a new SSD it seems to have new life.