As a trans woman who started transitioning at 43... I agree 100%.
This article mostly discusses waist size, for which I'm in the lower quartile. But after 40 years of testosterone poisoning my underbust is above the median. Finding clothing that fits and is flattering is really difficult!
A few years back I discovered that the third-party licensing files we had used in the '90s would roll over in 2016. The format used four ASCII digits for the number of days in an otherwise binary file and the epoch was the founding of the licensing company, sometime in 1988. If they had just used a 32-bit integer instead it would have saved me a lot of headache!
DEC WARS is full of great computer jokes. It's a 1983 Usenet posting by Alan Hastings and Steve Tarr: https://www.bsd.org/decwars.html
> It is a period of system war. User programs, striking from a hidden directory, have won their first victory against the evil Administrative Empire. During the battle, User spies managed to steal secret source code to the Empire's ultimate program: the Are-Em Star, a privileged root program with enough power to destroy an entire file structure. Pursued by the Empire's sinister audit trail, Princess _LPA0: races aboard her shell script, custodian of the stolen listings that could save her people, and restore freedom and games to the network...
I particularly enjoyed _Everything and More: A Compact History of Infinity_ by David Foster Wallace. It gave me a new appreciation of not only the last two centuries of math, but also the english language and the abuse of sentence structure, asides, and footnotes[1][2][3] for educational and entertainment purposes.
[1] so
[2] many
[3] footnotes[a]
[a] Which, I must say, I found interesting and informative[b]
We seek an experienced software engineer to conduct safety analyses, develop
functional requirements tests, and conduct design reviews for Green Hills
Software's real time operating system and the suite of C and C++ development
tools. As a Functional Safety Software Engineer, you will be responsible for
ensuring that Green Hills Software safety-critical products are safe for our
customers to use to build vehicles, medical devices, and industrial control
systems that people's lives depend on every day.
Job Requirements:
* An understanding of compilers, assemblers, linkers and debuggers and their role in developing embedded software
* An understanding of the concepts of real time operating systems
* At least two years of programming experience in high level languages, C and C++
* Experience with UNIX and with scripting in languages such as Python and shell scripts
* Bachelor's degree in Computer Science, Computer Engineering, or equivalent experience
* Ability to learn and understand how complex software systems work
We're also hiring for Development, Consulting, and Testing positions, both in Santa Barbara and worldwide: http://www.ghs.com/jobs.html
To apply please email your resume to jobs@ghs.com.
I use salmon's predecessor (lamson) to process emails for an email-driven helpdesk system. Emails come in through lamson, are processed based on headers, and either attached to the support ticket they belong to or are routed to an admin for manual processing.
Lamson isn't a perfect fit for the system, but it did make it easy to get started. Unfortunately it also had a number of bugs I had to fix, since the project was defunct. I should check to see if salmon needs those fixes.
The primary uses for procmail tend to be running a fixed set of rules to save mail to various directories or route it as input to scripts.
My use case needs to save it to a database and make various decisions depending on the sate of the database (e.g., send notifications to anyone watching the ticket and update due dates for the support SLA). Since this database access is more efficient if the process stays connected to the database, it's better to have a long-lived process which handles mail as it comes in than to launch a new script on every incoming email.
Lamson serves as both the procmail side and the script side. It's a long-running process that routes the incoming email to the appropriate business logic internally. And since it's in Python, it's easy to integrate with our existing Django database and business logic. It's not perfect, but it works well enough that I'm not actively looking for a replacement.
procmail+spamassassin is an example of a long-lived daemon and a client that talks to it, but indeed, spamassassin had to provide both parts because procmail doesn't directly do that.
I have 20 year old code that does the same client/server thing, by having procmail leave files in a directory that the daemon is watching for new files to appear in.
I should have mentioned that I run lamson in maildir mode rather than listen on port 25. I have postfix configured to dump incoming email into a maildir, and my lamson process watches that directory.
So I guess the reason I don't use procmail (aside from it not having a release since 2001) is that postfix is sufficient :->
This article mostly discusses waist size, for which I'm in the lower quartile. But after 40 years of testosterone poisoning my underbust is above the median. Finding clothing that fits and is flattering is really difficult!
reply