57 Matching Annotations
  1. Sep 2023
    1. I'd even go as far as saying each_with_object is often less readable than using a captured variable.

      elaborate? what is a captured variable? I assume he means the val = 0 from outside the scope of the block, which was "captured" in the closure.

  2. May 2023
    1. ISO 8601 specifies the use of uppercase letter T to separate the date and time. PostgreSQL accepts that format on input, but on output it uses a space rather than T, as shown above. This is for readability and for consistency with RFC 3339 as well as some other database systems.
  3. Mar 2023
    1. It was easier said than done to know when to add punctuation like / or .

      Example of someone who doesn't seem to understand that the / or . are primarily for readability.

  4. Jan 2023
    1. The popular recommendation is that there should be between 40 and 75 characters per line. The findings of multiple studies conclude that "short line lengths are easier to read". Regarding learning and information retention: "Subjects reading the narrow paragraphs had better retention than those reading the wide paragraphs"
    1. Research has shown that limiting the width of longform text leads to a more comfortable reading experience, and better retention of the content itself.
  5. Nov 2022
  6. Oct 2022
    1. https://youtu.be/ILuSxUYYjMs

      Luhmann zettelkasten origin myth at 165 second mark

      A short outline of several numbering schemes (essentially all decimal in nature) for zettelkasten including: - Luhmann's numbering - Bob Doto - Scott Scheper - Dan Allosso - Forrest Perry

      A little light on the "why", though it does get location as a primary focus. Misses the idea of density and branching. Touches on but broadly misses the arbitrariness of using the comma, period, or slash which functions primarily for readability.

  7. Sep 2022
    1. When I ask people about any part of their code, they usually say it's easy to understand. But when I open the code, it takes me a couple hours slapping to my face to keep myself alive to understand just a little part of their code.
    2. But how much readability are enough?
    3. they’re just too familiar with the code to think it's complicated
    1. This code is much easier to understand as it do not add levels of indentation and follows the principle where the 0 indentation level is the principal path of the application where other paths are exceptions or rare cases.
    1. use logos wellthroughout, provided with credible ethos, they fail to have strong pathos within their writing.

      Aristotle's rhetorical appeals are essence to any convincing paper but ideally I would like to see you elucidate on each of these three by possibly spreading them throughout. For instance, you could use the next annotated paragraph to display Ethos.

    2. Satisfying sex life hasbeen found to be important for health and well-being, regardless of age.

      Consider A satisfying sex life is important for health and well-being, regardless of age for the diminution of verbiage and the missing determiner.

    3. “The positive relationship between sexual quality of life and aging wasstrongest in the context of good-quality romantic relationships, where sexual exploration anda focus on partners’ pleasure is more likely to take place” (Forbes, Eaton, Kruger 2022pg.186). And “This is great news, as a satisfying sex life has been found to be important forhealth and well-being, regardless of age (Forbes, Eaton, Kruger 2022 pg.187). The key wordsthat draw you to the reading withing these two sentences are “positive” and “this is greatnews”

      I feel like there are four paragraph long quotes relatively close together. I thought this analysis was internalizing the work and putting the rhetoric into your own words, if not I need some quotes lol.

    4. Forbes, Eaton, Kruger 2022 pg.186). Miri, Nicholas, and Robert stated

      Great job sourcing the material you're referencing but I believe in redundancy: the audience knows what you're analyzing so you should be able to just state the page numbers without repeating the author's names.



  8. Feb 2022
  9. Sep 2021
    1. Code that is needed to create the output and the output itself is hard to read because of all the workarounds we have to use, especially around shadowed variables and control flow
  10. Jun 2021
    1. Note that every call of sample(1:6, 3, replace = T) gives a different outcome since we draw with replacement at random. To allow you to reproduce the results of computations that involve random numbers, we will used set.seed() to set R’s random number generator to a specific state. You should check

      In general I really like the online approach etc! really appreciated. I am now actively using and studying through this book. I think what would be super useful is to show some kind of equivalent of page numbers. Going back and forth between sections and scrolling up and down really makes me lose track of where i was.

  11. May 2021
    1. Those thoughts should beseparated from each other with blank lines.

      Only use blank lines to separate different thoughts. Don't use it everywhere arbitrarily. Especially, don't use it for every line code.

  12. Apr 2021
    1. “Who cares? Let’s just go with the style-guide” — to which my response is that caring about the details is in the heart of much of our doings. Yes, this is not a major issue; def self.method is not even a code smell. Actually, that whole debate is on the verge of being incidental. Yet the learning process and the gained knowledge involved in understanding each choice is alone worth the discussion. Furthermore, I believe that the class << self notation echoes a better, more stable understanding of Ruby and Object Orientation in Ruby. Lastly, remember that style-guides may change or be altered (carefully, though!).
  13. Mar 2021
  14. Feb 2021
    1. The fact we’re using ActiveRecord (or something looking like it) doesn’t mean Trailblazer only works with Rails! Most people are familiar with its API, so we chose to use “ActiveRecord” in this tutorial.
  15. Dec 2020
  16. Nov 2020
    1. One last bonus: CSS variables can be written in a way that makes it easier for human programmers to understand. If you just see hex code #93e9be, you won’t know what color it produces, while --brand-green makes clear the purpose of the variable.
    1. Similarly problematic is the “cancel culture,” where people attempt to expunge anyone with whom they do not perfectly agree, rather than remain focused on those who profit from discrimination and injustice.

      This is very important and easy to understand

  17. Oct 2020
    1. A reasonably clean alternative would be to map a function over the array and use destructuring in the each loop: {#each [1, 2, 3, 4].map(n => ({ n, sqr_n: n * n })) as { n, sqr_n }} {sqr_n} {sqr_n / 2}<br> {/each}
  18. Sep 2020
    1. Why the obfuscation of remaining to r and callbacks to c? This is fine for function-local variables but in this instance makes the code significantly harder to reason about? There is no notion of what c and r mean.
    1. I'm certainly not claiming that we should use clever tricks to scrunch our code into the most compact form possible at the expense of readability. Nor am I claiming that reducing lines of code is necessarily a worthwhile goal, since it encourages turning readable code like this...
    1. Personally for me, this is incredibly hard to read. Regex everywhere, nested objects with different rules and configurations that are very intuitive, multiple loaders that resolve backwards, built in loaders having obscure issues that require using third party loaders in between, separation of plugins and loaders, and so on.
  19. Aug 2020
  20. Jun 2020
    1. a technique that enable a test suite to perform as well as using fixtures (or better if you're running just a few tests from the suite) and read as good as you are used to when using factories
  21. Feb 2020
    1. The lack of a dynamic scripting language is annoying, though Tsung XML scenarios (again, just like JMeter) can include things like loops and if-statements, so it is actually possible to write all sorts of complicated user scenario “code.” The functionality is there, but the usability is not: few developers like “programming” in XML.
    1. We believe load test scripts should be plain code to get all the benefits of version control, as opposed to say unreadable and tool generated XML.

      Saw another comment lamenting the use of ugly/unreasonable XML files:


      Tired of using the JMeter GUI or looking at hairy XML files?

  22. Jan 2020
    1. An online tool for calculating readability Some word processing software has the Flesch-Kincaid formula built in. Or you can use this online tool to calculate the reading level of a particular passage:


  23. May 2019
  24. Oct 2017
    1. The transformation of a page by Readability is pretty dramatic, and its use can lead to a focused conversation in the classroom about what has been removed, and why, and what has remained, and why. This forced awareness of the construction of a web page is valuable knowledge for young users of the web.

      This is an important thing to think about because if a student is always using "readability" then are they really learning how to read online. This sounds like a really helpful tool for students with OCD or ADHD.

  25. Nov 2016
    1. When you agree to the Terms of Use, you can continue with the registration process.

      The text edit for this Terms of Use is testing at a Grade Level of 10, as a whole. However, individual sentences test lower 6-8). The multi-syllabic words and unrecognized words (eg-Movember, TrueNTH) add to the increase in reading level. But all in all, I think the edit may read a little clearer.