I can definitely relate to what you’re describing. There was a time when work felt more self-evident, but today, a lot of work is more abstract and ambiguous, which brings its own kind of exhaustion. For me, procrastination often stems from not being entirely sure what I’m supposed to be doing or what my real target is. It doesn’t help when management just says, “fix the problems,” without providing clear guidance.

One thing that has helped me is acknowledging that this uncertainty and anxiety are part of modern work life, and it’s okay to feel overwhelmed. The key is to remember that you’re a human being, not a machine. The work you’re doing isn’t necessarily easy, and that’s alright. Instead of rushing or being paralyzed by perfectionism, I try to slow down, break things into smaller tasks, and remind myself to relax. Clarity will often come in the process, not before starting.

There are no inherent “rules” in software development. These books are useless and a waste of time. They offer nothing but CS Dogma and are actually against freedom of expression.

It’s because you don’t understand their vision – classic idea guy redux

I’m not advocating one way or the other, but I would gladly take on the gardening duties :D