![](/static/66c60d9f/assets/icons/icon-96x96.png)
![](https://fry.gs/pictrs/image/c6832070-8625-4688-b9e5-5d519541e092.png)
Not allowed to call them “females” any more.
Not allowed to call them “females” any more.
Since version 3, TeX has used an idiosyncratic version numbering system, where updates have been indicated by adding an extra digit at the end of the decimal, so that the version number asymptotically approaches π. This is a reflection of the fact that TeX is now very stable, and only minor updates are anticipated. The current version of TeX is 3.141592653
Oh just fuck off.
Because they’re not Google.
Essentially John Oliver’s episode on Boeing.
Has Russia run out of radioactive material?
This has been my experience of agile in multiple workplaces.
If anything goes wrong with the deploy script, such as failing tests, no harm will be done because the script exits upon the first error encountered.
How do you clean up? Once the deploy script is fixed, how do you know what’s been done and what needs redoing?
Have you considered ansible/puppet/chef/salt — environments dedicated to deployment and cleanup, with idempotency to allow for fixing and repeating the deployment, across multiple operating systems and versions?
I saw that too and thought “here we go again”, but in this case it seems SCO stands for Source Code Origin.
“For the public, it’s going to be a really special experience.”
That’s one way of looking at it …
I like the first explanation better.
The One With the Porn Star