The stripey wood-and-black-rubber 'sound dampening' panels are all the rage these days and I don't really understand it.
Our management had the bright idea to put these things in all our meeting rooms on the wall with the TVs we use for remote calls. People started getting sea sick looking at them. Of course removing them would mean the management made a mistake, so they will stay there until the next bright idea hits.
Right up until one tries to set up a self-hosted server (spoiler - you can't, at least not without 'significant effort' - they themselves say that if you ask about it).
Eaton and APC at least have models with LFP chemistry, with comparable prices across power ratings. The LFP will be more expensive though due to the increased longevity, at least until lead-acid ones stops being produced.
The biggest issue with these diy builds is that they need the mechanics to be inside the lens - which is not necessarily a bad thing, however it severely limits the lens choice for the system, and introduces additional cost (you basically need to buy a shutter with every lens). The scene has definitely improved over the years, there are a number of very interesting x-pan-like builds which have been made possible by advancements in 3d printing.
I'm looking forward to the day someone figures out how to modify a full frame shutter assembly (plenty and cheap on ebay) to work with medium format film.
Is this really what they use to train commanding officers? It has all the hallmarks of a self-help book - vague advice coupled with some anecdotes - with a lot of bureaucratic fluff inbetween. How/why did the squad leader 'instinctively know' how to handle the reluctant machine gunner? Isn't that the opposite of training military personnel?
I think many in this thread are underestimating the desire of VPs and CTOs to just offload the risk somewhere else. Quite a lot of companies handling sensitive data are already using various services in the cloud and it hasn't been a problem before - even in Europe with its GDPR laws. Just sign an NDA or whatever with OpenAI/Google/etc. and if any data gets leaked they are on the hook.
I've seen plenty of bugs due to misuse of unsigned types, mostly coming from beginners that are trying to fix type conversion during comparison compiler warnings. Then they go on and do some arithmetic with the loop index, which results in an underflow or two. We now have hard rules against unsigned usage if it is part of an arithmetic operation.
Where things get a bit more tricky is when working with data that has some native unsigned type - e.g. when reading an image from file, it will mostly consist of unsigned chars. There you also need conversion rules and everyone aligned on algorithms, APIs etc.
Mostly though it's a matter of maintainability - it's easier to wrap your head around signed integers (no pun intended), even for beginners.
I often use this quote by George Monbiot in my course as a caveat for my hard-working students: "If wealth was the inevitable result of hard work and enterprise, every woman in Africa would be a millionaire."
Our management had the bright idea to put these things in all our meeting rooms on the wall with the TVs we use for remote calls. People started getting sea sick looking at them. Of course removing them would mean the management made a mistake, so they will stay there until the next bright idea hits.