Requirements: Ruby and Bundler should be installed.

One of his last works, the Aurifodina, “The Mine of All Arts and Sci-ences, or the Habit of Excerpting,” was printed in 1638 (in 2,000 copies) andin another fourteen editions down to 1695 and spawned abridgments in Latin(1658), German (1684), and English.

To create trails  When we are studying a text we need to take the time to understand more than just the storyline. During your second reading, any comments made during the first reading (marginal comments or summaries) will quickly give you the gist of your first reading, so that you can take advantage of your second.

Appendix F: Questions Universities Can Ask Certification Bodies to Assess Quality of Certifications

“Public research universities are committed to improving the workforce outcomes of their students and to addressing the workforce needs of local economies. This approach can ensure students that their credentials will have value to the labor market, and it can ensure employers that graduates have the skills required to perform in the workplace.”

If you now think: “That’s ridiculous. Who would want to read andpretend to learn just for the illusion of learning and understanding?”please look up the statistics: The majority of students chooses everyday not to test themselves in any way. Instead, they apply the verymethod research has shown again (Karpicke, Butler, and Roediger2009) and again (Brown 2014, ch. 1) to be almost completelyuseless: rereading and underlining sentences for later rereading.And most of them choose that method, even if they are taught thatthey don’t work.

Reading, especially rereading, caneasily fool us into believing we understand a text. Rereading isespecially dangerous because of the mere-exposure effect: Themoment we become familiar with something, we start believing wealso understand it. On top of that, we also tend to like it more(Bornstein 1989).

eBook 978-1-952271-05-2 $24.99

t be issued for unevaluated learning accomplishments, such as the mere completion of a series of tasks, attendance at events, or for learning that has not been assessed, as competency and learning accomplishment evaluation is very important.

After all, the academic disciplines, as they have come down to us, represent an implicit taxonomy that favors analytical reasoning and discursive practices.

You know you have to read "between the lines" to get the most out of anything. I want to persuade you to do something equally important in the course of your reading. I want to persuade you to write between the lines. Unless you do, you are not likely to do the most efficient kind of reading.

Francis Bacon, for instance, thought that "some books are to be tasted, others to be swallowed and some few to be chewed and digested; that is, some books are to be read only in parts; others to be read, but not curiously; and some few to be read wholly, and with diligence and attention."

A recent addition to the writer-editor-reader relationship is something called a “sensitivity reader,” that is someone of diverse background who can advise on dicey cultural matters whom writers are now encouraged to consult.

Serious reading will require just as much effort as it has always required.

Mr. Byers coined a term — “book-wrapt” — to describe the exhilarating comfort of a well-stocked library.

Law One: The more reading you assign, the less the students will read. Law Two: The more you talk in class, the less the students will read.

Our elders say that ceremonies are the way we “remember to remember,”

an international questionnaire designed to capture teachers’ general teaching characteristics and experience, self-efficacy teaching online, fostering online presence and institutional support transitioning to online teaching as a result of Covid-19

Worst practices

I think of the Kindle and what enormous potential that browser had to change our relationship with the internet, to push it towards a web that you read (instead of one that tries so very hard to read you).

The other commenters are right about the potential solutions. However, it is actually considered a best practice to move the object with the index signature to a nested property.Said differently: No property in the object with the index signature should depart from how the index signature is typed.

For example, it is worth discussing the process of Wikipedia

habits of mind surrounding technologies

“I love you. I’m sorry. Please forgive me. Thank you.”

while the super-rich may move through through world cities, their cosmopolitan practices and lifestyles rarely break out of the exclusive transnational spaces which stand at the intersecting points of particular corporate, capital, technological, information and cultural lines of flow.

“We’ve been thoughtful,” Amazon continued, “about adding only features and experiences that preserve and enhance the reading experience.” The question of whose experience doesn’t seem to come up.

Skimming through pages, the foremost feature of the codex, remains impossible in digital books.

In other words, as far as technologies go, the book endures for very good reason. Books work.

Update API usage of the view helpers by changing javascript_packs_with_chunks_tag and stylesheet_packs_with_chunks_tag to javascript_pack_tag and stylesheet_pack_tag. Ensure that your layouts and views will only have at most one call to javascript_pack_tag or stylesheet_pack_tag. You can now pass multiple bundles to these view helper methods.

an ongoing, complex process of aligning resources, practices, and initiatives of multiple communities [20].

The goal is not to read as many books as possible. The goal is to gain as much wisdom as you can.

Using models while reading can also help you get more out of the book. Here are some examples of paths they might lead you down: Confirmation bias: Which parts of this book am I ignoring? Does this book confirm my opinions? (Okay, but does it actually affirm your beliefs or are you just seeing what you want to see? If you cannot think of a single point in the book that you disagreed with, confirmation bias is likely distorting your reasoning.) Bayesian updating: What opinions should I change in light of this book? How can I update my worldview using the information in it? Keep in mind the words of John Maynard Keynes: “When the facts change, I change my mind. What do you do, sir?” Incentives: What motivates the characters or the author? What are they seeking? What is their purpose? Here’s how Kurt Vonnegut described the importance of incentives in books: “When I used to teach creative writing, I would tell the students to make their characters want something right away—even if it’s only a glass of water. Characters paralyzed by the meaninglessness of modern life still have to drink water from time to time.” Availability bias: Are the books I have recently read affecting how I perceive this one? How are my immediate past experiences shaping my reading? Am I assigning undue importance to parts of this book because they are salient and memorable? Social proof: How is social proof—the number of copies sold, bestseller status, the opinions of others—affecting my perception of this book? Is the author using social proof to manipulate readers? It is not unusual for authors to buy their way onto bestseller lists, providing social proof that then leads to substantial sales. As a result, mediocre books can end up becoming popular. It’s a classic case of the emperor having no clothes, which smart readers know to look out for. Survivorship bias: Is this (nonfiction) book a representation of reality or is the author failing to account for base rates? Survivorship bias is abundant in business, self-help, and biographical books. A particular case of a successful individual or business might be held as the rule, rather than the exception. Utility: If a book offers advice, does it have practical applications? At what point do diminishing returns set in?

Author and librarian Nancy Pearl advocates the “Rule of 50.” This entails reading the first 50 pages of a book and then deciding if it is worth finishing. The Rule of 50 has an interesting feature: once you are over the age of 50, subtract your age from 100 and read that many pages. Pearl writes: “And if, at the bottom of Page 50, all you are really interested in is who marries whom, or who the murderer is, then turn to the last page and find out. If it’s not on the last page, turn to the penultimate page, or the antepenultimate page, or however far back you have to go to discover what you want to know.…When you are 51 years of age or older, subtract your age from 100, and the resulting number (which, of course, gets smaller every year) is the number of pages you should read before you can guiltlessly give up on a book.…When you turn 100, you are authorized (by the Rule of 50) to judge a book by its cover.”

Most of us were taught as children to treat books as something sacred—no folding the page corners, and no writing in the margins, ever.

Book summary services miss the point. A lot of companies charge ridiculous prices for access to vague summaries bearing only the faintest resemblance to anything in the book. Summaries can be a useful jumping-off point to explore your curiosity, but you cannot learn from them the way you can from the original text.*

The most common and sensible location for putting down thoughts, critique or notes was the margin of the medieval book. Consider this: you wouldn’t think so looking at a medieval page, but on average only half of it was filled with the actual text. A shocking fifty to sixty percent was designed to be margin. As inefficient as this may seem, the space came in handy for the reader. As the Middle Ages progressed it became more and more common to resort to the margin for note-taking.

Dots and lines are particularly common ingredients of such footnote symbols. Interestingly, their first appearance is not as a connector of comment and text, but as an insertion mark that added an omitted line into the text.

Evidently, these two groups of bookmarks—static and dynamic—provided very different approaches to marking information—and thus to a book’s use. Readers who added clip-on or “spider” bookmarks anticipated they would need to retrieve information not from one single page but from a changing number of pages. In other words, movable bookmarks served an audience with a shifting knowledge “appetite,” while the static ones encouraged a more “ritual” use of a book. In other words, both types are telling, in their own way, about medieval reading culture.

I really hope they keep breaking it. Being the lead on a library for several years, most of the forced refactors were pretty straight forward and in almost every case made our code either more sound or easier to be consumed. Now I work on a runtime that embeds TypeScript and 3.5.1 has broken some code, thought it took me all of about 15 minutes to make the changes to adopt it, and in every case, it broke because we were being a bit loose with the types. While it didn't find any bugs, it made the code more "safe".

Step 3: Set up reading storage and a reading environment.

You particular circumstances may or may not warrant a way different from what lhunath (and other users) deem "best practices".

hen selecting by text it is best to use the byRole query as it helps enforce accessibility best practices.

When defining accessors in Ruby, there can be a tension between brevity (which we all love) and best practice.

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.

Setting an instance variable by going through a setter is good practice, and using two access modifiers is the way to accomplish that for a read-only instance variable

BCP stands for Best Current Practice

As a general rule: You should quote everything (that may be quoted).

Jesuit manuals such as Jeremias Drexel’s Aurifodina, subtitled The Mine of All Arts and Sciences, or the Habit of Excerpting, explained how to best take notes from reading to create commonplace books: personal notebooks of reading extracts that contained the religious, ethical, and political maxims deemed necessary to lead a good life. There were even admonitions about which texts not to read and how not to fold page corners or to mark texts with fingernail scratches.

increasing the number and diversity of climate actors

Also cross-compatibility with mail clients can be hairy, so you should see what the industry experts are doing.

You should always specify the height and the width of an image if only to help the browser lay the page out even before the image has been downloaded.

The quirky looking printf is necessary to correctly expand the script's arguments in $@ while protecting possibly quoted parts of the command (see example below).

For path names with newlines it is better to quote each pathname.

each of which we could show to be more beautiful, and more usable than the original.

You might not always notice, but Material Design is constantly evolving and iterating based on research.

Your validation functions should also treat undefined and '' as the same. This is not too difficult since both undefined and '' are falsy in javascript. So a "required" validation rule would just be error = value ? undefined : 'Required'.

here is my set of best practices.I review libraries before adding them to my project. This involves skimming the code or reading it in its entirety if short, skimming the list of its dependencies, and making some quality judgements on liveliness, reliability, and maintainability in case I need to fix things myself. Note that length isn't a factor on its own, but may figure into some of these other estimates. I have on occasion pasted short modules directly into my code because I didn't think their recursive dependencies were justified.I then pin the library version and all of its dependencies with npm-shrinkwrap.Periodically, or when I need specific changes, I use npm-check to review updates. Here, I actually do look at all the changes since my pinned version, through a combination of change and commit logs. I make the call on whether the fixes and improvements outweigh the risk of updating; usually the changes are trivial and the answer is yes, so I update, shrinkwrap, skim the diff, done.I prefer not to pull in dependencies at deploy time, since I don't need the headache of github or npm being down when I need to deploy, and production machines may not have external internet access, let alone toolchains for compiling binary modules. Npm-pack followed by npm-install of the tarball is your friend here, and gets you pretty close to 100% reproducible deploys and rollbacks.This list intentionally has lots of judgement calls and few absolute rules. I don't follow all of them for all of my projects, but it is what I would consider a reasonable process for things that matter.

This creates what is essentially an evolution process for the program, causing it to depart from the original engineered design. As a consequence of this and a changing environment, assumptions made by the original designers may be invalidated, introducing bugs.

D3 4.0 is modular. Instead of one library, D3 is now many small libraries that are designed to work together. You can pick and choose which parts to use as you see fit.

I totally understand that there may be a majority still considering this a bad practice and thus keeping it disabled by default in production seem ok. But there could at least be an option to enable it for people who want to, no?

Personal and professional development will follow andultimately these very same characteristics and approaches will naturally transfer intopractice and in direct contact with young people

the better a student/youth worker knows himself/herself the more likely he/shewill be able to help others know themselves;

always use real <label for="correct_input"> elements. Just that alone is a UX consideration all too many forms fail on

step :direct_debit

This connects the failure output to the previous task, which might create an infinity loop and waste your computing time - it is solely here for demonstrational purposes.

Yes, we could and should use Reform or Dry-validation here.

there are two key elements to an anti-pattern that distinguish it from a bad habit, bad practice, or bad idea

Each of the programming language generations aims to provide a higher level of abstraction of the internal computer hardware details, making the language more programmer-friendly, powerful, and versatile.

providing best practices for both HTML-rendering controllers and APIs.

we’re going to look how improved pattern matching and rightward assignment make it possible to “destructure” hashes and arrays in Ruby 3—much like how you’d accomplish it in, say, JavaScript

Like all best practices, I think the way you will resolve a problem will depend of the application you are doing.

If you're creating an actual, informational web page, stick to frameless HTML, CSS and unobstrusive JavaScripts and keep in mind that the page should still be usable with scripting disabled.

if you want a copy of my consolidated project management Excel workbook, feel free to contact me. It's gratis. I'm all for extending best practices.

For the future, you should: Install LTS (Long-term support) versions as they have an 8-year life span (with Extended Security Maintenance) or 5 years without. The current LTS version is Ubuntu 18.04.1 LTS Bionic Beaver released on July 26, 2018 with an EOL in April 2023. OR Carefully watch the EOL of the interim / development releases and upgrade frequently.

Progress is made of compromises, this implies that we have to consider not only disadvantages, but also the advantages. Advantages do very clearly outweigh disadvantages. This doesn’t mean it perfect, or that work shouldn’t continue to minimize and reduce the disadvantages, but just considering disadvantages is not the correct way.

I don’t find the software slow, I find the startup time for snap packages when the start for the first time on a session slow, but that has been improved, and it’s public that the snapcraft team has been working hard to improve that.

There is seldom any good reason to use this option. Mixing ERB into your controllers defeats the MVC orientation of Rails and will make it harder for other developers to follow the logic of your project. Use a separate erb view instead.

That practice went from being standard practice to being a faux pas (not abstracting JavaScript functionality away from HTML) to, eh, you need it when you need it.

When you use target="_blank" with Links, it is recommended to always set rel="noopener" or rel="noreferrer" when linking to third party content. rel="noopener" prevents the new page from being able to access the window.opener property and ensures it runs in a separate process. Without this, the target page can potentially redirect your page to a malicious URL. rel="noreferrer" has the same effect, but also prevents the Referer header from being sent to the new page. ⚠️ Removing the referrer header will affect analytics.

Guidelines do very little. Developer discipline is not a reliable method of encouraging best practices, they have to be enforced to be reliable.

Additionally, if we ever want to standardize more of JSX we need to start moving away from some of the more esoteric legacy behaviors of React.

Props and state can change, and components should handle those changes whenever they happen.

Even if a component is rendered just once, your design will improve if rendering twice doesn’t break it.

Teaching Tolerance offers some clear practices that can help establish connectedness:

but everything they were doing started to make sense

From npm@5.2.0, npm ships with npx package which lets you run commands from a local node_modules/.bin or from a central cache.

After years of copy-pasted, locally-hosted scripts, maybe Bower if you were lucky, npm has finally made it possible to easily distribute client-side packages.

Currently, the documentation of :global() is very poor, IMO styling best practices deserve a separate section in the docs.

With Svelte, components and files have a one-to-one relationship. Every file is a component, and files can't have more than one component. This is generally a "best practice" when using most component frameworks.