joejag

Author here. My writing process is:

* Write: Use FluidVoice to get all the text down in my own voice

* Edit: Ask ChatGPT etc to criticise the article

* Cleanup: Grammarly

* Publish: Good old GitHub Pages

I'm a 40+ year old man who buys cosmetics for CS2 (which has a resale market). If you are going to spend 200+ hours doing something you might as well have a nice environment to do it in.

There's a reason everyone isn't driving a Honda Civic.

I followed this advice and my shell went from 1530ms to 35ms startup time.

Main culprits were language switchers (nvm, jabba, pyenv). Which I moved to lazy loading.

If I drop the ohmyzsh plugins startup time is 11ms. But, I want some quality of life.

There's a nice benchmarking command in the article if you want to test yours:

for i in $(seq 1 10); do /usr/bin/time $SHELL -i -c exit; done

yeah, by about 3.131 trillion USD

Hmm. It show's as on the Friday for me. I suspect browser timezones are messing things up. I thought I'd made everything UTC, but more testing will be required. Thanks for reporting.

While planning an offsite, I needed to find a suitable week that worked for local holidays across four countries. That was harder than I expected, so this site will be easier for you if you want to see public holidays at a glance for any country in the world.

I had the joy of helping with a Teams to replace Slack rollout at the start of the Pandemic. During which I had multiple meetings with Engineers and Product folks at MS. Two reasons struck out as significant problems.

The first was that Teams is Skype and Sharepoint mashed together with duct tape. When you'd ask for improved UX, it would all fall to "Ah yes, the Sharepoint team would have to do X so the other team can do Y. They aren't built like that, though, so you cannot have it". Teams is not one product and will never feel that way.

The second was scarier. I was trying to encourage communities of practice and having open communication by default, with some private rooms when needed. Like in Slack, you have multiple channels rather than disappearing into your own Team. Promoting openness was anathema to their Product people "Why would you want people to see what you say? Privacy is the default". I got the impression MS internally is not a safe space to speak, and Teams has that same cultural baggage.