I'm not in the PA that will be sharing desks but sit in one of the affected offices. I can see about 100 desks from where I am right now. All of them are assigned to someone, but only 6 presently have someone sitting there. Occupancy of our corner peaks at maybe 30%?
Something was bound to happen given all the unused real estate. But it's shitty that those of us who actually use our desks, because we rather like work-home separation, now might end up with a desk time share. Maybe all those people who didn't actually want to come to the office should have just filed for permanent remote?
That meaning of dropped generally only applies in intransitive contexts. Here we have a thing dropping a thing, suggesting the older meaning of "dropped".
Agreed. I work in the PP's PA and was promoted on my first try for doing unsexy but worthwhile maintenance work on an important tool. It can happen. In my estimation the best thing to do if you want to get promoted is 0) have a positive relationship with your manager 1) read the SWE ladder for the next level 2) give your manager a document that describes your work using the language of the ladder as closely as possible. Said ladder does not say you need to deliver a shiny new thing, despite what is commonly assumed in this forum.
I basically still log in for interest group posts (e.g., photos from my son's preschool) and to RSVP for party invites. I'd love to see alternatives take over for these.
My 3 year old has ASD. I'm interested the finding about disproportionate megalencephaly, as his head is pretty big (but he's also rather tall). Suppose I wanted to see if he falls into the >1.5 SD cerebral volume/height bucket. Is there a way to meaningfully approximate it with his head circumference and height?
There's been a big investment in server platforms that strive to enable SWEs to build a new service that follows Best Practices with as little knowledge and handholding as possible. These consist of conformance tests that yell at you while you're coding if you are trying something generally thought to be bad, and semi-automated workflows that help you bring your code to production. When everything works as intended, the production workflows set up a decent set of alerts, acquire resources, configure CI/CD pipelines, and launch your jobs with just a few button presses on your part. (In practice, one of the steps will probably require debugging, but eh, it seems way better than the broccoli man video.)