Have you ever sat down on your chair and debugged a really complex issue which took you hours and hours (even up to midnight) but you never really noticed the time? Well sure, technically not noticing the time is not realistic but let's just say time just flew. This is probably what they call as The Zone.
For the past couple days I've been looking into this really complex issue about how our transformations conflict with each other (which causes Redshift serializable violation) and it's really stressful and demoralizing not even knowing where to start. Remember folks if this ever happens to you, raise a flag if your circumstances can afford it! It really helps even if you just talk about the problem with some other person (and helpful for your mental health!). Anyway, so I was able to come up with a pretty good hypothesis and how I can potentially solve the issue. The next issue that I got stuck on was how. I wouldn't get into the details but I would say there is always a systematic way of doing something, a surefire methodology of tackling a certain problem. However, there are certain circumstances in which one can't afford it. So there I went, I tried to do a couple of things, reached out to a couple of people (to that person who helped me confirm my hypothesis, thank you btw!), and finally got a sliver of hope when something related to my hypothesis worked. Now this didn't necessarily mean it's fixed, not yet. As the issues are complex and intertwined with each other, it just means there's a hole I can further dig into. Hours passed and I'm slowly getting progress - until all of a sudden I noticed the issue is gradually getting fixed and it's already midnight.
I am just thankful it's finally fixed. This is just a friendly reminder that we can pretty much do anything if we really put our heart into it (sounds very cliche I know, but again at the end of the day it's really up to you!)
Happy Friday indeed.
For the past couple days I've been looking into this really complex issue about how our transformations conflict with each other (which causes Redshift serializable violation) and it's really stressful and demoralizing not even knowing where to start. Remember folks if this ever happens to you, raise a flag if your circumstances can afford it! It really helps even if you just talk about the problem with some other person (and helpful for your mental health!). Anyway, so I was able to come up with a pretty good hypothesis and how I can potentially solve the issue. The next issue that I got stuck on was how. I wouldn't get into the details but I would say there is always a systematic way of doing something, a surefire methodology of tackling a certain problem. However, there are certain circumstances in which one can't afford it. So there I went, I tried to do a couple of things, reached out to a couple of people (to that person who helped me confirm my hypothesis, thank you btw!), and finally got a sliver of hope when something related to my hypothesis worked. Now this didn't necessarily mean it's fixed, not yet. As the issues are complex and intertwined with each other, it just means there's a hole I can further dig into. Hours passed and I'm slowly getting progress - until all of a sudden I noticed the issue is gradually getting fixed and it's already midnight.
I am just thankful it's finally fixed. This is just a friendly reminder that we can pretty much do anything if we really put our heart into it (sounds very cliche I know, but again at the end of the day it's really up to you!)
Happy Friday indeed.