This works nicely wherever we show authors, but after we deploy to production, the folks from other parts of the world won’t get notified anymore about their songs. Mistakes like these are easy to make when using concerns.

For user-contributed data that's freeform and unstructured, use jsonb. It should perform as well as hstore, but it's more flexible and easier to work with.

it is impossible to build a new web browser

It's great to enhance the Internet Archive, but you can bet I'm keeping my local copy too.

But the distressing domestic emergency which now confronted me, was most marvellously and beautifully provided for in the Correspondence of Miss Jane Ann Stamper–Letter one thousand and one, on “Peace in Families.” I rose in my modest corner, and I opened my precious book.

1. It’s not about physical vs. digital, but synchronous vs asynchronousIn L&D teams’ minds, the big split used to be between training that happened in-person and training that happened online. 

As Jorge Luis Borges pointed out, a library without an index becomes paradoxically less informative as it grows.

Wow, Aaron himself just answered it!

answered Oct 12 '09 at 18:28

tall old man, clean shaven save for a long white moustache,

which is the right thing to do btw

You can use LibreOffice's Draw

How a memory palace works When we’re learning something new, it requires less effort if we connect it to something we already know, such as a physical place. This is known as elaborative encoding. Once we need to remember the information, we can “walk” around the palace and “see” the various pieces. The idea is to give your memories something to hang on to. We are pretty terrible at remembering things, especially when these memories float freely in our heads. But our spatial memory is actually pretty decent, and when we give our memories some needed structure, we provide that missing order and context. For example, if you struggle to remember names, it can be helpful to link people you meet to names you already know. If you meet someone called Fred and your grandmother had a cat called Fred, you could connect the two. Creating a multisensory experience in your head is the other part of the trick. In this case, you could imagine the sound of Fred meowing loudly. To further aid in recall, the method of loci is most effective if we take advantage of the fact that it’s easiest to remember memorable things. Memory specialists typically recommend mentally placing information within a physical space in ways that are weird and unusual. The stranger the image, the better.

I’m not confident I’ll be able to keep a server running to serve up my notes, so I bundled them up into an archive of pregenerated HTML, which anyone who has a copy can unpack and read, without requiring any online resources.

Complexity: your partner needs to be sufficiently autonomous. Autonomy is promoted by growing inner complexity of the system. Its inner complexity depends on both the number of notes and their relationships with each other.

The Joke File has been scanned into an internal database that is accessible on-site in both the Recorded Sound and Moving Image Research Centers.

CASE OFABDULAZIZ, CABALES AND BALKANDALI v. THE UNITED KINGDOM

His face was a strong—a very strong—aquiline, with high bridge of the thin nose and peculiarly arched nostrils; with lofty domed forehead, and hair growing scantily round the temples but profusely elsewhere. His eyebrows were very massive, almost meeting over the nose, and with bushy hair that seemed to curl in its own profusion. The mouth, so far as I could see it under the heavy moustache, was fixed and rather cruel-looking, with peculiarly sharp white teeth; these protruded over the lips, whose remarkable ruddiness showed astonishing vitality in a man of his years. For the rest, his ears were pale, and at the tops extremely pointed; the chin was broad and strong, and the cheeks firm though thin. The general effect was one of extraordinary pallor. Hitherto I had noticed the backs of his hands as they lay on his knees in the firelight, and they had seemed rather white and fine; but seeing them now close to me, I could not but notice that they were rather coarse—broad, with squat fingers. Strange to say, there were hairs in the centre of the palm. The nails were long and fine, and cut to a sharp point. As the Count leaned over me and his hands touched me, I could not repress a shudder. It may have been that his breath was rank, but a horrible feeling of nausea came over me, which, do what I would, I could not conceal. The Count, evidently noticing it, drew back; and with a grim sort of smile, which showed more than he had yet done his protuberant teeth, sat himself down again on his own side of the fireplace.

hey were driven by a tall man, with a long brown beard and a great black hat, which seemed to hide his face from us. I could only see the gleam of a pair of very bright eyes, which seemed red in the lamplight

hard-looking mouth, with very red lips and sharp-looking teeth, as white as ivory

Dependencies are hoisted, meaning they get installed in the root node_modules folder. This is done for performance reasons: if a dependency is shared by multiple packages, it gets saved only once in the root.

The local package will be copied to the prefix (./node-modules).

I've copied his response here as this question ranks very high in web search results.

More points were awarded to candidates with master’s degrees and more years of experience in similar fields. While this approach seemed to provide a neutral method for evaluating candidates based on qualifications, it soon became apparent that the process, with its reliance on education and experience to the exclusion of other important qualities, was deeply flawed and created barriers to hiring talented, diverse candidates

Happy Third Birthday #24728!

paint, chairs, food, electric and neon lights, smoke, water, old socks, a dog,movies, a thousand other things that will be discovered by the present generation of artists.

When we use a GraphQL API there are two kinds of errors we may encounter: Network Errors and GraphQL Errors from the API. Since it's common to encounter either of them, there's a CombinedError class that can hold and abstract either.

However, this request-by-request mindset doesn’t map well to GraphQL because there’s only one controller and the requests that come to it may be very different.

Michael Young coined the term,[1] formed by combining the Latin root "mereō" and Ancient Greek suffix "cracy", in his essay to describe and ridicule such a society, the selective education system that was the Tripartite System, and the philosophy in general.

Diminishing social mobility excludes the middle class from the hope of achieving the American Dream.

for some analysts this myth of meritocracy entrenches gender and racial inequality. 

That the belief that the United States is a meritocracy is an inherently racist or sexist belief, or that the United States was created by members of a particular race or sex for the purpose of oppressing members of another race or sex.”

Whether you agree or not, to me there's nothing in this world that is entirely apolitical - when there are people there is politics. You don't have to agree with my views, nor do I expect you to. Diversity and disagreement is what drives mankind forward.

Forcing people out of the habit to assume this branch would be called master, is a valuable lesson.

Personally I think it is a very bad idea to leverage political views, even if I may share them, through software.

On existing projects, consider the global effort to change from origin/master to origin/main. The cost of being different than git convention and every book, tutorial, and blog post. Is the cost of change and being different worth it?

The emphasis was made on a raw CDP protocol because Chrome allows you to do so many things that are barely supported by WebDriver because it should have consistent design with other browsers.

However, the term master is out of favor in the computing world and beyond.

Right now, we are building a concept proofing prototype using Anycable.

they handled this with 4 1x dynos on Heroku (before switching to AnyCable they had 20 2x dynos for ActionCable).

No I'm writing it from first principles using the bisect runner as a guide and some other external gems.

For me the diagrams make it easier to talk about what the tests do without getting bogged down by how they do it.

I’m going to add the API Server as an actor to my first test sequence to give some granularity as to what I’m actually testing.

For features like websocket interactions, a single full-stack smoke test is almost essential to confirm that things are going as planned, even if the individual parts of the interaction are also covered by unit tests.

Why does test suite performance matter? First of all, testing is a part of a developer's feedback loop (see @searls talk) and, secondly, it is a part of a deployment cycle.

How to test at the correct level?

As many things in life, deciding what to test at each level of testing is a trade-off:

Unit tests are usually cheap, and you should consider them like the basement of your house

A system test is often better than an integration test that is stubbing a lot of internals.

Only test the happy path, but make sure to add a test case for any regression that couldn’t have been caught at lower levels with better tests (for example, if a regression is found, regression tests should be added at the lowest level possible).

GitLab is transitioning from controller specs to request specs.

These tests should be isolated as much as possible. For example, model methods that don’t do anything with the database shouldn’t need a DB record. Classes that don’t need database records should use stubs/doubles as much as possible.

Black-box tests at the system level (aka end-to-end or QA tests)

White-box tests at the system level (aka system or feature tests)

Levels

A common cause of a large number of created factories is factory cascades, which result when factories create and recreate associations.

Test speed GitLab has a massive test suite that, without parallelization, can take hours to run. It’s important that we make an effort to write tests that are accurate and effective as well as fast.

:js is particularly important to avoid. This must only be used if the feature test requires JavaScript reactivity in the browser. Using a headless browser is much slower than parsing the HTML response from the app.

Use Factory Doctor to find cases where database persistence is not needed in a given test.

A class adds a layer of abstraction, which makes the component API and its inner workings less clear.

Do add business logic to helpers or utilities, so you can test them separately from your component.

A rule of thumb is that data should just be data - it is not recommended to observe objects with their own stateful behavior.

The most important guideline to give is the following: Write clean unit tests if there is actual value in testing a complex piece of logic in isolation to prevent it from breaking in the future Otherwise, try to write your specs as close to the user’s flow as possible

If you don't need to support IE9 or lower, you can use flexbox freely, and don't need to use floated layouts.

Maybe I’m just a worrywart. Just as there’s a tendency to glorify technological progress, there’s a countertendency to expect the worst of every new tool or machine.

Introduce behaviour that is likely to surprise users. Instead have due consideration for patterns adopted by other commonly-used languages.

I've seen (and fixed) Ruby code that needed to be refactored for the client objects to use the accessor rather than the underlying mechanism, even though instance variables aren't directly visible. The underlying mechanism isn't always an instance variable - it can be delegations to or manipulations of a class you're hiding behind a facade, or a session store with a particular format, or all kinds. And it can change. 'Self-encapsulation' can help if you need to swap a technology, a library, an object specification, etc.

a principle I use is: If you have an accessor, use the accessor rather than the raw variable or mechanism it's hiding. The raw variable is the implementation, the accessor is the interface. Should I ignore the interface because I'm internal to the instance? I wouldn't if it was an attr_accessor.

I have been wrapping instance variables in accessor methods whenever I can though.

Also, Sandi Metz mentions this in POODR. As I recall, she also advocates wrapping bare instance variables in methods, even when they're only used internally. It helps avoid mad refactoring later.

Which gets the job done, but that's a chunk of boilerplate for a simple accessor

One of the consequences (although arguably not the primary motivation) of DRY is that you tend to end up with chunks of complex code expressed once, with simpler code referencing it throughout the codebase. I can't speak for anyone else, but I consider it a win if I can reduce repetition and tuck it away in some framework or initialisation code. Having a single accessor definition for a commonly used accessor makes me happy - and the new Object class code can be tested to hell and back. The upshot is more beautiful, readable code.

It was the first to present the concept of creating a function without a superfluous keyword function, replacing it with something that in 2015 was to become the function arrow (=> in ES6, -> in CoffeeScript). He also got rid of the curly braces (like Python), replacing them with indentations. Often in CoffeeScript, you can omit (once required) parentheses, that often unnecessarily decrement the readability of the code.

I like auto-property generation... who needs boilerplate code?

That's not exactly Symbol#to_proc conversion — it's part of the inject interface, mentioned in the documentation. The to_proc operator is &

instance_eval { reduce(:+) / size.to_f }

Programmers should be encouraged to understand what is correct, why it is correct, and then propagate.

add some quality of life stuff like volume sliders, windowed mode, unlimited undo, etc.

Yet even thisdecline is followed by an unexpected resurgence in mnemonics in the 1800s, when Connors claimsthat writing was replacing speaking in school settings (127).

Not only does England fail to producemany memory treatises post-1600, the memory treatises she does produce are largely devoid of theinventive images that mark earlier English treatises and that continued to mark treatises on thecontinent

Willis is more concerned with the construction of a perfectly orderedmental place system than with imagery.

Ong puts it this way:“Ramus can adopt memory intodialectic because his entire topically conceived logic is itself a system of local memory”(Ramus280).However, it is a simplified systemunlike the classical one: The ancient precepts about images and theirfacilitation of invention have been dropped.

Ramist method does away withimaginesand architecturalloci, replacing them with asystem of abstract, logical arrangement.

Memory treatises published in Europe, by half-century.

I offer general remarks on the need for a more detailed history of the canonof memory, which is often (but erroneously) assumed to be a casualty of writing (Corbett andConnors 22) or“modernist”ideologies (Crowley; Pruchic and Lacey). The former argument isdemonstrably untrue; the latter is on the right track but incomplete.

Todate, however, no scholar has taken advantage of bibliographic resources to verify whether or notmemory treatises did in fact decline in England in the latter sixteenth and early seventeenthcenturies, a period that coincides with the continuing influence of iconoclasm and the risinginfluence of English Ramism. In this article I provide such bibliographic evidence, demonstratingthat the publication of memory treatises abated in England following Henry VIII’s reforms andduring the English Civil War

The high costs of implementing a TTP come about mainly because traditional security solutions, which must be invoked where the protocol itself leaves off, involve high personnel costs. For more information on the necessity and security benefits of these traditional security solutions, especially personnel controls, when implementing TTP organizations, see this author's essay on group controls. The risks and costs borne by protocol users also come to be dominated by the unreliability of the TTP – the DNS and certificate authorities being two quite commom sources of unreliability and frustration with the Internet and PKIs respectively.

it’s also the case that the web was first built in the 90s to share complicated academic work and make it editable by its readers

I'm not sure why MSFT decided to change these codes in the first place. While it might have been a noble goal to follow the IETF standard (though I'm not really familiar with this), the old codes were already out there, and most developers don't benefit by the new codes, nor care about what these codes are called (a code is a code). Just the opposite occurs in fact, since now everyone including MSFT itself has to deal with two codes that represent the same language (and the resulting problems). My own program needs to be fixed to handle this (after a customer contacted me with an issue), others have cited problems on the web (and far more probably haven't publicised theirs), and MSFT itself had to deal with this in their own code. This includes adding both codes to .NET even though they're actually the same language (in 4.0 they distinguished between the two by adding the name "legacy" to the full language name of the older codes), adding special documentation to highlight this situation in MSDN, making "zh-Hans" the parent culture of "zh-CHS" (not sure if it was always this way but it's a highly questionable relationship), and even adding special automated code to newly created "add-in" projects in Visual Studio 2008 (only to later remove this code in Visual Studio 2010, without explanation and therefore causing confusion for developers - long story). In any case, this is not your doing of course, but I don't see how anyone benefits from this change in practice. Only those developers who really care about following the IETF standard would be impacted, and that number is likely very low. For all others, the new codes are just an expensive headache. Again, not blaming you of cours

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

I'm not sure why MSFT decided to change these codes in the first place. While it might have been a noble goal to follow the IETF standard (though I'm not really familiar with this), the old codes were already out there, and most developers don't benefit by the new codes, nor care about what these codes are called (a code is a code).

What may not be expected in a country of eternal light? I may there discover the wondrous power which attracts the needle; and may regulate a thousand celestial observations, that require only this voyage to render their seeming eccentricities consistent for ever. I shall satiate my ardent curiosity with the sight of a part of the world never before visited, and may tread a land never before imprinted by the foot of man

I tried all the different static site generators, and I was annoyed with how everything was really complicated. I also came to the realization that I was never going to need a content management system with the amount of blogging I was doing, so I should stop overanalyzing the problem and just do the minimum thing that leads to more writing.

This is super important because the more open protocols we have, the more open systems we will have.

A litmus test on whether an option belongs to adapter config or kit config, would be to ask whether the option becomes irrelevant when you switch the adapter to static.

One way to look at your current situation is that you're not paying them enough to tell you the gory details, not that you're not knowledgeable enough.

Hey, I'm a PhD in [field] and do [whatever] professionally. Before calling you, I've narrowed down the problem to [something on their end], so that's what needs to be addressed. If I could speak to an engineer about [specific problem], that'd be great; but if we've gotta walk through the script, let's just knock it out quickly. If they end up requiring the script, then the best way to use your expertise is to run through it quickly. Keep the chit-chat to a minimum and just do the stuff efficiently. If they start describing how to perform some step, you might interrupt them with, "Got it, just a sec.", then let them know once you're ready for the next step.

So what can you do to demonstrate your technical knowledge? Well, you are doing the right thing by using the correct technical terms. That will give an indication to the person handling the ticket. Explicitly explaining your role as the administrator or developer should also help.

From experience I can say that professionals will be more forgiving if you go through things at a basic level than amateurs who have no idea what you're talking about, so people will probably err on the side of caution and not assume the customer has a high level of expertise.

the problem is that I write a lot of these emails and they are a waste of my and everyone elses time

µ

J.‑C. Bonichot, A. Arabadjiev, A. Prechal, M. Safjan, P.G. Xuereb and L.S. Rossi

L. Bay Larsen

A. Prechal

A. Arabadjiev

J.‑C. Bonichot

K. Lenaerts

J.‑C. Bonichot

I had always assumed – without realising the assumption – that the ancient knowledge keepers would have progressed around the henge posts or stones much as I do around a memory palace. It hadn’t occurred to me that there may be experts on each topic, ‘owning’ each post or stone and the knowledge it represented. Is there any way the archaeology could ever tell us if this is the case?

“Finance is, like, done. Everybody’s bought everybody else with low-cost debt. Everybody’s maximised their margin. They’ve bought all their shares back . . . There’s nothing there. Every industry has about three players. Elizabeth Warren is right,” Ubben told the Financial Times.