I was 6 or so when the vaccine was first offered in the 1960s in elementary school. For some unknown reason, I skipped the chance, much to my parents displeasure. No idea why they didn't take me to the pediatrician to get vaccinated later.
In the 1970s, I caught the measles while I was in Army basic training. I spent 3 weeks in the base hospital. Not fun.
Don't be stupid. Make sure your kids get vaccinated.
The origins of Agile are reasonable enough, a relatively terse set of observations for things that frustrated a group of people.
The problem with Agile is that while the originators created something useful, they then quit doing actual work in favor of writing books and evangelizing about Agile. In order to sell the next edition, they had to add something to the methodology, but never actually had to use the new additions themselves in real projects. The result is a set of practices where you can pick any two or so and they are quite helpful. But adding the 3rd or 4th has zero marginal utility and by the time you toss in the 5th and 6th practice so you are doing Agile "right," the marginal usefulness of the additional practices is negative.
The equilibrium price of a finite resource (like fossil fuels or fissile materials) is determined purely by supply and demand...
You forgot the rate of interest. The price of a finite resource changes over time as supply is used up. The percentage change in the price will change at an amount just equal to rate of interest. The owner of a barrel of oil can sell it today for P1 or wait until tomorrow and sell it for P2. If the percentage change from P1 to P2 is greater than the interest rate, it is in the owner's interest to hold. If less than the rate of interest, he is better off selling today and earning the interest. The result is that over time, the percentage price change should equal the rate of interest. See Hotelling's Rule.
Columbus Dispatch:One month into a ransomware attack against Columbus that the city has now acknowledged may have compromised the personal information of close to half a million private citizens and thousands more city employees, the public still knows precious little about what happened.
Prosecutor's database exposedMayor Andrew Ginther confirmed on Saturday that information in the city prosecutor's database was exposed during the July cybersecurity data breach.
Private citizen lawsuit."(The breach) affects a huge amount of people," said Meador. "Anyone who scanned their ID to get into city hall, crime victims, so the sky is the limit."
Employee lawsuitA group of anonymous Columbus police officers and one firefighter have filed the second lawsuit against the city claiming their personal information was stolen and some suffered financial losses from bank accounts and credit cards hacked after the city was the victim of a ransomware attack.
Unfortunately, Ginther was recently re-elected Mayor. We did try and oust him over his proclivity for giving away tax abatements that have cost the city school system millions in lost revenue, but we lost by a 2:1 margin.
What really should happen:
5. Convert the company to a mutual insurance company owned by their policyholders and make the old management pay the fines out of their personal pockets.
I'm in a similar boat. I have 2 vid cards, one connected to the office monitors, one to the TV. I run one copy of xdm with 2 copies of X. The Xs are defined by the seats in
Xdm and X do run as root, but I wonder if I could create an xdm user and give that user ownership of the vid and snd devices using udev when the system is booted and then the Give/TakeConsole files could give the user ownership of the devices and return it to xdm when the user logs out.
Legit greybeard here.
People hunted me down to help scale up AI networks. I was ready to retire.
Same. I'd retire, too, but I keep getting offers to solve interesting problems. My father used to claim that "it isn't who you know that counts. It isn't what you know that counts. It is who you know who knows what you know that counts." That has paid off in both dollars and interesting problems throughout my career.
At the time, there was literally no way anyone could hope to model fusion on a computer, and very little understanding of what they were doing in general beyond a basic particle physics standpoint.
That, in a nutshell, describes my father's career. He went from programming an IBM 704 in the 50s/60s simulating particles zipping around an accelerator at UW to simulating fusion machines at ORNL in the 60s/70s/80s.
System going down at 5 this afternoon to install scheduler bug.
