Just “deciding not to do tasks” is one option that works (or, as I like to say “never put off till tomorrow anything that you can get out of altogether”...) A

Just “deciding not to do tasks” is one option that works (or, as I like to say “never put off till tomorrow anything that you can get out of altogether”...) A much more powerful tool as a senior dev is to push back on pointless or stupid requirements. “No we will not build a video transcoder so you can upload 8K video files you your WordPress site that gets 85+% of its traffic on phone screens. Learn to resize video before you upload it, or buy that as a service from Brightcove et al.” (Yes, that is a real example of a requirement I pushed back on, because neither the customer nor the account manager understood the problem. One of my devs tried to push back and got talked over, before I put my foot down and said “No, not happening. Happy to explain I detail why if you’d like.”)