Anonymous wrote:
Anonymous wrote:
Anonymous wrote:
Anonymous wrote:
Anonymous wrote:I don’t get it. This was what it was like when I had my kids in the late 2000s.
As someone who worked in the late 2000s, we were doing schedule shifts back then to avoid rushes at building entrances.
Sounds like they're just trying to get people to quit.
+1
Also had kids late 2000s. Spent lots of $ on before and aftercare for all of the elementary years, which most of my coworkers haven’t done due to flexible schedules. Also no maternity leave. So there were differences- we didn’t have a set start and end time, and agree that sucks and is punitive- but other things sucked working full time with kids.
But yes I agree a defined start and end time is bad for all of us. I might have to look into other transportation options if we go that way.
I have been in the labor market for 35 years and staggered work start times and AWS has been a major thing for that entire period. There are very few jobs where having everyone in the office at exactly the same hours is beneficial. This is all idiocy.
Huh. My first federal job at DoJ ran from 1997 to 2001. In that position, I worked closely with clients in USFWS, EPA, Energy, USFS, Dept of the Navy and probably some others. I can think of zero, literally zero, of these (non-admin/non-HR) people in all of those agencies (let's say GS12 and above) who worked from home. Like, none. I know because we'd meet all the time in person downtown. I can think of two EPA scientists who weren't there after 3 pm. Literally everyone else was in the office if we needed a 4 pm emergency meeting. Everyone worked between the hours of 8 and 6.
Do I want us to return to that? No. but for the love of god, PLEASE stop the lie that federal RTO is a novelty and WFH or ridiculous AWS like 0600-1400 has been the norm since the Nixon years. Not for the professional class.