- Mar 2021
-
twitter.com twitter.com
-
ReconfigBehSci on Twitter. (2020). Twitter. Retrieved 27 February 2021, from https://twitter.com/SciBeh/status/1339855911796543488
-
-
github.com github.comd3/d31
-
Microlibraries are easier to understand, develop and test. They make it easier for new people to get involved and contribute. They reduce the distinction between a “core module” and a “plugin”, and increase the pace of development in D3 features.
-
-
stackoverflow.com stackoverflow.com
-
Semantically this is wrong.
-
-
stackoverflow.com stackoverflow.com
-
Usually when people are talking about code being semantically correct, they're referring to the code that accurately describes something.
-
HTML elements have meaning. "Semantically correct" means that your elements mean what they are supposed to.
-
Semantically correct usage of elements means that you use them for what they are meant to be used for.
-
It means that you're calling something what it actually is.
-
The classic example is that if something is a table, it should contain rows and columns of data. To use that for layout is semantically incorrect - you're saying "this is a table" when it's not.
-
-
Fits the ideal behind HTML HTML stands for "HyperText Markup Language"; its purpose is to mark up, or label, your content. The more accurately you mark it up, the better. New elements are being introduced in HTML5 to more accurately label common web page parts, such as headers and footers.
Tags
- explicit meaning
- explanation
- calling something what it actually is (semantic labeling)
- definition
- simple explanation
- good explanation
- semantically correct
- semantic markup
- be specific
- fundamental principles/paradigm of the Web
- use meaningful names (programming)
- good example
- example
Annotators
URL
-
-
css-tricks.com css-tricks.com
-
You don’t need to do any tricky cursor stuff, because it’s all semantically wired up already.
-
always use real <label for="correct_input"> elements. Just that alone is a UX consideration all too many forms fail on
-
- Feb 2021
-
github.com github.com
-
now that I realize how easy it is to just manually include this in my app: <%= javascript_include_tag 'xray', nonce: true if Rails.env.development? %> I regret even wasting my time getting it to automatically look for and add a nonce to the auto-injected xray.js script
Tags
- removing legacy/deprecated things
- fix design/API mistakes as early as you can (since it will be more difficult to correct it and make a breaking change later)
- regret
- removing feature that is more trouble than it's worth (not worth the effort to continue to maintain / fix bugs caused by keeping it)
- removing features to simplify implementation
- wasted effort
Annotators
URL
-
-
www.theregister.com www.theregister.com
-
-
Allowlist, not whitelist. Blocklist, not blacklist. Goodbye, wtf. Microsoft scans Chromium code, lops off offensive words
-
a suggestion by Microsoft to “cleanup of potentially offensive terms in codebase” aims to rid the software blueprints of language such as whitelist (change to allowlist), blacklist (change to blocklist), “offensive terms using ‘wtf’ as protocol messages,” and other infelicities.
-
In May, Microsoft announced AI features in Word that, among other features, will emit “advice on more concise and inclusive language such as ‘police officer’ instead of ‘policeman.’"
-
-
trailblazer.to trailblazer.to
-
The new 2.1 version comes with a few necessary but reasonable changes in method signatures. As painful as that might sound to your Rails-spoiled ears, we preferred to fix design mistakes now before dragging them on forever.
-
The new call API is much more consistent and takes away another thing we kept explaining to new users - an indicator for a flawed API.
Tags
- fix design/API mistakes as early as you can (since it will be more difficult to correct it and make a breaking change later)
- pointing out gaps/downsides/cons in competition/alternatives
- better late than never
- if it's incorrect; fix it
- learn from your mistakes
- do it right/well the first time because it may be too hard to clean up/fix later if you don't
Annotators
URL
-
-
softwareengineering.stackexchange.com softwareengineering.stackexchange.com
-
This is not correct. Or at least, it is not entirely correct.
-
- Jan 2021
-
github.com github.com
-
The code is far simpler and easier to understand/verify
-
-
www.americanpressinstitute.org www.americanpressinstitute.org
-
The purpose of news is to inform, educate, and give us understanding and knowledge of what is going on in the world. It helps us to keep up to date with issues so we are in the know and fully aware of events taking place.
-
-
stackoverflow.com stackoverflow.com
-
text-decoration is more 'correct' because it is the 'real' CSS property meant for underlining text.
-
- Oct 2020
-
english.stackexchange.com english.stackexchange.com
-
Logistically speaking, I suppose "depender" and "dependee" would be more accurate, though neither of those are proper english words as far as I know.
-
In the context of software engineering, I've always used "dependent" and "dependee".
-
-
github.com github.com
-
virtual-dom exposes a set of objects designed for representing DOM nodes. A "Document Object Model Model" might seem like a strange term, but it is exactly that. It's a native JavaScript tree structure that represents a native DOM node tree.
-
- Sep 2020
-
www.changelogs.md www.changelogs.md
-
Move svelte into dependencies, as it was accidentally stuck in peerDependencies
"accidentally stuck in": well, not really accidentally; it's in the change log so I assume it was intentional
-
- Aug 2020
-
meta.stackexchange.com meta.stackexchange.com
-
Can't upvote this enough. It is highly irritating to see language destroyed (and we wonder why kids bastardize the language..).
Tags
- even if majority makes a mistake; it doesn't make it correct
- example of: using incorrect terms
- hoping/trying to convince others that your view/opinion/way is right by consistently sticking to it despite many being ignorant/mistaken/unaware/holding different opinion
- combating widespread incorrectness/misconception by consistently doing it correctly
- correctness
Annotators
URL
-
-
english.stackexchange.com english.stackexchange.com
-
my point is that using "into" in such a case is just as incorrect as using "inas" would be. The fact that people make mistakes doesn't change this.
"Log in" is the only correct way to spell the verb, and the only way to be consistent with 1000s of other phrasal verbs that are spelled with a space in them.
We don't need nor want an exception to the general rule just for "login" just because so many people have made that mistake.
-
- Feb 2020
-
loadimpact.com loadimpact.com
-
It is also good practice to make sure that your load testing is functionally correct. Both the performance and functional goals can be codified using thresholds and checks (like asserts).
-
- Feb 2019
-
www.literacyworldwide.org www.literacyworldwide.org
-
These discussions can be fraught with power dynamics, resulting in controversial issues appearing unbalanced as more powerful authors block alternative viewpoints.
Students need to know which information is going to be unbiased and true. There are MANY internet sources that use shock value information or biased information rather than presenting corect information.
-
- Jan 2018
-
hunabku.pbworks.com hunabku.pbworks.com
- Oct 2013
-
rhetoric.eserver.org rhetoric.eserver.org
-
The foundation of good style is correctness of language, which falls under five heads. (1) First, the proper use of connecting words, and the arrangement of them in the natural sequence which some of them require. For instance, the connective "men" (e.g. ego men) requires the correlative "de" (e.g. o de). The answering word must be brought in before the first has been forgotten, and not be widely separated from it; nor, except in the few cases where this is appropriate, is another connective to be introduced before the one required. Consider the sentence, "But as soon as he told me (for Cleon had come begging and praying), took them along and set out." In this sentence many connecting words are inserted in front of the one required to complete the sense; and if there is a long interval before "set out," the result is obscurity. One merit, then, of good style lies in the right use of connecting words. (2) The second lies in calling things by their own special names and not by vague general ones. (3) The third is to avoid ambiguities; unless, indeed, you definitely desire to be ambiguous, as those do who have nothing to say but are pretending to mean something. Such people are apt to put that sort of thing into verse.
What is really important is clarity.
Tags
Annotators
URL
-