Once the Fed funds rate gets closer to 5%, you'll see more pushback from politicians and media. What does the Fed do in this situation if it needs to keep tightening? It may choose to switch to smaller rate changes, or even go flat, and at the same time embark on Treasury sales, or at least, rebalancing along the curve. So either way, not a good time to be in bonds.
For an alternative approach, if you treat this function as a time series where x is time, you can get a reasonably good approximation by performing SVD of the trajectory matrix and building the forecast from the principal components (eigen vectors) using a recurrent formula.
We removed all tracking scripts from the front-end framework we use (vuepress) and are only checking nginx logs with geoip and org extensions enabled. This is more than enough for us as we're in the non-consumer software business with a relatively low volume of page views by human visitors. We see the org, the country, the city, and the page flow. Good enough.
Not having a nose is ok compared to having a half of the head attached from another sculpture. This was the case in imperial Rome when the sculptors had to quickly retrofit works in progress to fit the new emperor. In some periods you had three emperors succeed each other, most certainly involuntarily, within a period of three years.
Rubicon is a rather shallow river and is easy to cross by the way. But comparing menage-a-trois to a watershed event in human history deflates the risks taken by Caesar.
We use Travis CI for checks as well as github and travis webhooks to deliver warnings to specific committers who need to fix the errors in a particular PR. Scheduled Travis CI checks send alerts to the general channel if the master branch starts failing.
Our docs are on github. We enabled Travis CI checks and all commits are now automatically validated with the default and custom markdownlint rules. If the linter finds errors, the committer receives a warning to Rocket chat with a link to Travis CI status page containing errors as well as suggestions on how to fix them.
We adopted a set of formal guidelines [0] for our database docs, based on Google Developer Guide [1], and automated the checks as much as possible with linters [2].
The checks cover spelling, markdown formatting, broken links, and grammar/style. For instance, we specifically reject hostnames, domain names, IP addresses, person names, phone numbers unless it's on our Example List[3], which itself is largely based on RFCs.
> which served the website using a fake certificate
This would cause an untrusted certificate error in browsers.
> failed to obtain an SSL certificate while man-in-the-middle attacking
The sentence doesn't make sense. MITM is by definition an attack where an actor was able to impersonate the target. In this case, they presented an certificate that was not signed by a CA in the root CA file on the clients. So this can be qualified as a failed MITM attempt.