> made me really want to find a job that was less pay but also that low in hours
This was a very large factor in why I quit - old job wouldn't let me cut back hours, even at reduced pay, even framing it as "leave without pay", so I had no choice but to quit to get my time back, and I had enough money.
As it is, I'm content staying in that "learning and broadening" mode, even though I'm 20-ish years in on my career.
I don't think I'll go back, unless I absolutely have to, or a project catches my interest, but even then, no amount of money is going to convince me to work so many hours or ever in an office again (another reason I quit was they wanted us back in the office, despite my being much more effective working from home).
> old job wouldn't let me cut back hours, even at reduced pay, even framing it as "leave without pay",
I was curious what your role was, at what the incentives might have been for your old job to refuse this.
In your about page I see:
> Previously a programmer in the DoD world
speculation: were you working for a contractor that needed to bill your time out by the hour to the government? So if you weren't working maximum billable hours, they weren't making maximum profit margin on your hours, compared to someone else who would?
No, I was in civil service. Something I've had explained to me since is that even if my boss wanted to (he didn't; very old-school thinking), they couldn't because my position wasn't "coded" for part time.
This was a problem I also bumped up against quite often as someone who has been doing "DevOps" things since before that term was coined, but the government very much wants to pigeonhole people and couldn't wrap it's head around someone with IT experience who was also a software engineer. Even with certs that I basically earned blindfolded, they wouldn't grant me a sysadmin letter, and I didn't want to re-code to IT/IM because I saw how burned out sysadmins got. The turnover in government IT was insane.
If I really wanted, I could go be a government contractor, but I've seen they still want even contractors on-site, and it's completely unnecessary. For now, I'm just "re-tooling" to tech stacks that have piqued my interest, exploring my options (eg, my brother the designer wants to build games with me).
Honestly, I'm not the first, and from people I've kept in touch with, I'm far from the last. Government agencies need a serious kick in the pants if they want to keep good talent. It's not so much about the money, that's always going to be below market rate due to the tradeoff in stability and benefits (and even benefits are dwindling), it's more about recognizing that WFH is a right, not a privilege, and being flexible in hours and horizontal job duty changes. I've watched many a better engineer than myself leave for greener pastures (Micron, Blue Origin, etc), and middle management is still in denial because they've been in the same role for 30+ years and think "nothing has changed", or if they do adopt business practices, it's always the worst ones (open floor plans, etc). FFS, I couldn't get the last project I worked on to enable CI on their GitLab instance.
This was a very large factor in why I quit - old job wouldn't let me cut back hours, even at reduced pay, even framing it as "leave without pay", so I had no choice but to quit to get my time back, and I had enough money.
As it is, I'm content staying in that "learning and broadening" mode, even though I'm 20-ish years in on my career.
I don't think I'll go back, unless I absolutely have to, or a project catches my interest, but even then, no amount of money is going to convince me to work so many hours or ever in an office again (another reason I quit was they wanted us back in the office, despite my being much more effective working from home).