How well do you usually score? I tried getting an A+ (all the way up from an F), but I can't get past the CSP warning. Maybe I'm going about it the wrong way.
The site also works on qutebrowser (QtWebEngine) in Linux, as well as on the other usual suspects.
It's so smooth, the lack of lag when you're scrolling is just perfect. The hardware helps, of course, but I have the same smooth scrolling on very dated hardware to which I installed Chrome OS, too.
I would settle for Chrome OS-like touchpad smoothness and gestures in Linux. The out-of-the-box touchpad sensitivity and scroll smoothness in Chromebooks with outdated hardware and something as low-end and old as an a Celeron N2840 is incomparable to anything I've ever managed to configure in Linux, multifinger gestures included.
Thank you for the incredibly insightful reply! There are a few things in particular that stood out. I have worked mostly remotely during a period of my career, and I know just how important it is to maintain discipline and clear, constant communication.
I feel we'd be quick to identify low-performers, because it can get demanding quickly here. I'm a pretty hands-on manager for the time being, though always trying to foster autonomy as much as possible, but I know what the team is doing at all times -- we keep track of it with the help of allocation maps, and regular syncs with the dev teams that would leave little space for someone to... space out. The team keeps itself accountable, too: they wouldn't let anyone underperform for long, without trying to address it -- and mostly, in a very positive way.
The one-off calls with Engineering you mentioned, that's something I'd really like to highlight: it's been a mixed bag for us. As practice, I usually reinforced the need to collect all information needed in one batch and only then addressing the teams to get the answers needed. Sometimes, it just works, but there's always something missing. Following-up isn't always easy, and not everyone takes it lightly. That's when it's just easier to go and get 'em, in a 5 minute catch-up for clarification. Technical writers, per nature, are shy people, as are devs. Face-to-face interaction doesn't come naturally, but it's been known to work.
The problem is when other teams just choose not to reply. That's usually when I'm CC'ed, but there's good will established, those issues have been mostly overcomed.
As for the working hours: I am, and the company as a whole, is very flexible. I don't care what time they get in and what time they get out; I don't care if they're at home, as long as they're approachable when needed. I only care about them getting the job done. If they wanna go the same way that fella who outsourced all his work to China or something and then just validated their work? I'd promote them.
In its entirety, your answer was great. Thank you! I'll be keeping this all in mind, even share with the team right now. (Maybe not the part about shady promotions and all)
The site also works on qutebrowser (QtWebEngine) in Linux, as well as on the other usual suspects.