48 Matching Annotations
  1. Last 7 days
  2. Mar 2020
    1. If you’re age 60 and up or at high-risk for coronavirus (COVID-19), we offer new services to help you get the medication you need.

      This is hideous formatting. Walmart web techs need to make this much larger and more legible since we older folk can't always read so well.

  3. Dec 2019
    1. The beauty of using Google Sheets or another spreadsheet tool for your to do list is that you have so many formatting options. Sometimes I change the color of a cell to indicate that it's high priority. Other times I bold it. And other times I just write IMPORTANT in front of it. Whatever works. But if you like to be more consistent, you can choose colors to indicate specific things: priority, level of effort, type of tasks, or anything else you want to be able to see at a glance. For example, I always highlight a row in blue if I'm going to be out of the office. That way, I don't overschedule the week. And I highlight a row in red if it's a non-negotiable—something I have to do the day it's scheduled because of an external deadline. And because you have text formatting options—which many to do lists don't—you can make your formatting as granular as you'd like. Bold certain types of tasks, italicize others, or even add a border around cells. Whatever stands out to you visually, go with that

      Free-form text formatting has its pros and its cons.

      Pros: It's very flexible. Since it's free-form, you can ad hoc make any new system you want, and designate, say, bold or blue to mean whatever you want it to.

      Cons: No way to enforce the rules you made for yourself. In fact, it may be hard to even remember the rules you made for yourself. You may have to create a key/legend for yourself to be safe.

      This is like why I dislike software where the only way to change font is to manually choose a font. I like it better when you can define a style/class (I think Word can do this, IIRC; and obviously HTML/CSS can), choose how that class should be formatted (font, etc.) and then can style any text with that class. This is a better way to go because classes have semantic meaning. This is the same dilemma I remember facing ~10 years ago when WYM editor was fairly new: It let you select use semantic classes/elements, whereas WYSIWIG editors were the norm (probably still are) and only let you do manual free-form formatting, with no semantic meaning conveyed.

    1. // reduce() without initialValue [ { x: 22 }, { x: 42 } ].reduce( maxCallback ); // 42 [ { x: 22 } ].reduce( maxCallback ); // { x: 22 } [ ].reduce( maxCallback ); // TypeError // map/reduce; better solution, also works for empty or larger arrays [ { x: 22 }, { x: 42 } ].map( el => el.x ) .reduce( maxCallback2, -Infinity );
    1. First sighting. First time I've seen a literal, non-whitespace character (┊) used to show indentation. Looks pretty nice. But breaks copy-and-pastability.

  4. Nov 2019
    1. import { NgModule } from '@angular/core'; import { CommonModule } from '@angular/common'; import { FormsModule } from '@angular/forms'; import { MaterialModule } from '@angular/material'; import { MyInterface } from './my.interface'; import { MyService } from './my.service'; @NgModule({ imports: [ CommonModule, FormsModule, MaterialModule.forRoot() ], declarations: [ MyInterface],//<- this is causing the message exports: [ MyInterface], providers: [ MyService ] }) export class MyModule { }
  5. Sep 2019
  6. Aug 2019
    1. Project Descriptio

      Don't waste space on whitespace, but keep your proposal readable. Double check on the formatting slack they they give you, but head your sections with bold, indented text but don't break the line afterwards. Give a few spaces or a colon and head into the paragraph

    2. 1)

      Don't be shy about numbering arguments in-paragraph, especially in the intellectual merit section. Listing several ideas in sequence makes your writing feel 'blippy' - moving too abruptly. By explicitly offsetting with numbers you implicitly prepare your reader for rapid topic switches. They also take up less space than "this, next, then, last, etc."

    3. I propose to developphonetic discrimination in mice as a model for speech perception. I will thendirectly testthe predictions made by competing neurolinguisticmodels

      End your introduction with a one-sentence description of your project. Use italics to make in-paragraph text easy for your reviewer to pick out.

    1. Participant data: can help you determine if you are actually reaching the people you intend to. Focus groups: how did people experience the program? How could you improve it from the participant perspective? Satisfaction surveys: did participants get what they wanted from the program? Staff perception data: How did the program go for staff? Were expectations realistic? What did they see in terms of qualitative changes for participants? Program adherence monitoring: how well did you follow your program plans?

      Can we revise the text color or format so that this section is easier to read and visually more manageable? Each beginning term, for example, could be formatted in this way:

      "Participant data: Can help you determine if you're actually reaching the people you intend to reach."

    1. Places a greater emphasis on determining unit of analysis

      In this explanatory subsection, can we perhaps format the text color or font so that the main point in each numbered section stands out visually? For example, a revised format might look something like this:

      "1. Places a greater emphasis on determining unit of analysis. When conducting a content analysis, you'll want to first determine what your unit of analysis may be. . . ."

    1. These two categories exist as opposite extremes on a continuum.

      I would suggest that we begin a new paragraph with the sentence "These two categories..."

      We may also want to very briefly reiterate the relevant topics. For example, the first sentence of the new paragraph might read something like "Idiographic and nomothetic research represent two different research categories existing at opposite extremes on a continuum."

    2. [2.20]

      just an observation - we may want to round the estimated reading times to the nearest half-minute. I think there's some potential for confusion among readers interpreting an estimated reading time such as "6.57" - this estimate is so specific that it might not seem at first glance like an estimated reading time. Rounding that number and changing the format - i,e., "6.57" [current] to "7 mins" [suggested] - might help students clearly understand what we are trying to communicate. I do think the estimated reading times are potentially very helpful for readers, though.

  7. Jun 2019
    1. Turn on the option to use github pages with the docs folder Github should now display a url where you can view the web-book.

      Numbering on these lines should be 22 and 23, respectively

    2. 21.

      This should start on a new line

  8. Aug 2018
    1. Compared to paper artifacts such as laboratory notebooks, computer files do not offer a proper structure to manage temporal and evolutive data.

      Don't agree with this statement at all. Blogs are nothing but linear chronological structures.

    2. Paper holds temporal properties which are not yet integrated in computer.

      Also, weirdly overstated. There were plenty of products and meta data even in 2009 that was available to determine provenance and iteration.

    3. Blog tools are designed as publishing tools; they do not support iterative thinking the way paper notebooks do.

      This statement seems to be fixed in traditional, old-school blogging (one idea = one post) and doesn't consider other forms that adapt/extend other ways to represent temporality/change/iteration.

      As one example, live-blogging techniques which incorporate rapid updating of new information through chronological mini-posts, manual time-stamping of new material, etc. Also. plug-ins that allow annotation, image uploads, Google Docs with version control, etc.

      Also, WP post/page formatting options with HTML, typography, etc., can augment re-ordering of information to designate change.

  9. Feb 2018
    1. Abhráin

      The formatting of e-books on Internet Archive does not allow hypothesis.is users to annotate the books’ text. In annotating Hyde’s Love Songs of Connacht for the EN6009 Annotate-A-Thon, I have attached annotations to the text beneath the scanned images. Extracts and corresponding page numbers are placed at the beginning of each annotation, in order to properly contextualize my responses.

  10. Apr 2017
    1. Measles has doomsday capabilities.

      bold to strengthen the statement to highlight danger

    2. Anti-vaxxers choose to still view measles this way, as another childhood illness similar to chickenpox.

      using boldface to summarise view of conspiracists

  11. Mar 2017
  12. Feb 2017
    1. actions. Writing and speech are actions — and powerful ones at that.” – Mike Sturm, Sticks and Stones: On the under-appreciated Power of Words

      Formatting.

  13. Nov 2016
    1. “Advisory Neighborhood Commission 5E.” N.p., n.d. Web. 18 Nov. 2016. Barnard, Anne. “Beirut, Also the Site of Deadly Attacks, Feels Forgotten.” The New York Times 15 Nov. 2015. NYTimes.com. Web. 16 Nov. 2016.

      Double space this or try to do something to make more readable.

  14. Aug 2016
  15. Jun 2016
  16. www.glottotopia.org www.glottotopia.org
    1. One

      Remove new paragraph here.

    2. 5

      Where is the footnote mark in the body of the text?

    3. Is this wrapping from the second line? It's hard to read with only one line wrapping, so adjust if possible.

    4. the night (before I go hunting)Ialreadyhave a plan

      If this is a complete sentence - and it seems like it is - then both Malay and translation should have sentence punctuation. Same for other examples. If the Malay isn't a complete sentence, adjust the translation to make that clear.

    5. 19

      Use same punctuation in first line of example as in third.

    6. 15

      First line of example doesn't have same punctuation as the translation line.

    7. 10

      First line of example doesn't have same punctuation as the translation line.

    8. (9)

      First line of example doesn't have same punctuation as the translation line.

    9. Possessive marking withpu‘poss

      I would move this whole part of the table to table 9.3, which would group all of the punya examples together in table 9.3 and the pu examples in table 9.3. As it is right now, it's not clear why you'd split the tables up the way you have.

    10. 0

      Where is the footnote mark in the text body?

    11. -

      Use en-dash.

    12. -

      Use en-dash.

    13. -

      No spaces. Use en-dash.

    14. (5a-5d,

      No spaces. Use en-dash.

    15. (5j-5l)

      Should be (5j-5l) without spaces, but make the - an en-dash instead.

    16. n(hum)punyanp(inal)

      Is this supposed to be on the line above, with "mama..." on the next line? Same for all examples in (5). If not, I'm not following what structure you're trying to point out here.

    17. (1)

      Don't split an example across two pages.