The component model is a very powerful technique for keeping large amounts of complex code maintainable. I worked in large amounts of tricky jQuery before the component model and I would never wish to go back.
JSX works well for a component approach because you’re expressing the component in a fully functional programming language. Doing a lot of that work tends to make the developer quite capable in Javascript.
Ability to communicate trumps actual competency every time in a typical career.
People who are senior to you got there because they have a superior ability to communicate, not because they have any competence. This will range from people who are so communicatively capable they can silvertongue their responses to utterly conceal incompetence/laziness to their own management to people who have slight competence but better communication and so get promoted over the most knowledgeable/experienced/capable in their domain.
Twenty years ago I thought these type of people were an aberration. I’ve come to realise that in fact, they are the majority in any business/corporate hierarchy.
I just wish that Teams would load in a reasonable time on Firefox. It's a corporate enforced need and it takes minutes to load the web Teams version in Firefox. Microsoft seem not to treat Firefox as a legitimate web client.
One of the challenges of being a piano player - youtube search for a new piece you're interested in and there will be a video of a 4-5 year old playing it on a baby grand somewhere :-)
Absolutely. When I do front-end work, I screenshot every visual change in the PR. Boss wants a look at the current work -> screenshot Users want to see a difference -> screenshot.
But the most valuable it that it builds up a visual history of changes in my Screenshots dir.
This is my favorite use case as well. There's nothing better than starting a pull request review on someone else's front-end work and seeing the changes they've made before looking at the code.
In the appendix links at the bottom, there's a comment that a large percentage of houses in Japan are still built with post & beam. I've been prompted with a slew of recent "Japanese carpentry videos" that seem to sync with this.
I'm curious why it's still prevalent in Japan? Most new Japanese houses are not built in the old machiya style.
Interviewed at a company recently, who were very keen to take on a senior dev, as they had a lot of 'juniors'. Their interview process boiled down to 'we want you to take hackerrank'. At which point I basically decided they weren't somewhere I wanted to work.
Looks like it needs Jack rather than Pipewire