Skip to main content

The "you guys must have changed something" Comment

As a developer you hear and witness several different things from users.  One thing I've learned over the past 20 years is you must have patience, especially with certain users.

It's amazing how many users are convinced that if something looks different or something "seems" to be missing on their screen that they assume something has changed in the code.  One of the comments I get a lot is, "you guys must have changed something in the code."

Well, when you're the only developer at a company you know when something has changed or not changed.  I try to explain to these users that "no, nothing has been changed in that program, we haven't made any changes to that in almost 6 months".  Then I get responses like, "well I over heard you guys talking about a username being misspelled, and maybe that's what's causing this."  My response, "No, that had nothing to do with the program you're in and that was on our test system anyway."

Most of the time in these situations you just have to be patient and let them believe what they're going to believe.  When the above example happens it's usually caused by them not having rights to certain features, but they try and convince me they've had the ability to do the feature 5 days ago.

"Hmmmmm, that's funny because when I look at the code it would be impossible for you to have that feature."  But again, they're convinced something has changed.  Anyhow, you give them the rights, and they "do" have the feature visible to them now.

Comments

Popular posts from this blog

2018 Goals Update

Wow, the month of January 2018 has flown by!  I cannot believe it's Feb 1 already!  But I will say I've been pretty happy with the progress of keeping my goals for the 2018 year!

Here's what I've kept to thus far:

1. Recite the Optimist Creed every morning (well at least during work days)

2. No more Mountain Dew in the morning

3. I've learned PHP and in the progress of learning C# and ASP.net (progress is good!)

4.  I'm almost finished reading Soft Skills by John Sonmez (trying to read 1 book per Quarter)

5. Family vacation to Disney has been booked!

6. Blog has been started!

Book Review: The New Psycho-Cybernetics

The book The New Psycho-Cybernetics by Dr. Maxwell Maltz is truly an amazing book!  This book should be read by everyone!  Whether your self-image is good or bad this book talks about taking steps to improve your self-image, live a longer life, and ultimately be happy!

I myself feel like I have a good self-image, my self-esteem is high and overall I'm an optimistic and happy person.  But I can see how a book like this can help me strive for higher achievements and help me to reach those higher goals!

For those with poor self-images and low esteem this book will benefit you immensely.  The book talks about several examples where people have been down, sick, lonely.  But have gone through the exercises in the book and come out with a much better self-image and becoming much more happy.

There are so many examples in the book its hard to cover them all and that's why I will definitely be reading the book again, as well as a reference for future inspirations.  Towards the end of th…

Ways To Avoid Developer's Burnout

Last night I read an article by Adris Azeez called Avoiding Burnout as as Software Developer and it got me thinking about the steps I take to avoid burnout, boredom, etc.

Several of the ideas Adris talks about are very similar to what I already do, but the main point is to change things up, take a break when needed, and if you're not in "coding" mode do something else that's productive.
As a developer for over 20 years I can honestly say there are days where the "ideas" and "code" just doesn't flow.  So here are a few things I do to still be productive at work when I'm developing:
1) Work on a "fun" project: sometimes when you work on the same project for several days/weeks, the brain needs a break.  I find that if I focus on something new it refreshes my mind and the creative juices start flowing again.  For example, I store several "fun" projects in my head to develop in the future.  Recently, I developed a new March …