Can I use a card index for note taking?Yes, you can certainly use a card index for note-taking. Card indexes have been a popular method of note-taking for many years and can be very effective. Here are a few tips to get you started:Choose the right size of card index: Card indexes come in various sizes, so choose one that is comfortable for you to handle and store.Use cards of the same size: Using cards of the same size ensures that they will fit into your index box or file and that they will be easy to handle.Choose a system for organizing your cards: You can organize your cards alphabetically, by subject, by date, or any other system that works for you.Use one card per idea or topic: To keep your notes organized and easy to find, use one card per idea or topic.Keep your notes brief and to the point: Use brief notes that summarize the key points of your topic. This will make it easier to review your notes and find the information you need.Review your notes regularly: Review your notes regularly to keep the information fresh in your mind and to make sure you haven't missed anything important.Overall, a card index can be a very effective method of note-taking, as long as you develop a system that works for you and use it consistently.

Yes, you can definitely use a card index for note-taking. In fact, many people find card indexes to be a useful and convenient tool for organizing and storing notes. Here are some tips for using a card index for note-taking:Choose a system: Decide on a system for organizing your cards. You could organize them alphabetically, by topic, by date, or by any other method that works for you.Choose the size of cards: Choose the size of cards that works best for your needs. Common sizes include 3" x 5", 4" x 6", and 5" x 8".Use one card per idea: Write one idea or piece of information on each card. This will help keep your notes organized and easy to reference.Include keywords: Include keywords on each card to make it easier to find relevant information later.Use dividers: Use dividers to separate different topics or sections in your card index. This will help keep your notes organized and easy to navigate.Carry it with you: A card index is a portable tool, so you can take it with you wherever you go. This makes it easy to take notes on the go and to refer to your notes when you need them.Overall, a card index can be a useful and efficient tool for note-taking, especially if you prefer a physical, tangible way of organizing and storing information.

he spoke of the ‘historian’s credo’ that ‘the factscrubbed clean is more eternal than perfumed or rouged words’ (Marcus, 1957:466).17

Moreover, card indexes give further form to Bruno Latour’s meditations on writing: ifLatour described writing as a kind of ‘flattening’ of knowledge, then card indexes, likevertical files, represent information in three dimensions, making ideas simultaneouslyimmutable and highly mobile, and the smallness of ideas and ‘facts’ forced to fit onpaper slips allowed for reordering (Latour, 1986: 19-20).

However, the miniscule size of ‘facts’ did not neces-sarily reflect Deutsch’s adherence to any theory of information. Instead, it indicated hispersonal interest in distinctions of the smallest scale, vocalized by his motto ‘de minimiscurat historicus’, that history’s minutiae matter.

Bruno Latour has reflected, information is more malleable when it is not too large(Daston, 2002; Latour, 1986: 19).

The ‘size’ of facts served a dream of information recombination, and was served bythe card form. Other advocates of Zettelkasten like Johann Jacob Moser (1701–1785)remarked that fairly small facts meant the mass of information was broken down to itsindividual components and thus could be constantly reshuffled in a ‘game of cards’(Krajewski, 2011: 53-5).

We know we’re supposed to write one idea per page/card. What constitutes an “idea”? How do I identify what a good idea is? What does an idea that fits on one card feel like?

Children, who in our post-agricultural age are otherwise pretty useless economically, can actually be usefully employed at this stage. They love cutting things with scissors, and precision is not crucial.

Cohen was reluctant to provide reference values for his standardized effect size measures. Although he stated that d = 0.2, 0.5 and 0.8 correspond to small, medium and large effects, he specified that these values provide a conventional frame of reference which is recommended when no other basis is available.

Filing is a tedious activity and bundles of unsorted notes accumulate. Some of them get loose and blow around the house, turning up months later under a carpet or a cushion. A few of my most valued envelopes have disappeared altogether. I strongly suspect that they fell into the large basket at the side of my desk full of the waste paper with which they are only too easily confused.

Current ruby releases generate *.tar.gz, *.tar.bz2, *.tar.xz, and *.zip. But I think we can stop generating *.tar.bz2. I think *.tar.bz2 are less merit. For better size, *.tar.xz exist. For better compatibility, *.tar.gz and *.zip exist.

In one way, the cards’ uniform size and format was part of Deutsch’sdream to produce a systematic method of research and writing.

Thesheets must always be of equal size, or at least of equal height in order not to get stuck or beoverlooked when manually searching for sheets or adding them.

much better than the SOM is built from the bottom up

count up all the potential customers that would be a good fit for your business and multiply that number by the average annual revenue of these types of customer in your market

TAM refers to the total market demand for a product or service. It’s the maximum amount of revenue a business can possibly generate by selling their product or service in a specific market

number of customers that you are able and willing to target

calculate TAM by running a bottom-up analysis of your industry

This opens the possibility of doing a design much better than Squeak's, both fundamentally and at the user-level, to create a model of an entire personal computer system that is extremely compact (under 20,000 lines of code)

the Squeak system, which was derived from PARC Smalltalk, includes its own operating system, GUI, development tools, graphics, sound, Internet sockets, and many applications including Etoys and Croquet, yet is only about 230,000 lines of code. The executables are about 2.8MB and only half of this code is generally used.

The Southern Levant, situated between modern day southern Syria via Israel to Sinai, has a spatiotemporally dense and continuous Paleolithic archaeological record offering a unique opportunity to detect faunal changes, including those predating the appearance of Homo sapiens (Bar-Yosef, 1980; Stutz, 2014). It is thus a suitable model to test long-term changes in the body mass of mammalian assemblages, in view of paleoclimates and changing human lineages, to decipher whether climate and/or humans are responsible for animal body size declines. The excellent archaeological record can further illuminate whether size declines are observed since hominins first colonized the region, or whether they start with the emergence of Homo sapiens (Louys et al., 2021), or are concentrated in the last glacial and its aftermath. We tested whether the size, and size changes, in hominin prey through the Pleistocene and early Holocene were related to time, the prevailing human lineages and cultures, paleoenvironment, and temperatures.

Setting "img max-width:100%" is a technique employed in responsive/fluid web site design so that images re-size proportionally when the browser is re-sized. Apparently some css grid systems have started setting this style by default. More info about fluid images here: http://www.alistapart.com/articles/fluid-images/

Now, our img element will render at whatever size it wants, as long as it’s narrower than its containing element. But if it happens to be wider than its container, then the max-width: 100% directive forces the image’s width to match the width of its container.

It is important to realize that while the block size is fixedbetween any particular pair of adjacent levels in the hierarchy, other pairs of levelscan have different block sizes.

tlrobinson interpreted right that codebase size should be measured in number of tokens

To manage a variable-size stack frame, x86-64 code uses register %rbp to serveas a frame pointer

Defining the project scope means that you must have a clear vision and agreement on the outcomes of the project. This allows any deliverable of the project to remain on schedule.

When you give an element a width of 100% in CSS, you’re basically saying “Make this element’s content area exactly equal to the explicit width of its parent — but only if its parent has an explicit width.” So, if you have a parent container that’s 400px wide, a child element given a width of 100% will also be 400px wide, and will still be subject to margins, paddings, and borders — on top of the 100% width setting.

The most likely cause of this problem is having set the height of an element to be 100% of the page somewhere in your CSS. This is normally on the html or body elements, but it could be on any element in the page. This can sometimes be got around by using the taggedElement height calculation method and added a data-iframe-height attribute to the element that you want to define the bottom position of the page. You may find it useful to use position: relative on this element to define a bottom margin or allow space for a floating footer.

case-driven trial was planned 205to accrue 130case

Are you also tired and fed up with the bulkiness of jQuery, but also don't want to have to type document.querySelector("div").appendChild(document.createTextNode("hello")); just to add some text to an element?

That image only contains 200 pixels horizontally, but the browser stretches it to 400px wide or even farther!Luckily, you’ll see there’s an easy “fix” there at the end: our old good friend the width attribute!<img src="example.gif", srcset="example.gif 200w" sizes="(min-width: 400px) 400px, 100vw" width="200" /* <=== TA-DA! */ class="logo">As long as you can specify the width attribute so it reflects the true maximum size of your largest image, you won’t run into this problem of having sizes make your image wider than it naturally should go.

The selected source size affects the intrinsic size of the image (the image’s display size if no CSS styling is applied).

Of course in the world of responsive images, we put constraints on our images with CSS:img { max-width: 100%;}Now the image appears at it’s natural size unless it’s constrained by the parent container! Excellent.

Trying to force this one thing to work for everyone is the worst way to do that.

The elimination of what is arguably the biggest monoculture in the history of software development would mean that we, the community, could finally take charge of both languages and run-times, and start to iterate and grow these independently of browser/server platforms, vendors, and organizations, all pulling in different directions, struggling for control of standards, and (perhaps most importantly) freeing the entire community of developers from the group pressure of One Language To Rule Them All.

Situation: you have a single line of text in a flex child element. You don’t want that text to wrap, you want it truncated with ellipsis (or fall back to just hiding the overflow). But the worst happens. The unthinkable! The layout breaks and forces the entire flex parent element too wide. Flexbox is supposed to be helping make layout easier!

Great, I can use vw to scale text so it doesn't look puny on a desktop! Perfect... Oh. Huh, now the text is too small to read when viewed on a phone. Okay, well I can just use "max(x,y)" to make sure it doesn't get shrunk beyond a minimum size. Perfect... Oh. Hmm. Looks like "max" isn't supported properly by Chrome. Okay, well guess I'll just use "px" again.

auto As a maximum, identical to max-content. As a minimum it represents the largest minimum size (as specified by min-width/min-height) of the grid items occupying the grid track.

This is really cool! Having the content decide on the space it needs is so powerful!

fixed: With this value, the table’s layout ignores the content and instead uses the table’s width, any specified width of columns, and border and cell spacing values. The column values used are based on widths defined on columns or cells for the first row of the table

It is also very likely that the contents of the table might change the structure or dimensions of the table. For example, long words residing in the table cells can cause the cell width to increases. If you fix that problem, it might happen that the long words cross the cell boundaries.

The only difference is that in this case “auto” will not work, but instead “height: 100%” is required.

Blocks Don’t Need 100% Width When we understand the difference between block-level elements and inline elements, we’ll know that a block element (such as a <div>, <p>, or <ul>, to name a few) will, by default expand to fit the width of its containing, or parent, element (minus any margins it has or padding its parent has).

It seems like this should be one of the easiest things to understand in CSS. If you want a block-level element to fill any remaining space inside of its parent, then it’s simple — just add width: 100% in your CSS declaration for that element, and your problem is solved. Not so fast. It’s not quite that easy. I’m sure CSS developers of all skill levels have attempted something similar to what I’ve just described, with bizarre results ultimately leading to head scratching and shruggingly resorting to experimenting with absolute widths until we find just the right fit. This is just one of those things in CSS that seems easy to understand (and really, it should be), but it’s sometimes not — because of the way that percentages work in CSS.

min-width: 0;

The explanation here is that the minimum size of an fr unit is auto. Grid then looks at the min-content size of the item. If the item has a size (you’ve given it a width) or has something in it with a size such as an image, the min-content size might be much bigger than the share of available space you think 1fr will give you. It’s easy to think of 1fr as being “one part of the space in the grid container” when it is really one part of the space left over. If there is space to grow then the tracks grow from that min-content size assigning space. Using minmax, as you have pointed out, is the best thing to do if you want to forcibly have equal width tracks, as that says “I want this track to have a min-content size of 0”, you could potentially in that situation end up with overflows as you lose the squishiness.

And since auto is entirely based on content, we can say it is “indefinitely” sized, its dimensions flex. If we were to put an explicit width on the column, like 50% or 400px, then we would say it is “definitely” sized.

Zappos created models to predict customer apparel sizes, which are cached and exposed at runtime via microservices for use in recommendations.

Alternatively, you can build a custom icon system from existing icon libraries. To save on load times and improve performance, I would recommend always creating icon systems that include only the icons that you will use. If you’re only using 10 of them throughout your site, there is no good reason to link to the entire Fontawesome library of icons.

Rules of thumb on magnitudes of effect sizes

Microbundle also outputs a modern bundle specially designed to work in all modern browsers. This bundle preserves most modern JS features when compiling your code, but ensures the result runs in 90% of web browsers without needing to be transpiled. Specifically, it uses preset-modules to target the set of browsers that support <script type="module"> - that allows syntax like async/await, tagged templates, arrow functions, destructured and rest parameters, etc. The result is generally smaller and faster to execute than the esm bundle

Power Analyses

Replaced nested `require` statements with `import` declarations for the sake of a leaner bundle. This entails adding empty imports to three files to guarantee correct ordering – see https://github.com/styled-components/styled-components/pull/100

He took three paces—with the fourth he reached his goal,       

Perhaps we should detect URLSearchParams objects differently (using duck typing detection instead of instanceof window.URLSearchParams, for example) but the solution isn't adding a specific polyfill to Axios (as it'd increase the bundle size and still won't work with other polyfills).

Many people recently are complaining about bundler performance. But I don’t think any tool is going to solve performance problems. Bundlers can try innovative ideas such as multi-threading and improved caching, but you’re always going to hit a limit. If you’re having performance problems, it’s more likely because you’re not keeping tabs of what you’re importing, and haven’t considered splitting your project into multiple projects.

There'll be no more warnings. But if you open bundle.js, you'll see something shocking: it contains the entirety of React and React DOM. That's 7000 LoC!

This is a demonstration of building a custom D3 4.0 bundle using ES2015 modules and Rollup. Custom bundles can be optimized to contain only the code you need. This example exposes just three fields on the d3 object: d3.event, d3.select and d3.selectAll. The minified and gzipped bundle is only 3,691 bytes, a savings of 93% over the default build!

Why I’m excited about ES6 modules: a custom build of D3 4.0 in 3,610 gzipped bytes. (93% smaller!)

If we compile our empty component and bundle it with Svelte internals, it ends up being 2,080 bytes uncompressed, and 1,043 bytes gzipped. So the overhead for using Svelte ends up being only a kilobyte. Compare that to other frameworks that require 10x or 100x that many bytes just to mount an empty component!

In addition, HBOT was found to reduce mortality rates from necrotizing fasciitis, and significantly decreased wound size in nonhealing diabetic wounds.

The amount of moneyparticipants transferred to the agent (from $0.00 to $0.30) was usedas an indicator of trustworthiness, as was how much money theybelieved they would receive back from the agent (0% to 100%)

It's also a good way to make sure my personal thoughts don't get exposed to a more wider audience.

Factors that affect power

Cohen’s recommendations:  Jacob Cohen has many well-known publications regarding issues of power and power analyses, including some recommendations about effect sizes that you can use when doing your power analysis.  Many researchers (including Cohen) consider the use of such recommendations as a last resort, when a thorough literature review has failed to reveal any useful numbers and a pilot study is either not possible or not feasible.  From Cohen (1988, pages 24-27):

Plasmids (IncP/N/W)with 373short and rigid pili only transfer efficiently on solid surfaces, unlike those with longand flexible 374pili (IncF/H/T/J),capable of transferring equally well in liquidand on solid surfaces[35,36]

Interplay Between Optimization and Generalization of Stochastic Gradient Descent with Covariance Noise

Revisiting Small Batch Training for Deep Neural Networks

Don't Use Large Mini-Batches, Use Local SGD

Approximate Fisher Information Matrix to Characterise the Training of Deep Neural Networks

If the rule is relaxed to embrace pattern alone, as explicitly advocated by Rensch and Mayr, exceptions can still be found both intra- and interspecifically. Within species, Rensch (1938) reported that 10–30% of the warm-blooded species examined by him were exceptions to Bergmann's rule. Ray (1960) reviewed the literature on body size variation in relation to climate for poikilotherms, and concluded that the rule was supported by 75% of species studied. Nevertheless, these percentages (see also James, 1970; Yom-Tov & Nix, 1986) support Mayr's (1956) contention that the rule would be proved if upheld by the majority of species, although his subsequent definition of a majority as more than 50%(Mayr, 1963) is rather generous in respect of a ‘rule’. Some studies, however, do find that the percentage of species in agreement with the intraspecific rule fails even this criterion (McNab, 1971).

It is the definition of Bergmann's rule, and specifically the taxonomic level at which the rule is considered to act, that has done most to cloud the degree of generality of the effect it describes. Bergmann himself (quoted in James, 1970) stated that ‘(i)f we could find two species of [homeothermic] animals which would only differ from each other with respect to size, . . . (t)he geographical distribution of the two species would have to be determined by their size . . . if there are genera in which the species differ only in size, the smaller species would demand a warmer climate, to the exact extent of the size difference.’ Also: ‘(a)lthough it is not as clear as we would like, it is obvious that on the whole the larger species live farther north and the smaller ones farther south.’Bergmann's formulation was later altered by Rensch (1938), whose revised definition was that ‘within a Rassenkreis [complex of races] of warm-blooded animals the races living in colder climates are generally larger than the races living in warmer regions.’ Rensch considered that the new definition better fitted the rule as then understood, but was quite clear that the revision was his own (‘I myself reduced it to the geographical races of a species’; Rensch, 1938). It was this revision that subsequently became the accepted formulation of Bergmann's rule; later definitions included ‘Races of warm blooded vertebrates from cooler climates tend to be larger than races of the same species from warmer climates’(Mayr, 1956), and ‘The smaller-sized geographic races of a species are found in the warmer parts of the range, the larger-sized races in the cooler districts’(Ray, 1960; see also definitions in Gittleman, 1985; Goudie & Ankney, 1986; Paterson, 1990; McDowall, 1994; Steudel, Porter & Sher, 1994; Smith, Betancourt & Brown, 1995; Atkinson & Sibly, 1997).The notion that the application of Bergmann's rule at the intraspecific level is a derived state was emphasized by James (1970), who noted that it was a considerable modification of Bergmann's original message, although one that fitted well with knowledge of intraspecific body size variation. Quotations from Bergmann (1847; given in translation by James, 1970) imply that he considered the effect to be interspecific, but between closely related species. Whether he intended the example he gave of ‘species within a genus’ to be literal is unclear. Whichever, it is clear that his formulation was not intraspecific, as he thought it ‘paradoxical that the effects of the same rule in races of animals are not very apparent’(Bergmann, 1847, quoted in James, 1970). In this context, it is interesting that Mayr (1956; see also Rensch, 1938) noted that many of the species considered by Bergmann were, when Mayr was writing, afforded only sub-specific status! Nevertheless, since James's paper, Bergmann's rule has been examined at a variety of taxonomic levels, for example within species (Barnett, 1977; Ralls & Harvey, 1985; Yom-Tov & Nix, 1986; Geist, 1987; Graves, 1991; Smith et al., 1995, 1998; Van Voorhies, 1996, 1997; Mousseau, 1997; Partridge & Coyne, 1997), between species within genera (Gittleman, 1985; Taylor & Gotelli, 1994), between functionally related species (Geist, 1987; Cotgreave & Stockley, 1994), and between species within a range of higher taxa (Zeveloff & Boyce, 1988; Cushman et al., 1993; Barlow, 1994; McDowall, 1994; Hawkins, 1995; Hawkins & Lawton, 1995; Poulin, 1995; Poulin & Hamilton, 1995; Blackburn & Gaston, 1996a).

The problem with early stage investing is that markets can never be sized in Excel. If they could be reduced to a formula, we’d all be working at hedge funds. No, the essence of early stage investing is more instinctual.