Skip to main content

When Your Co-worker is Dying

This blog post is dedicated to a fellow work and friend of mine of some 14 years.

Ryan Andersen was diagnosed with Stage 4 Lung Cancer about 4 years ago.  The doctors told him he had about 8 months to live.  Ryan was a very unique individual, he spoke his mind and was a very good programmer.  I can attribute a lot of what I've learned in programming (especially in web programming) from Ryan.  We worked together close to 14 years and we became a very strong team.  Every once in awhile I come across some of his comments in our code and I just laugh.

In the workplace, it was a very tough situation knowing Ryan was going to pass away soon, but also try and get as much information from him on the projects he was working on.  We actually were in the middle of a software project that we marketed and sold.  I had the task of taking over, but imagine while you're working with your fellow co-worker, who doesn't think they're going to die.  It was tough.  Not as tough as what Ryan was going through though.  Every time I think about his death I get teary eyed.

Ryan passed away in January 2015.  He had a wife and 10 year old son at the time of his death.  He was only 47 years old.

Every once in awhile if I'm working on some project or code and I get stuck, I'll say a little prayer to Ryan to help me out :)  We miss you Ryan and thank you for all the help you've given me!



Comments

Popular posts from this blog

Alexa Is Listening, Recording, and Sending!

Check out this story where a couple in Oregon was having a private conversation and Alexa recorded and sent the conversation to one of their contacts!  They were not aware until the contact contacted them about what had happened.  The couple contacted Amazon and they verified the series of events.  But what's even more bizarre is the couple wanted to return their Amazon home devices but Amazon has not agreed to return the costs for the devices! Check out the article here  by Bruce Brown on  Digital Trends

Nonclustered Index in SQL Server

So, I've run into an issue with one of my queries because it takes about 40 seconds to run and according to the Recent Expensive Queries section of the Activity Monitor in SQL Server, there is a section of code taking up about 51% of the query.  First, let me say that I've been writing Transact SQL for quite awhile but have never ventured into the Clustered and NonClustered areas of forming Indexes.  I do use indexes on all my tables but that's just the regular Primary Unique key.  We've been using this query for awhile and it does work but when the result set is about 5K records it takes a little while to run.  So here's the actual query itself SELECT PartNo , SerialNo , HeciCode , ScanDate , OrderType , PoNo , po . IssueDate , SoNo FROM ScanHistory sh WITH ( NOLOCK ) LEFT OUTER JOIN trkRWPOHeader po WITH ( NOLOCK ) ON sh . PoNo = po . PONum WHERE len ( PoNo ) > 2 AND ScanDate >

Staying Fit As a Software Developer

One of the things I love about John Sonmez's book Soft Skills is that he has an entire section dedicated to Fitness! Fortunately, I've always been someone who has been active.  I played sports in high school, intramural sports in college, and still stay active playing golf, basketball, softball, skiing and more.  I also workout almost every weekday.  How does this help me? Well, for starters it helps me stay in shape.  As a software developer you're sitting at a desk a lot!  You can't burn many calories sitting at your desk!  My usual weekly routine is to workout every weekday for about 45-60 minutes.  I'll mix in free weights and some circuit training.  I might run a few miles here and there, but usually when I run it's on the weekends.  I try and play basketball every Wednesday night, and this is the best workout ever!  (just try and not get injured!)  You can lose a lot of calories playing basketball! (if you don't like basketball try racquetball)