5 ms·
I think the more basic point Is that if you want something you can’t get at work, you need to provide it for yourself. If you take a job that does not encourag
by devoutsalsa 4y ago
I think the more basic point Is that if you want something you can’t get at work, you need to provide it for yourself. If you take a job that does not encourage coding, it shouldn’t be a surprise you’ll do less coding, and it also shouldn’t be a surprise that you’ll need to code on your own time if you can’t meaningfully do it at work. My current role has involved a lot less coding lately, and I need to make time to keep my skills sharp and/or learn new things.
- cies 4y ago> if you want something you can’t get at work This is not about "something you can’t get at work". I have problems doing sex/drug/rock'n'roll at work, just seem not to be able to get to it. Hence it gets pushed to the wknds. This is about ensuring you can keep coding at work while making promotions. This is "work coding" not "side-project coding". >My current role has involved a lot less coding lately, and I need to make time to keep my skills sharp and/or learn new things. You seem to be okay with cannibalizing your wknd for work. Great that that works for you, but I think this should not be expected and is not the answer to OPs question. Also, I think it fits the workaholic mindset that I try to avoid altogether.
- devoutsalsa 4y agoI don’t work much outside of core hours, I just use downtime at work efficiently.