joejag
* 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
There's a reason everyone isn't driving a Honda Civic.
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
Visualise when holidays overlap across countries
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.
Two Months with Powershell on a Unix
Agile in a Box
Three little questions to save your new job before it starts
The origin of soft skills
Tracking where your time went with Lego workstream visualisation
Your two blank line budget for tests
The Text Editing Kata
Anti-if: The Missing Patterns
How many eyes do you want on your code?
My favourite Zsh features
Choose One: Feature Toggles vs. Authorisation
What I'm arguing is that the community we are part of also has issues that aren't clear cut, that we could debate to generate interest and inspire the community.
There is no shortage of great political speeches.