Sunday, April 26, 2020

Hubble: A 30 Year "Failure"

Way back in the primitive days of post-WW2 America, astronomer Lyman Spitzer wrote a paper discussing the benefits of a space-based telescope. He spent the next couple of decades trying to convince anyone to help with the development of this telescope.

After many funding problems, a bunch of technical issues, an extreme delay caused by a Space Shuttle disaster (that traumatized almost half of U.S. school kids, including yours truly) and a sky-rocketing budget, on April 24, 1990, NASA finally launched the Hubble Space Telescope into orbit.

Hubble has had a somewhat difficult history. It was a very ambitious undertaking with a lot of moving parts that had to be precise to an extremely small degree. It had plenty of naysayers, and the cost overruns made it an easy target for jokes about NASA and budgets.

But the HST is an instrument that is going to significantly improve our abilities to look further into space than we've been able to, and we were going to get back some AMAZING pictures.

And then....

Credits: Left: E. Persson (Las Campanas Observatory, Chile)/Observatories of the Carnegie Institution of Washington; Right: NASA, ESA and STScI
Credits: Left: E. Persson (Las Campanas Observatory, Chile) /
Observatories of the Carnegie Institution of Washington;
Right: NASA, ESA and STScI
The initial results were quite a bit underwhelming. The jokes took on a whole new life, even prompting Jay Leno to joke that Hubble should be shot down and put out of its misery. The project was a bust. 

But fortunately, NASA has some pretty smart, persistent people working there. They realized that there was a problem with the mirror, and, since HST was designed to be manually serviced, they set out to do just that. It took a few space walks to get the mirror fully corrected, but after just the first fix in 1993, they got...

Credits: NASA
Spiral Galaxy M100 - Before/After 1st Fix
Credits: NASA
Hubble was working a lot better. 

In the ensuing years, Hubble has been upgraded and significantly improved. It has made over a million impressive observations, made numerous discoveries, significantly increased our knowledge of our universe, given us stunning images to look at and sparked an interest in space. Hubble is a pretty impressive redemption story and has become an unimaginable success. Not too shabby for a project that was only supposed to last for 3 years.

The James Webb Space Telescope has some pretty large shoes to fill. 

Happy 30th "Birthday", Hubble!


Hubble's Deployment
The Hubble Space Telescope, seen from the space shuttle 
Discovery during the observatory's deployment 
on April 25, 1990.   (Image: © NASA)

Jupiter Moon Transit, January 24, 2015
(Image credit: NASA/ESA/STScI)
Cosmic Reef
Hubble took this image, titled "Cosmic Reef," 
released April 24 to celebrate its 30th anniversary.  
(Image credit: NASA/ESA/STScI)

And a big THANK YOU to NASA, the ESA, the Goddard Space Flight Center and everyone else involved with Hubble.

Friday, April 17, 2020

Goodbye to an Old Friend

Today, I said goodbye to one of my oldest friends; a friend that has been with me for almost two decades.

This friend came along at the beginning of my software development career and has seen me through the many ups and downs of my path as a professional geek. When my youngest child was born, this friend was already there. Many years ago, this friend was destined for permanent retirement; thrown out like common refuse. Worthless. Headed for oblivion. But I saw value. I came to the rescue.

Home to home and half way across the state, this friend has followed me. It has been a rock and a comfort for me. I have battled many dangerous enemies with this friend. It has witnessed many of my adventures. This friend has helped me to face many challenges.

Sadly, it's time to say goodbye.

When I first found this friend, it was in a professional setting. Over the years, the friendship has moved to mostly leisure time.

The COVID-19 Quarantine has given me a chance to reconnect with this friend in a way that I haven't really experienced much in those ensuing 20 years. The last three weeks of Work-From-Home have given me the chance to spend a great deal of professional time with this friend, as opposed to the countless hours of fun and games this friend has been there for.

But the decision was made to move on before this craziness began. Commitments were made. Other companies were engaged to implement this split. I feel a little bad trading this friend in for a newer, younger model. But it had to be done.

My friend of 20 years will be leaving me today.

Old Friend
Goodbye, old friend.

I am frankly quite impressed that it has made it this long. Only ONE of its siblings survived this far, and that one met its end about 3 years ago. I wish I remembered the brand. I believe my brother and I purchased office furniture at Office Depot. We bought several of these chairs, and then a couple of Executive Chairs. All of them lasted MUCH longer than I ever expected them to. Whatever it was, it was a very impressive brand.

But, alas, it is time to move on.

New Friend
Hello, new friend.

I can only hope that this new chair is able to form the same long-lasting bond that the other one did. It's not as fancy as the old one was, but, so far, it's comfortable.

Time will tell.

Friday, March 13, 2020

What A Week!

Last Tuesday morning (March 3,2020), a little after midnight, my phone alerted me that there was a Tornado Warning in the area. I turned on the TV just in time to watch the News Channel 5 station get hit dead on by a tornado. ( and there's the Reporter's view ).

Shortly after that, it started raining pretty hard at my house, and the lightning flashed to a green sky. I knew it was coming our way.

I ran to get my wife out of bed and get downstairs with our son. We made it about halfway there before we lost electricity. The tornado touched down about a thousand feet from my house. It was over pretty quickly.

It was late, but my neighbors were out checking on each other. It was really too dark to see the full extent of the damage, but my block fared better than just a block over. Amazingly, I don't think anyone was seriously injured, but we did have a lot of downed trees and damaged houses.

We got electricity back yesterday.

Community response has been TREMENDOUS!

The day after the tornado hit, a friend of mine came over to help me cut up some trees. While we were doing that, another guy came up with his chainsaw to help cut. He didn't want money. He just wanted to help. Then we had volunteers from all over come into the area to help with cleanup. They finished cutting up my downed trees and hauled all of the stuff out to the street. All within just a few hours. The city has been coming by to haul off the debris.

Nashville Electric Service has put in a HEROIC effort and got our power back on.

My wife and I have been living out of hotels this week. I have some very good things to say about one, and some not so good things to say about another. When I get a chance this weekend, I'll post up some of the photos I took and videos I found, and I'll add a little more detail to my post.

There's still a lot of cleanup to do. The school my wife teaches at was severely damaged and classes had to be relocated. And there are other houses and areas of town with A LOT of damage still. A neighborhood just a few miles away from me was pretty much flattened.

We got lucky.

And despite the destruction, the people here are another reminder of why I love living in this town.

Thank you, Nashville.

Saturday, February 29, 2020

Happy Leap Day!

To be today, a year has to:

- Be divisible by 4
- NOT be divisible by 100
    - UNLESS it is also divisible by 400

Since 2020 meets the requirements:


HAPPY LEAP DAY!!!


... or as it's known to some who are finding out today that they messed up a date calculation somewhere,
March 1.

Sunday, February 2, 2020

Even More Date Masking..... Sorta

Today is is the 2nd day of February in the year 2020. And just like any palindrome, this means that it's written the same both forwards and backwards.

Today is a Palindrome Day!

Palindrome Days are pretty rare, except for the first few centuries of a new Millennium, which is where we currently find ourselves. I was here for the start of this Millennium, but (...since I don't want to make my vampire traits overly obvious and draw the attention of Buffy & Friends...), I doubt I'll be here for the start of the next one.

What makes this one pretty cool, is that it doesn't matter which of the two main maskings you use, mmddyyyy or ddmmyyyy, today will be the same. It's also pretty much the only day within my lifetime that the non-ISO date formatting simply doesn't matter.

Since I'm in the U.S., and we want to be different from pretty much everyone else, I commonly see my standard American mmddyyyy masking. That makes today 02022020. Or if you reverse it, it becomes 02022020.

But say I was looking at today from somewhere that is pretty much the rest of the world. Today is ddmmyyyy: 02022020. It still gets to be a palindrome!

It's also the 33rd day of the year AND there are 333 days left in the year.

Courtesy of https://www.pinterest.com/pin/523684262891075625/
Geek Overload = 11!
Since my brain has already exploded, this morning, at 02:02:20 UTC (or your local timezone if you're cheating), we can kick that palindrome out to a time component.

What if we go with ISO-8601 standard formatting: yyyymmdd. That's 20200202. The digits shift by a character, but we're still a palindrome. We have hit a palindrome date in 3 different formats!

This also makes today a Global Palindrome Day!

Our last one was November 11, 1111. I wasn't there for that one either. And our next one won't occur until 12/12/2121. Oddly enough, my son's birthday is December 12. But that date is slightly above the Guinness Record for Oldest Person. Who knows. At that point, he'd be over 120 years old. It would be pretty cool to cement a fairly interesting and likely unique Guinness Record.

But, once again, I offer you a very geeky Happy Global Palindrome Day!

Tuesday, January 28, 2020

Crystal Reports Permissions, Oh How I Hate Thee!

At work, we are decommissioning our Crystal Reports XI server and migrating to an SSRS 2016 server.

Permissions in Crystal Reports are a great big pain in my backside. 

That is all.

Thursday, January 16, 2020

T-SQL Tuesday #122 - Impostor Syndrome


This is the first time I've participated in a T-SQL Tuesday, and I need to start with an apology for being late. I know I'm technically violating the rules by several hours, so I don't expect to win the massive prize that these come with, but it is what it is, right?

The irony of my tardiness is that a large part of the reason I'm late (and the primary reason this is my first T-SQL Tuesday) is because I was waffling about whether or not I had anything useful to contribute. It feels a little odd to realize you are doubting your ability to talk about Impostor Syndrome.

On to my Origin Story:

 I've been into gadgets for pretty much my entire life, and my dad did his part to encourage my curiosity. He grew up working on cars and motorcycles, and he liked gadgets, too. The 80s provided him with plenty of geeky little things to play with. Fortunately, he was an airline pilot and had a little bit of disposable income for those geeky toys, so he could vicariously get his techie fix through my brother and me.

When I was a kid, I cut countless little snippets of wire for various iterations of the Electronic Lab Kits from Radio Shack (one of the BEST stores EVER). I disassembled numerous RC cars, so I could see how they worked. He bought a Commodore 64 and subscribed to Family Computing Magazine. I'm betting I'm not the first person to use those things to teach myself BASIC. I was off to a pretty geeky start.

In high school, I got two big things: 1) a serious girlfriend (who became my very patient wife), and 2) my pilot's license.

When it was time to pick a college, my mom wanted me to follow my geeky leanings and learn to be a programmer, but in the early 90s, a Computer Science degree was pretty much learning C and FORTRAN. No thanks.

After graduation, I decided to follow in my father's footsteps. I was going to be an airline pilot, too.

I immediately went off to Flight School, and for the next 6 months, I earned a few more certifications and became a Flight Instructor. I had been deemed skilled enough to teach other people how to fly airplanes. Cool, right?

I still wanted an airline career, so college was a Bachelor of Science in Professional Aviation . While there, I was also a Flight Instructor for other students in my same program. Several of my students are zooming around the skies today for Delta, United, FedEx and others. I was good at it. I knew what I was doing.

In the mid 90s, I got my nice, new degree, and I finally had enough qualifications for a move to the airlines. But it wasn't what I expected it to be. I didn't enjoying it as much as I enjoyed teaching, and a decent pilot salary was still about a decade away; it wasn't enough to feed myself, much less a wife and soon-to-be kid. I wasn't sure what to do with myself. Pardon the pun, but my life was kind of in a holding pattern.

 At the time, my little brother (who DID listen to Mom) owned a web development business and was looking for some help. He asked me to assist part-time, which shortly turned into a full-time need. I was enjoying myself, and didn't realize that I had just ended Career #1 as a pilot and started Career #2 as a programmer.

But this isn't where my Impostor Syndrome started. I knew that I was new and that there was a whole lot I didn't know; my expectations of myself were at an appropriate level.

It was a small company, so I learned way more than just how to program. I helped set up our network (a few times, since we moved). I had to administer all sorts of computers, including our application servers and databases and our workstations. When we acquired a company that customized portable computers (now called tablets) for pilots, my aviation knowledge turned me into a Subject Matter Expert and I became a lead for R&D. I was doing well and feeling pretty good about my ability to contribute.

And then the events of September 2001 made it difficult for both aviation and software development companies. We had to close a few years later.

I was a contract web developer for a few years, then landed at a Background Screening company. THAT is where my Impostor Syndrome kicked in. For several years, I was a software developer, then I did Support, then Business Intelligence (due to my earlier curiosity about our data), then back to Software Development. I learned a tremendous amount about all sorts of things, but I never felt like I knew enough about whatever it was I needed to know at the time.


I ultimately left there to get back into data, and since then, I've bounced back and forth between Software Dev and Database Dev, all the while, proclaiming that I couldn't help with X problem because I didn't know enough since "I am not a DBA". Which was usually followed by me researching whatever the problem was and ultimately helping anyway.

Throughout my career, I've worked with some VERY smart people. My curiosity has led me to read and follow other VERY smart people. This really hasn't helped me feel any better about my own skill level. I'm essentially a member of the unwashed masses who are "self-taught". My background and professional education are in Aviation, not Computers. I don't deserve to be with these people. Pretty soon, they'll figure out how clueless I am, and I'll be done. Humiliated and cast out.

That's pretty much the way I've felt for the last decade. I've worked many extra hours and done a ton of extra work so that my bosses won't discover that I'm not qualified for my position and should be fired on the spot. I started this very blog several years ago with the express purpose of being more visible and vocal for other devs, but I haven't written near the content that I wanted to because I've often feel like I don't really have anything to add to the conversation. For the last couple of years, I've wanted to speak at conferences, but I've procrastinated submitting my topics because I didn't want to try to talk about something I was clueless about (even though I did quite a bit of research to prepare). Too often, I sabotage myself because self-doubt creeps in.

 Last year, I realized that I've been working in IT over TWICE as long as I was an active pilot. I also can't really compare my skill level in Aviation to where I am in IT. They aren't the same. IT is a VERY broad field. There's way too much to know for any one person to know more than a slice of it. And Google has made me see how much there is that I just don't know.

Several years ago, I started going to a few conferences and actually began meeting some of the bloggers and writers that I had idolized. I discovered that they are every bit as brilliant as I thought they were, but they're also human and not the keepers of impossible volumes of knowledge that I'd built them up to be. They'd likely be the first to tell me that they don't know everything. And that's OK. The secret to being really great at something is to recognize your own weaknesses and cover them with other people who excel in those areas.

That realization has allowed me to understand that they are still extremely qualified EXPERTS, despite not having every answer, I need to learn how to accept the same from myself.

Today, I AM a DBA. And I'm still a Programmer, too. I'm doing what I enjoy doing. I'm not as fast as some people, but I don't have to be. I also don't know how to fix every problem that comes my way. But I don't have to be that person either. I still don't feel like I'm always the best person to fill my seat, but I'm beginning to realize that I know a bit more than I think I do. And if I don't know something, I find the answer. I try my hardest to make sure that my responsibilities are covered to the best of my abilities.

It's OK that I don't know everything. Nobody expects that of me. It's not realistic. I just need to convince myself to hold me to the same standards, expectations and limitations of everyone else.

It's hard sometimes.