Why did I write it down? In order to remember, of course, but exactly what was it I wanted to remember? How much of it actually happened? Did any of it? Why do I keep a notebook at all? The impulse to write things down is a peculiarly compulsive one, inexplicable to those who do not share it, useful only accidentally, only secondarily, in the way that any compulsion tries to justify itself.—Joan Didion, “On Keeping a Notebook”

I think we are well advised to keep on nodding terms with the people we used to be, whether we find them attractive company or not.—Joan Didion, “On Keeping a Notebook”

Many people here say they're rich in things that aren't included in any official measure of poverty. Things like family and faith. So they're understandably a bit bitter about how they're often seen from the outside.

Keep a clear record of how you obtained consent from your current subscribers When, how, and why (what for) you obtained their data – timestamp, wording, source.

Louis Menand summarized the mid-centurysituation and Macdonald’s thinking as follows: “There was a majormiddle-class culture of earnest aspiration in the 1950s, the productof a strange alliance of the democratic (culture for everyone) and theelitist (culture can make you better than other people).

The hallowed American dream is thegold standard by which politicians and voters alike are meant to measurequality of life as each generation pursues its own definition of happinessunfettered by the restraints of birth (who your parents are) or station (theposition you start out from in the class system).

Making a property writable adds an order of magnitude in complexity. In the real world it's definitely not realistic for every class to be immutable, but if most of your classes are, it's remarkably easier to write bug-free code. I had that revelation once and I hope to help others have it.

In addition, data model policy requires that RAs maintain a record of the date of allocation of a DOI name, and the identity of the registrant on whose behalf the DOI name was allocated.

record-keeping of animal behaviour in systematic units of time and incorporating at least one verb.

Record keeping using small clay ‘tokens’ was present in the Near Eastern Neolithic in the tenth millennium bc, these objects widespread and abundant by the sixth millennium bc, and by the fourth millennium bc it is clear they were functioning, perhaps as generalized elements for simple counting tasks recording time, resources and the like, albeit among other functions that did not have a mnemonic function (Bennison-Chapman Reference Bennison-Chapman2018, 240).

The sudden awareness of something that calls for an explanation, once the fog of habit has lifted, seems to be the real stuff revolutions’ sparkles are made of

My day to day notebook is a soft 5 inch by 3.5 inch pocket notebook as shown below. I use a mechanical pencil when out and about (no breakage or sharpening) and take a small eraser (in this case an eraser shaped like Lego). This book is good for notes and ideas. Notice I cross them out when I have acted on them in some way (done the work, or given up on the idea). The goal of the daily notebook is to eventually throw it away (not save it). So all work needs to move out and I need to be able to know it has been moved.

It turns out that a much more accurate picture is that povertyspells tend to be short but frequent.

One reason for this is that poverty is not something that people wish to ac-knowledge or draw attention to. Rather, it is something that individuals andfamilies would like to go away. As a result, many Americans attempt to concealtheir economic difficulties as much as possible.22 This often involves keeping upappearances and trying to maintain a “normal” lifestyle. Such poverty downthe block may at first appear invisible. Nevertheless, the reach of poverty iswidespread, touching nearly all communities across America.

It’s as if we need the gravitational pull of both worlds to keep us on track, locked on a good and righteous path. Without both worlds pulling on us, we would crash into one, or simply lose our way, hurtling through the universe on our own, intersecting nothing, helping no one.

When I was around eight years old, having recently made the trip with my family back ‘home’ to London from where I was born and lived my earliest years in Nairobi, Kenya, I contracted measles, the first of many childhood illnesses that confined me to bed and disrupted my schooling. My father sat by my bedside and read stories to me about the planets and outer space, infecting me with his love of scientific exploration. I was given books to read about natural history and I learned to identify the garden birds in the tree that grew outside my bedroom window. I made watercolour paintings of these and others that I had never seen from illustrations on the pages of ‘Collins Pocket Guide to British Birds’. Then, whenever I was well enough, I was taken out into the countryside and spent many happy days bird-spotting for myself. I was taken on my first ‘fungus foray’ to a place called Burnham Beeches, west of London. It was led by the redoubtable figure of a man called Bayard Hora and I was awestruck by what I many years later described as ‘The Fountains of the Forest’ as they erupted from ground and trees in manifold shapes and colours, not least the legendary ‘fly agaric’ (Amanita muscaria), the ‘parasol’ (Macrolepiota procera) and numerous ‘brittle gills’ (Russula spp). I found that their Latin names came easily to me and I delighted in showing off my recall to peers and teachers.

'm open to considering adding this to core but it's such a rare need (given that you're the first to ever ask for it, and I've never wanted or needed an around(:all) hook) I have a preference for keeping it in external gem if we can do so w/o hooking into rspec's internals

Webpacker used to configure Webpack indirectly, which lead to a complicated secondary configuration process. This was done in order to provide default configurations for the most popular frameworks, but ended up creating more complexity than it cured. So now Webpacker delegates all configuration directly to Webpack's default configuration setup.

I keep detailed records of my installation and configuration process so that I can quickly find out where something went wrong.

‘Don’t get fooled by those mangled teeth she sports on camera!’ says the ABC News host introducing the woman who plays Pennsatucky. ‘Taryn Manning is one beautiful and talented actress.’ This suggestion that bad teeth and talent, in particular, are mutually exclusive betrays our broad, unexamined bigotry toward those long known, tellingly, as ‘white trash.’ It’s become less acceptable in recent decades to make racist or sexist statements, but blatant classism generally goes unchecked. See the hugely successful blog People of Walmart that, through submitted photographs, viciously ridicules people who look like contemporary US poverty: the elastic waistbands and jutting stomachs of diabetic obesity, the wheelchairs and oxygen tanks of gout and emphysema. Upper-class supremacy is nothing new. A hundred years ago, the US Eugenics Records Office not only targeted racial minorities but ‘sought to demonstrate scientifically that large numbers of rural poor whites were genetic defectives,’ as the sociologist Matt Wray explains in his book Not Quite White: White Trash and the Boundaries of Whiteness (2006). The historian and civil rights activist W E B du Bois, an African American, wrote in his autobiography Dusk of Dawn (1940) that, growing up in Massachusetts in the 1870s, ‘the racial angle was more clearly defined against the Irish than against me. It was a matter of income and ancestry more than colour.’ Martin Luther King, Jr made similar observations and was organising a poor-people’s march on Washington at the time of his murder in 1968.

I noticed all my friends getting jobs and having new shoes and this and that. And I would ask him like, "What are you doing?" And he was like, "I just got a job. I got a car. I got this."Mike: I could see them--that they were advancing in life, and I was still in the same spot. So I asked my mom if I could get a job, and that's when she broke it down to me that I wasn't even from here. And that was right there like a slap in the face.

Luisa: J___, who was a friend of mine, was undocumented and she said, "I am undocumented. I am a Mexican citizen. I am not an American." She was put into a little room and she was not allowed to go in. She was just caged in there and that was very … that marked me like, no, I can't tell anyone. I'm seeing what's happening to these people. I can't tell anyone, so nobody ever knew.

Luisa: Her mother, I remember one time she's driving me home, and she asks extremely aggressively if I am illegal or not. And I remember being scared like a deer in the headlights. “No, I'm not. I'm not.” I was so scared of this mostly because one of my uncles saw somebody—an ex-girlfriend, I think it was, pretty much accused him of being illegal. He was deported and we had this huge thing in our heads that if somebody knew we were illegal, we were going to be deported and ripped away from everything that we knew. So I was not allowed to tell anyone.Luisa: To this day, none of my friends know that I had no papers. None of them. That's saying a lot because [Chuckles]—

Was there any domestic abuse in your family?Luisa: With my parents? My mother, yes. She doesn't like to talk about it. The older I get, the more she opens up, but it's not something that she likes to talk about. It was never in front of us, it was behind closed doors. I thank my father. He's a piece of shit, but I thank him for at least having the thought of not wanting to traumatize us. So yes, it was behind closed doors, but the more I get out of my mom, it was a lot of emotional abuse as well, a lot. I think there was some physical abuse. My mom's never touched upon it, but that's what happened.

I feel the pain. It is a normal thing that standards do evolve over time, though, and our software needs to cope with it.

We still do not understand how information practices from the worlds of learning, finance, industry, and administration cross-pollinated. From the fourteenth century onward, accountants developed complex instructions for note-taking to describe holdings and transactions, as well for the recording of numbers and calculations. By the seventeenth century, merchants, and indeed ship captains, engineers, and state administrators, were known to travel with trunks of memoranda, massive inventories, scrap books, and various ledgers and log books that mixed descriptive notes and numbers. By the eighteenth century, tables and printed forms cut down on the need for notes and required less description and more systematic numerical notes. Notaries also were master information handlers, creating archives for their legal and financial documents and cross-referencing catalogue systems.

There used to be other backends in addition to C: Java, CSharp, and Javascript but those suffered from bitrot and have been removed.

Personally, I'm starting to think that the feature where it automatically adds xray.js to the document is more trouble than it's worth. I propose that we remove that automatic feature and just make it part of the install instructions that you need to add this line to your template/layout: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %>

Now that I've thought more about it, I honestly think the auto-adding the script feature is overrated, over-complicated, and error-prone (#98, #100), and I propose we just remove it (#110).

now that I've thought more about it, I think the auto-adding the script feature is overrated, over-complicated, and error-prone (#100), and ought to just be removed (#110).

now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script

I personally think that starting from google's components makes easier to keeping update to material specs updates.

I thought about this while re-reviewing it and think it's probably not a good fit for the Yarn core because the use case is mainly for CI's. I believe that a simple shell script should fix most people's problems.

If you are working in a large enterprise application, we have to create small components. Small components are much more flexible in terms of reusability and maintainability.

This is Sass based, and therefore doesn't require Svelte components

Doing a HOC properly, as a library should, with hoisted statics and displayName and ref, etc., is a hassle and would add unnecessary bulk.

And I'm all for not adding a gazillion flags to to an elegant library.

In your environment you may want to always configure internationalization, routers, user data etc. If you have many different React roots it can be a pain to set up configuration nodes all over the place. By creating your own wrapper you can unify that configuration into one place.

Because consent under the GDPR is such an important issue, it’s mandatory that you keep clear records and that you’re able to demonstrate that the user has given consent; should problems arise, the burden of proof lies with the data controller, so keeping accurate records is vital.

The records should include: who provided the consent;when and how consent was acquired from the individual user;the consent collection form they were presented with at the time of the collection;which conditions and legal documents were applicable at the time that the consent was acquired.

Non-compliant Record Keeping Compliant Record Keeping

Consent receipt mechanisms can be especially helpful in automatically generating such records.

With that guidance in mind, and from a practical standpoint, consider keeping records of the following: The name or other identifier of the data subject that consented; The dated document, a timestamp, or note of when an oral consent was made; The version of the consent request and privacy policy existing at the time of the consent; and, The document or data capture form by which the data subject submitted his or her data.

CR 1.0 is an essential specification for meeting the proof of consent requirements of GDPR to enable international transfer of personal information in a number of applications.

Full and extensive records of processing are expressly required in cases where your data processing activities are not occasional, where they could result in a risk to the rights and freedoms of others, where they involve the handling of “special categories of data” or where your organization has more than 250 employees — this effectively covers almost all data controllers and processors.

If you have fewer than 250 employees, you only need to document processing activities that: are not occasional; or

Most organisations are required to maintain a record of their processing activities, covering areas such as processing purposes, data sharing and retention; we call this documentation.

Under EU law (specifically the GDPR) you must keep and maintain “full and extensive” up-to-date records of your business processing activities, both internal and external, where the processing is carried out on personal data.

has shone a spotlight on the risks that flow from platforms that operate by systematically keeping their users in the dark.

Ninety-five per cent. of all our volume of business is being done with what we call exchange of bank deposits—that is simply book-keeping entries in banks against which people write cheques?