downscale? never mind.

Downscaling for the past 2 days hasn't helped much, to be honest. I am still stuck on the same bug despite extensive debugging, and my neck hurts. 

Timeboxing will force efficiency. As such, I am going to build a new schedule. Though it will still be focused on my biggest priorities -- master's thesis, piano pieces, and edX -- it will not eliminate anything. 

I should have learned by now that all downscaling does is create more local optimization problems :) And when you get stuck on the same problem forever, you start spinning your wheels. It becomes counterproductive. 

Though I will still find ways to squeeze in extra debugging for this push, I will no longer kill other aspects of my life. I am trying very hard to debug this before the weekend. But even if I do not, I will figure this out. 

All I can say is, I really hope this is a syntax problem, like I plugged something in wrong...and not a problem with 3D needing significantly different math than 2D. 

But I'm almost certain that this won't be the issue. 

Actually, it was cognitive friction preventing an effective debug. Subconsciously, I kept looking for shortcuts. This is why I did not step through every piece of the algorithm in sequence. And this is exactly why it's what I will do next. Find the first point of failure and work up to it on paper. Not a single step skipped. 

Now I am going to take a walk because my neck hurts. 

Comments

Popular posts from this blog

Unleashing my inner Disney Princess ✩₊˚.⋆☾⋆⁺₊✧ at the 2024 Disney Princesses Half Marathon

The 20-something types of Computer Science majors

The Evenstar