Joined 16 years ago
However, it's extremely common in forecasting to revise the forecast once actuals come in. In the case of the BLS, it's the documented approach for a very long time.
Every month the numbers are adjusted and annually. All of the notes as to why, the method, etc are in the actual reports*.
*I don't recommend reading them or the footnotes unless you have insomnia. :)
** Also, if the source data is inaccurate, corrupted, etc; if the models are non-transparently adjusted, that would be horrible and cause for alarm. At the moment, we don't know if that is the case. Yet.
The BLS (USA) does adjust the numbers every month (for two months after the initial release) and annually. Regardless if the numbers go up or down, this is fairly common with statistics and forecasting in general. When actuals come in, the forecast is adjusted closer to reality.
Anecdotally: It gets lost in the mix of headlines when those adjustments show that the initial projections were on trend, or "close enough the talking heads don't care enough". However, it gets "interesting" when it's off-trend; or confirms prior notable good/bad news. In this case, it confirms* what was suspected, mostly confirms what was reported. As actuals came in, the reality was worse than projected.
*"Confirms" use case here: job growth is poop right now.
Regardless if the numbers go up or down, regardless of the administration.
So, yes...the last administration did the same thing, and the administration before that, etc.
* All of those classes also had lab time (some dedicated, similar to a chemistry class), info on how to get the IDE if you had $ access to a computer at home, and alternatives as well.
Personally, I see more value in pseudo code (written or typed) and sketch type diagrams (analog or digital) than handwriting code. However, it was WILD and amazing to watch the gray-hairs of those days debug your code on paper!
(Old Pentium Pro, PII, multi chip desktop days) -- When I did a different type of work, I would be in love with these new chips. I just don't throw as much at my computer anymore outside of things being RAM heavy.
The M1 (with 16 GB ram) is really an amazing chip. I'm with you, outside of a repair/replacement? I'm happy to wait for 120hz refresh, faster wifi, and longer battery life.
That person has assessed their risk level and determined that their community's disregard for their personal risk, negatively impacts their personal model. Therefore they have to use a different device to mitigate their risk.
Seems pretty logical, matches with known science, with a minor exception that the half face respirator may not offer greater protection vs a well fitting* N95/KN95
* well-fitting being the crucial note there.
Loose definition (with errors and assumptions, but helps some without getting into actual probability math):
If it says "30%" - many of us have heard "30% chance of showers". It is NOT "30% chance of showers"; it actually is "100% percent chance of rain, over 30% of the area, within a given time, of a particular amount of rain."
Which is STILL (to me), difficult for the average person to comprehend.
Copying and pasting from Weather.com (linked PDF - https://www.weather.gov/media/pah/WeatherEducation/pop.pdf)
PRECIPITATION PROBABILITY The probability of precipitation forecast is one of the most least understood elements of the weather forecast. The probability of precipitation has the following features: ..... The likelihood of occurrence of precipitation is stated as a percentage ..... A measurable amount is defined as 0.01" (one hundredth of an inch) or more (usually produces enough runoff for puddles to form) ..... The measurement is of liquid precipitation or the water equivalent of frozen precipitation ..... The probability is for a specified time period (i.e., today, this afternoon, tonight, Thursday) ..... The probability forecast is for any given point in the forecast area To summarize, the probability of precipitation is simply a statistical probability of 0.01" inch of more of precipitation at a given area in the given forecast area in the time period specified. Using a 40% probability of rain as an example, it does not mean (1) that 40% of the area will be covered by precipitation at given time in the given forecast area or (2) that you will be seeing precipitation 40% of the time in the given forecast area for the given forecast time period. Let's look at an example of what the probability does mean. If a forecast for a given county says that there is a 40% chance of rain this afternoon, then there is a 40% chance of rain at any point in the county from noon to 6 p.m. local time. This point probability of precipitation is predetermined and arrived at by the forecaster by multiplying two factors: Forecaster certainty that precipitation will form or move into the area X Areal coverage of precipitation that is expected (and then moving the decimal point two places to the left) Using this, here are two examples giving the same statistical result: (1) If the forecaster was 80% certain that rain would develop but only expected to cover 50% of the forecast area, then the forecast would read "a 40% chance of rain" for any given location. (2) If the forecaster expected a widespread area of precipitation with 100% coverage to approach, but he/she was only 40% certain that it would reach the forecast area, this would, as well, result in a "40% chance of rain" at any given location in the forecast area.
Removing the MX products completely solved the problems with every other Bluetooth device I have.
In the beginning, I only had the MX (Mac Specific) mouse, and the problem did not happen very often. On occasion, but not too bad. After one of the OS updates, it was a non-stop issue. Disabling the auto switching (between Apple devices) helped a little.
Later, I also bought the MX Keys (Mac Specific) keyboard. I started having issues with a non-Apple headset on/off out of the blue. I could never use my AirPods with my laptop for anything other than listening to music. I tried everything from killing Bluetooth pref, to resetting my AirPods.
What finally solved it? I deleted all Logitech Devices from my laptop. Reset all Bluetooth settings. Re-paired my AirPods. I have not had a single problem in audio quality for 3 months now.
My Logitech devices are just sitting off to the side collecting dust now.
I just thought a little rough organizing might be nice.
I have family that has issues with grip and/or circulation --which causes other issues with capacitive touch. I found a stylus (and a nice collection of inexpensive ones too) goes a LONG way towards helping. In my non-medical opinion, I believe decades of muscle memory holding a pen/pencil helps the elderly navigate. Their hand also doesn't get in the way of their view either.
Voice control is a really amazing addition, but it may be overwhelming to recall some or most of the controls. So I would start small. I found a lot of success working with older adults and tech while just starting with small wins.
Also mind conditioning: start your day asking what the weather is like. That helps get them to feel less "funny" when using it. It becomes more casual and less embarrassing.
In the 80s, it was just a daily life comic, Parents with young kids, more from the parents perspective. As their kids [comic] grew older, so did I and my siblings [real world]. The comic progressed to show when their kids had kids [comic ]--in the 90s. My parents were also grandparents at the time, and they would smile and giggle as they shared the Sunday comics.
Being old enough to witness those moments were really touching to me. Made me have an even deeper appreciation for a story that evolved, but also watching my parents grow and change --not just "grow older".
Personally, I found the the more I looked at concept of most/all things being finite, the more appreciation for those things, people, moments, food, jobs, projects, etc I have. I haven't become a mindful monk by any stretch, but it has both shaped and improved my outlook in many ways.
