I feel similarly.
I've been pure remote since COVID.
I used to complain about having to come into the office just to stare at a screen quietly next to people.
Being remote has been great in some ways, but I've really noticed the reduction in connection to coworkers and the major decline in informal collaboration. I've also had to dedicate a room of my house as an office (have kids, so working from any common space is fully impossible).
My life just feels smaller now, when most days instead of traveling through the city on a busy train to meet up with dozens of collaborators, discuss, eat together, I start my day by sitting down in a small room by myself in front of a screen.
Work is what I do with most of my days. I'd like it to be as engaging and as socially connective as possible. I don't like commuting, but I'm planning for my next job to be in person.
This is why I like more bottom-up approaches to coding.
Code broken up sorta arbitrarily, that's compressed moreso than abstracted, is hard to follow.
But, when there's a reasonably small set of solid domain abstractions (even extremely complex ones in implementation), that's totally fine.
This is where preferences vary; some folks have committed nuances of various helper libraries to memory, and find it easier to process a `fuse_zip` combinator or whatever than a loop, but for the readers who'd need to look that up, it's an attention land-mine.
API design, abstraction design, is a type of UX design, and like other forms of design, accessibility is a concern. Keeping the vocabulary fairly small and the abstractions well-behaved and consistent help nearly everyone, but particular ADHD folk.
Work is what I do with most of my days. I'd like it to be as engaging and as socially connective as possible. I don't like commuting, but I'm planning for my next job to be in person.