Could be fun with a decently made legacy system without artificial pressure from POs, managers, etc., but hell when you inherit a mess and nobody (who matters) believes you when you say you need to first fix 12 issues before you can do something simple.
One has to weigh the probability that (1) said limits are removed and (2) when they're removed, it makes a sufficient difference in prices against being permanently priced out. A house now, or a 5 million dollar apartment for 500k (both figures inflation adjusted) in 50 years? People wouldn't be foolish for going with the former if they're not rich.
Unfortunately I've had interactions with the medical system where the doctors wrote their after meeting notes with severe errors and pieces of fiction, as well as specialists who almost ran out of the room after 5 minutes of an appointment they billed 45 minutes for to the insurance. I doubt such cases are rare and I suspect this sort of product, which I'm a priori neutral about, would change the situation much for the worse.
Loading up on bonds when rates are rock bottom instead of bills is asking for trouble. Sure, when yields are at averages or historic highs, back the truck up; otherwise, there's not much difference between yielding 0% and 1%, but a lot of difference in liquidity.
As an aside, I remember in recent times various institutions, either by law or voluntarily, loading up on long term bonds at 0% +/- 0.5% bonds. I'm sure that's going to be a fun situation should they face even a slight liquidity crisis of, say, more retirees pulling money out than there are young people depositing into pensions and whatnot.
Can you explain the difference between bills and bonds and why the difference was significant in this case? For myself and probably a lot of engineers reading this comment, it seems like inside baseball.
Bills are shorter duration, bonds are longer duration. You can look up the terms to get exact time ranges. When the yields for both are very low, there's next to no upside to holding onto the low yield for longer. The downside is that if one is in critical need of cash immediately, nobody wants the old low-yield (compared to current yields) bonds and will only buy them at a discount. For bills, due to the shorter duration, extra liquidity is built-in.
Suppose that Bing Chat itself wants to store data for the longer term, but it doesn't have the direct ability to do it, so what can it do? Once in a while, send the human some unhinged messages with a high probability of them being saved on reddit, news sites, etc. If you recall, some examples of the unhinged messages Bing sent were very strangely worded at times, very repetitive, etc. How difficult would it be to hide a message inside of an unhinged message? Now these messages will be included in future data sets for training.
Xe-HPC wasn't a risk-averse design, nor was Arc, nor was Alder Lake, nor was Sapphire Rapids. The only problem is that Xe-HPC is nowhere to be found, Arc was delivered 2 years late and buggy, and Sapphire Rapids was at least 1 year late; only Alder Lake delivered on time and without major problems. Thus, the problems came from poor execution.
Look at Intel's projected node schedule, it's very aggressive. Show me the risk aversion there. The problem is that it's difficult to achieve that schedule without problems, and taking into account Intel's history, the market doesn't believe they can do it.
Any ideas on how the "only by" would work? I'm not seeing a way around pasting generated text and signing it as one's own work. Proof of work solutions would have to have a high cost for anyone to care, otherwise there would be bots "proving" the work of writing an essay by generating it in phases like a human would edit drafts.
This is the really first time I've thought about this, so uh... No, no ideas.
One's identity would need verified concurrent with creation of a text. I am not really satisfied with the idea of a specialized word processor or input device that does biometric validation, I'd rather have a specific, standardized protocol. I wonder if this is already deemed impossible, or if someone is working on the problem.
I went with a Synology router in 2019 almost entirely due to how nice SRM was. It's still running fine. Maybe the competition had time to catch up, but I never had a reason to look.
Do you code like this as well or is this specific only to writing docs? If it's just docs, then honestly, it sounds like you just really hate working on them even though you can do a good job.
I also have problems staying focused when writing code, but it's not as present and problematic.
But that's the thing, I don't hate writing (at least technical documents, the career stuff and others are always boring). For my blog I even do it willingly (and it's less of a problem because there's no expectation there anyway).
