Retrospective: How I spent hours of debugging code for a one-word bug
April 23, 2019 •3 min read
I then reverted the code back to a much earlier changeset that was checked in soon after the initial commit. The issue did not appear in this older changeset. I began modifying files incrementally, changeset by changeset, testing every modification until the issue re-appeared. Then I modified the files line by line until I found the line that triggered the issue.
It was a simple CSS one-liner:
position: fixed; needed to be
position: absolute; for the subsites only.
I still do not know why this caused the issue in iOS only, or why it presented the way it did. The change was initially made to fix some other positioning issue in the main site and in the sibling sites, and though the code for the other sites are so similar to the subsites that broke, this one line made all of the difference.
A career in this field is made up of many days like this -- where finding a bug is where the challenge lies, not the fix itself. The fix was simple but the real work was in finding it.
Companies Struggling with Employee Retention: Stop Blaming Job-Hoppers and Lack of Loyalty
March 6, 2019
Lessons from a Weekend of Building a React / Node App
July 16, 2019
Think others might enjoy this post? Share it!
I'd love to hear from you, let me know your thoughts!