Multi-version approaches to developing software aren't as good at reducing common-mode failures as many people expect[1].
[1] J. C. Knight and N. G. Leveson, “An experimental evaluation of the assumption of independence in multiversion programming,” IIEEE Trans. Software Eng., vol. SE-12, no. 1, pp. 96–109, Jan. 1986, doi: 10.1109/TSE.1986.6312924.
Yes. Synology introduced the requirement to use first-party drives earlier this year and it was such an unmitigated disaster for them that they rolled it back just a couple of days ago.
One feature I wish the Arch wiki had last time I used it was conditionally hiding sections. It presented various options throughout their guides and depending on which options you chose later sections weren't relevant. I often found I'd get partway through a step only to discover it wasn't relevant.
It would be great if, when presented with different options, you could indicate which one you'd selected and have it hide the irrelevant stuff further down the page
It's a pain for even experienced users. Popping open the developer tools in the browser because you've done Ctrl-Shift-C is annoying, accidentally calling a group chat of 50 people in MS Teams for the same reason is really annoying.
Ok as much as I like keyboard shortcuts, having a shortcut for making calls is just cruel.
The ctrl-c thing isn't a big deal for me since I copy text to clipboard either using tmux (just selecting is enough) or piping the terminal screen to vim (where I've mapped it to just +)
I've been doing a bunch of receuiting recently and I make a point at the beginning of each interview to explicitly tell them that we don't do trick questions. We also don't do leetcode at all.
My approach to interviewing is that I want candidates to do the best they possibly can.
I was talking to one of the engineers at Daisy Lab[1] at a local hardware meetup a few months back. They are working on precision fermentation for dairyas described in the article. It's a really interesting technology and they seemed to be having really promising results.
I believe you've got confused between the NRO (National Reconnaissance Office) and NGO (Non-governmental Organisation). The NRO is very much part of the US government.
Apparently System-scope custom fields have a significant performance hit in Jira. I think project-scope custom fields are better.
Sometimes it feels like Jira is so incredibly configurable but is really missing the "pit of success". There is a way to make it nice to use and reasonably performant, but you really need to go into it with a strong plan. And even then it's really easy to balls it all up in short order if you're not vigilant.
There are a lot of bits and pieces that are clicking into place lately in the Python ecosystem. Recently I've been using the combination of Marimo and these uv script dependencies for building reproducible rwporting and diagnostic tooling for other teams.
Beyond whatever design or production issues caused this particular anomaly there will also be the delays due to the fact they just blew up a lot of ground support equipment.
[1] J. C. Knight and N. G. Leveson, “An experimental evaluation of the assumption of independence in multiversion programming,” IIEEE Trans. Software Eng., vol. SE-12, no. 1, pp. 96–109, Jan. 1986, doi: 10.1109/TSE.1986.6312924.