The summary says "detergent residue from professional dishwashers demonstrated the remnant of a significant amount of cytotoxic and epithelial barrier–damaging rinse aid remaining on washed and ready-to-use dishware", which might address the question about concentrations in regular use.
I interpreted it as "leftovers of a significant amount" not a "significant amount of leftovers", meaning that it was used in high quantities, but only remnants (in non significant amounts) were found.
You shouldn't assume remnant means "non significant", just "fewer"/"less than" what you started with. If only 5% of the substance remains (aka, the remnants) is still enough to cause problems, those are remnants by definition, but could still be significant amounts in terms of their (chance of) effects/impact.
Side note, those numbers are entirely arbitrary to illustrate the point, not meant to be indicative in anyway of how much is actually left in the processes above.
> To produce the protein needed for insulin, we need to grow microorganisms with a bioreactor and purify the protein from the culture with a protein purification system (FPLC). Proprietary examples of this equipment come at a very high initial cost and with high ongoing costs of support from the manufacturers. Our goal is to develop easy to manage, easy to repair, and affordable equipment to sustain local and community-built insulin production.
> Our FPLC design is in the early stages, and we are steadily developing mechanical and electrical designs to detect UV-C absorbance and manage the concentration of two buffers via peristaltic pumps and a mixing chamber. We plan to use Arduino microcontrollers as well as the Raspberry Pi, and the finished device will make use of the open-source Ender 3 3D Printer to facilitate automated fraction collection with G-CODE input. The bioreactor design makes use of quite a few commercial off-the-shelf parts and is ready for prototyping.
Kathi Fisler gave a great talk at the latest racketcon about research done based on the HtDP curriculum. I thought it was interesting to see the sorts of problems that fit well with the basic structure templates given in htdp and the kinds of problems that were a bad fit.
He makes mention of 2,300 Datomic databases. Can anyone shed some light on how a company maintains (or requires?)... 2,300 databases? What business needs lead to something like this? What kind of reporting pipeline possibly could pull so many dbs with cross concerns together under one roof?
Let’s say the company has four databases and 500 technical employees. That could get you to 2k personal development instances. Take your non-development instances and multiple for failover, blue-green deployments, multiple data centers. It doesn’t necessarily sound nice but it’s conceivable.
I've been working with Clojure for a few years now, and the thing I love most about the language is how it nudges developers to write straightforward code. It's maybe closer to a well-structured procedural style than to highly indirect OO or to deeply polymorphic category-theory-inspired typed functional programming. The emphasis on mostly-first-order pure functions composed of other functions, receiving and returning immutable values, makes it easy to untangle even the worst balls of mud, while the well designed set of data-structures (few) and functions operating on them (many) allow for easy and terse expression of everyday data manipulation chores.
If we keep the majority of the code pure and straightforward, we can deal with state and I/O with other constructs, like atoms and records, only where we need to (doing this systematically tends to lead me to some variation of the functional-core/imperative-shell pattern).
STM, multimethods, macros and whatnot are cool and have their uses, but after a while I think the really cool thing is how little do we need to resort to fancy stuff and how much is accomplished with just functions and data.
Lol I’ve been learning Clojure for fun these last few days and I had to read this twice because the first time I thought I was looking at a function from a module.
> we can deal with state and I/O with other constructs, like atoms and records
Can you elaborate on what you mean here or link to specific articles? I’m talking about the representing I/O side effects as records part.
There is a component framework that builds dependency tree for stateful modules and does implicit injection of params. It is a beautified pattern(usually you can do initializations in higher levels, but you have to resolve dependiences yourself and for the whole tree) for dealing with things that require state while keeping explicit references(so that you understand where it came from and can inspect(visually) its lifecycle).
