>If it means I don't do any work on a Tuesday, who cares? All that matters is if I'm delivering what is expected of me (e.g. my spring tickets) and available fo

>If it means I don't do any work on a Tuesday, who cares? All that matters is if I'm delivering what is expected of me (e.g. my spring tickets) and available for communication. If I spend 4 hours a day working & 4 hours studying & playing mahjong online, what's it to you, you know? Enlightened employers realize this. It's not super common in the industry yet, but if you can find an employer who doesn't track your productivity by seeing how many meetings you attend and how often you're sitting at your desk alt-tabbing between VS Code and Github to look productive, you've hit the jackpot. Success should (ideally) be measured by value-add to the company, and dependability of the employee. Not many employers/managers know how to track value-add though. For a non-tech-savvy manager to measure the success of an engineer is difficult. They might look at your code commit and see that you removed 400 lines of code and added 20 and think of this as a "negative" impact because the numbers don't look nice. It's a frustrating aspect of the industry, but possible to work around if you work with decent people.