You still use TP if you have a bidet though

Honestly, I think yes, it’s inevitable. The reason why is that keeping up with constantly changing technologies requires constantly learning how to do everything over again, and again, and again. It will get tiring eventually, and people will feel that learning the ins and outs of yet another social media app just isn’t worth it when they can already get by.

I say this as as software developer who sees a new tool or framework or language come out every year that’s bigger and better than the last, and I see the writing on the wall for myself. I’ll be outdated and just some old geezer who works on legacy tech stacks in 10-20 years, just like the guys working in COBOL or whatever now.

Just want to say that this is a fantastic answer. Pay attention to the parts about printing/downloading stuff. There are huge parts of America where you won’t get a reliable cell signal sometimes for hours.

If that’s the problem, then I would just use something like goimports to auto fix the imports every time I hit save. I never even see those errors so they don’t bother me.

I’m having a hard time envisioning a situation where testing my code requires a bunch of unused variables. Just don’t declare the variables until you’ve started writing the code that uses them…

Why in the world would you want to develop something that doesn’t follow the coding rules required by your org, just so you can go back and fix everything before submitting a PR? That’s just extra work.