Man I gotta disagree with you there honestly. I actually get my best debugging done between midnight and 4 AM when it's dead quiet and nobody is texting me. Like last week I had this weird null pointer thing that I banged my head against for 6 hours during the day, then at 2 AM I saw it in 10 minutes. There's something about being half asleep that makes me stop overthinking and actually look at the variable names instead of assuming they're right. The coffee is key though, you gotta time it right or you'll just stare at the screen like a rock.

Using teeth can crack the dielectric, better to just use a sharp knife.

Half hour seems like a lot of time to just let mud sit. You're not worried about it drying out before you even get it on the wall?

Yeah I heard about that job from a buddy who works that area. 45 minutes per bolt is rough but sometimes the rust lock is just that bad. I had a similar one last year on a Ford exhaust manifold and it took me almost an hour with the torch and impact gun. The customer was watching me the whole time too which never helps. At least if the pay was flat rate you could make up for it on the next job. Still though that kind of stuff makes you wonder if it's worth the headache sometimes.

Oh man, this brings back memories of when I tried to learn Python by jumping straight into building a web scraper without knowing basic syntax. Spent two days wondering why my loops were breaking everything. Turns out I didn't even understand what a variable was properly. It's like trying to run before you can walk, you know? My buddy always says you gotta crawl first, then walk, then run with code. Otherwise you just end up frustrated and confused.