81 Matching Annotations
  1. Last 7 days
    1. Hypothesis permet d’annoter et de commenter très simplement une page web, de manière collective

      Cet outil est en effet pratique, bien qu'il nécessite un compte. Je comprends le choix en terme pratique et en terme de référencement du projet. Mais n'aurait-il pas été intéressant de créer un site et un outil par soi-même? En tant que designer éditorial, il me parait primordial de réfléchir et se réapproprier la forme plutôt que de se conformer à des formes standardisées (ici une forme plutôt classique finalement). Une question très contemporaine je pense, quand on voit ce que sont devenues nos interfaces : les Géants laissent peu de place à la personnalisation, à l'appropriation des outils, et l'utilisateur est quelque peu infantilisé.

  2. Jun 2021
    1. 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.
    2. Also, Sandi Metz mentions this in POODR. As I recall, she also advocates wrapping bare instance variables in methods, even when they're only used internally. It helps avoid mad refactoring later.
    3. But suddenly I'm using a raw instance variable, which makes me twitch. I mean, if I needed to process has_sauce before setting at a future date, I'd potentially need to do a lot more refactoring than just overriding the accessor.
  3. May 2021
  4. Mar 2021
    1. Here's where I start to have a preference for Svelte; the two are very similar but once I got used to Svelte I found that React felt like jumping through hoops. You can't create a worker instance, it has to go in a useRef, and then you can't easily pull code out into a function without then requiring useCallback so it can be a safe dependency on useEffect. With Svelte I write code that's closer to "plain" JavaScript, whereas in React more of my code is wrapped in a React primitive.
    1. You don’t have to stick to the task interface! The [circuit interface] is a bit more clumsy, but gives you much better control over how ctx and signals are handled.
    2. The circuit interface is a bit more clumsy but it gives you unlimited power over the way the activity will be run.
  5. Feb 2021
    1. In object-oriented programming, information hiding (by way of nesting of types) reduces software development risk by shifting the code's dependency on an uncertain implementation (design decision) onto a well-defined interface. Clients of the interface perform operations purely through it so if the implementation changes, the clients do not have to change.
    1. The more important point comes from a program design perspective. Here, "programming to an interface" means focusing your design on what the code is doing, not how it does it. This is a vital distinction that pushes your design towards correctness and flexibility.
    2. My understanding of "programming to an interface" is different than what the question or the other answers suggest. Which is not to say that my understanding is correct, or that the things in the other answers aren't good ideas, just that they're not what I think of when I hear that term.
    3. Programming to an interface means that when you are presented with some programming interface (be it a class library, a set of functions, a network protocol or anything else) that you keep to using only things guaranteed by the interface. You may have knowledge about the underlying implementation (you may have written it), but you should not ever use that knowledge.
    4. If the program was important enough, Microsoft might actually go ahead and add some hack to their implementation so the the program would continue to work, but the cost of that is increased complexity (with all the ensuing problems) of the Windows code. It also makes life extra-hard for the Wine people, because they try to implement the WinAPI as well, but they can only refer to the documentation for how to do this, which leads to many programs not working as they should because they (accidentally or intentionally) rely on some implementation detail.
    5. Abstract myself from the how it does and get focus on what to do.
    6. Say you have software to keep track of your grocery list. In the 80's, this software would work against a command line and some flat files on floppy disk. Then you got a UI. Then you maybe put the list in the database. Later on it maybe moved to the cloud or mobile phones or facebook integration. If you designed your code specifically around the implementation (floppy disks and command lines) you would be ill-prepared for changes. If you designed your code around the interface (manipulating a grocery list) then the implementation is free to change.
    7. It's more like providing an Employee object rather than the set of linked tables you use to store an Employee record. Or providing an interface to iterate through songs, and not caring if those songs are shuffled, or on a CD, or streaming from the internet. They're just a sequence of songs.
  6. Oct 2020
    1. This assumes that the module has been given a well-defined, stable description (the interface in the sense of information hiding).
  7. Sep 2020
    1. Svelte will not offer a generic way to support style customizing via contextual class overrides (as we'd do it in plain HTML). Instead we'll invent something new that is entirely different. If a child component is provided and does not anticipate some contextual usage scenario (style wise) you'd need to copy it or hack around that via :global hacks.
    2. Explicit interfaces are preferable, even if it places greater demand on library authors to design both their components and their style interfaces with these things in mind.
  8. Jun 2020
  9. May 2020
  10. Apr 2020
    1. This is one possible path to take in that you simply reject the registration and ask the user to create another password. Per NIST's guidance though, do explain why the password has been rejected:
  11. Jan 2020
  12. Dec 2019
    1. TUI

      I assume this means text-based UI?? First time I've seen this term.

  13. plaintext-productivity.net plaintext-productivity.net
    1. Avoiding complicated outlining or mind-mapping software saves a bunch of mouse clicks or dreaming up complicated visualizations (it helps if you are a linear thinker).

      Hmm. I'm not sure I agree with this thought/sentiment (though it's hard to tell since it's an incomplete sentence). I think visualizations and mind-mapping software might be an even better way to go, in terms of efficiency of editing (since they are specialized for the task), enjoyment of use, etc.

      The main thing text files have going for them is flexibility, portability, client-neutrality, the ability to get started right now without researching and evaluating a zillion competing GUI app alternatives.

    1. Might be a little too low-level (even with GUIs) for some teams of users. GPG and Git both require some setup and experience in these tools, or the willingness to learn. Porting a GPG key from machine to machine is not trivial.
  14. Oct 2019
    1. Unfortunately, numerous widely-used tagless-final interfaces (like Sync, Async, LiftIO, Concurrent, Effect, and ConcurrentEffect) encourage you to code to an implementation.


  15. Sep 2019
  16. Aug 2019
  17. Jul 2019
  18. Jun 2019
  19. Mar 2019
    1. Shneiderman's eight golden rules of interface design This is a simple page that lists and briefly explains the eight golden rules of interface design. The rules are quite useful when designing interfaces and the explanation provided here is sufficient to enable the visitor to use the principles. Rating 5/5

  20. Feb 2019
    1. with either hand (one pen is positioned for each hand)

      A fully ambidextrous interface, both hands with keys and pens. Where is that done now?

    2. giving the human the minute-by-minute services of a digital computer equipped with computer-driven cathode-ray-tube display

      Sitting there with a smartphone one might smirk at the mention of a CRT display, but remember when this was written-- screens were way way off from being a "normal" interface for computer interaction

  21. Nov 2018
  22. Jun 2018
    1. One consequence of thisposition is a more radical understanding of the sense in whichmateriality is discursive (i.e., material phenomena are inseparable from theapparatuses of bodily production: matteremerges out of and includes as part of itsbeing the ongoing reconfiguring of boundaries), just as discursive practices arealways already material (i.e., they are ongoing material (re)configurings of theworld) (2003: 822).Brought back into the world oftechnology design, this intimate co-constitution ofconfigured materialities with configuring agencies clearly implies a very differentunderstanding of the ‘human-machine interface’.
    1. Raccomandazione 3.6g - Definire un modello di governance del dato e progettare automatismi organizzativi e tecnologici

      ogni applicativo gestionale in uso nelle Pubbliche Amministrazioni centrali e locali DEVE(!) fare uso di [API (Application Programming Interface)] (https://pianotriennale-ict.readthedocs.io/it/latest/search.html?check_keywords=yes&area=default&q=api) al fine di pubblicare, in modalità automatica, dati tematici aggiornati in tempo reale. Senza l'uso di API pubbliche (e documentate) non ci sarà mai un sistema di dati pubblici in formato aperto su cui poter fare riferimento per creare qualsiasi tipo di riuso costante ed utile alla società e per la nascita di nuove forme di economia. Senza API pubbliche continueranno ad esserci soltanto isolati esercizi di stile di qualche rara Pubblica Amministrazione (nel contesto nazionale) sensibile alla pubblicazione dei dati, soltanto perchè fortunatamente vede al suo interno del personale dirigente/dipendente sensibile culturalmente all'obbligo (non sanzionato in caso di non rispetto) della pubblicazione dei dati.

      Oggi (2018) l'uso delle API pubbliche nei software delle PA non va raccomandato, va imposto! Diversamente si continua a giocherellare come si fa per ora. Ma niente dati di qualità e su cui fare riferimento senza API pubbliche nei software della PA!

  23. Feb 2018
    1. la estructura ontológica del diseño está compuesta de las interrelaciones entre la herramienta, el usuario y la tarea o propósito, todos reunidos por la interfaz.
      <table style="width:100%"> <tbody><tr> <td> </td> <td> </td> </tr> </tbody></table>
  24. Dec 2017
    1. A mental map (or cognitive map) is our mental representation of a place. It includes features we consider important, and is likely to exclude features we consider unimportant.

      (Urban planner Kevin Lynch, early 1960s)<br> Elements of mental maps

      • paths
      • edges - boundaries and endings
      • nodes - focal points like squares and junctions
      • districts
      • landmarks

      Modern maps could use augmented and virtual reality to help clarify those elements, making a place easier to navigate and use. But they can also add useless noise that makes the place seem more confusing than it actually is.

  25. May 2017
    1. Neither Apple nor Microsoft really captured the essence of what made the Smalltalk system powerful. They used it as a model to make computers more accessible, but they left out the aspect of letting people bend the system to their will, to customize it to be just what they want. Their systems were really an object-oriented facade over a traditional, non-object-oriented system. They lacked a consistent metaphore of everything being an object. The web has been even more stultifying in this regard (I mean the web interface), though Firefox has helped some, so I hear, with the concept of browser extensions.
  26. Mar 2017
    1. Jessica Helfand in her essay The Dematerialism of Screen Space (2001) critiques the phenomenon of design practise being led by developments in software engineering. She argues that designers should take the initiative: “design must submit to a series of commands and regulations as rigourous as those that once defined Swiss typography. Aesthetic innovation, if it indeed exists at all, occurs within ridiculously preordained parameters: a new plug-in, a modified code, the capacity to make picture and words ‘flash’ with a mouse in a non-sensical little dance. We are all little filmmakers, directing on a pathetically small screen – yet broadcasting to a potentially infinite audience. This in itself is conflicting (not to mention corrupting), but more importantly, what are we making? What are we inventing? What are we saying that has not been said before?” Helfand here is referring to the web, but her argument applies equally well to designing tablet publications. Designers of book and magazine apps should be asking themselves those last three questions. Since tablet publishing conventions are in the process of being formed (like child invention), we have a unique opportunity right now to influence their direction.
    2. Some key themes arise from the two NNG reports on iPad usability: App designers should ensure perceived affordances / discoverability There is a lack of consistency between apps, lots of ‘wacky’ interaction methods. Designers should draw upon existing conventions (either OS or web) or users won’t know what to do. These are practical interaction design observations, but from a particular perspective, that of perceptual psychology. These conclusions are arrived at through a linear, rather than lateral process. By giving weight to building upon existing convention, because they are familiar to the user, there is a danger that genuinely new ideas (and the kind of ambition called for by Victor Bret) within tablet design will be suppressed. Kay’s vision of the Dynabook came from lateral thinking, and thinking about how children learn. Shouldn’t the items that we design for this device be generated in the same way?

      The idea of lateral thinking here is the key one. Can informatics be designed by nurturing lateral thinking? That seems related with the Jonas flopology

    3. The document argues that the use of illusionary surfaces and objects will lead to a more intuitive and pleasurable experience for the user. It also, yet again, looks to prior conventions for solutions rather than starting afresh.
  27. Nov 2016
    1. Every theorem of mathematics, every significant result of science, is a challenge to our imagination as interface designers. Can we find ways of expressing these principles in an interface? What new objects and new operations does a principle suggest? What a priori surprising relationship between those objects and operations are revealed by the principle? Can we find interfaces which vividly reveal those relationships, preferably in a way that is unique to the phenomenon being studied?
    2. Speech, writing, math notation, various kinds of graphs, and musical notation are all examples of cognitive technologies. They are tools that help us think, and they can become part of the way we think -- and change the way we think.

      Computer interfaces can be cognitive technologies. To whatever degree an interface reflects a set of ideas or methods of working, mastering the interface provides mastery of those ideas or methods.

      Experts often have ways of thinking that they rarely share with others, for various reasons. Sometimes they aren't fully aware of their thought processes. The thoughts may be difficult to convey in speech or print. The thoughts may seem sloppy compared to traditional formal explanations.

      These thought processes often involve:

      • minimal canonical examples - simple models
      • heuristics for rapid reasoning about what might work

      Nielsen considers turning such thought processes into (computer) interfaces. "Every theorem of mathematics, every significant result of science, is a challenge to our imagination as interface designers. Can we find ways of expressing these principles in an interface? What new objects and operations does a principle suggest?"

  28. Aug 2016
    1. les interfaces ne sont nullement régulées par cette structure de regard, mais bien par une structure d'action.

      interfaces selon Galloway. Par contre attention, interfaces n'est pas équivalent à l'espace numérique.

  29. Apr 2016
  30. Feb 2016
    1. A study of typing strategies among both touch-typists and self-taught typists.

      http://10fastfingers.com/typing-test/english<br> Test your typing speed by typing a series of random words for one minute.

  31. Nov 2015
    1. There is a lot of evidence that quite subtle changes to user interfaces can have dramatic effects on how the interfaces are used. For example, the size of a search box or the text that accompanies it can considerably influence the queries that people submit.

      -- David Elsweller

    2. The whole gendered usage of hearts seems to have escaped Twitter. So does the fact that people fave (with stars) in complex ways - they are bookmarks, they are likes, they are nods of the head. But they are not indicators of love. I feel very weird loving tweets by random men I've only just started a conversation with. Not that there's anything wrong with feminine. But women - and men, in their own ways - are well-aware of how feminized visual signals get read by others, and in an identity space like Twitter, I suspect that will really minimize usage. Or at least until we all get used to it.

      -- Bonnie Stewart

  32. Sep 2015
    1. MyInterfaceImpl

      I believe that a better name would be StandardOutputMyInterface. The name of the implementation should describe the character of the implementation, which in this case is output to the standard output stream. I consider simply appending Impl to the interface name a (common) bad habit.

  33. Jul 2015
    1. The on-line annotations were also more likely to be anchored in complete sentences.

      This seems odd. Maybe the interface in some way pushed them toward this? For instance, I sometimes think the way that Hypothesis shows the quote in the annotation card severs it from its context in such a way as to make it seem out of place when highlighting just that portion seemed fine inline.

  34. Mar 2015
    1. The book or physical instance, then, is one of many levels of address.

      Definition for manifestations of the text. Maybe useful in discussing interface as the encountered work?

    2. Because a text can be queried at the level of single words and then related to other texts at the same level of abstraction: the table of all possible words could be defined as the aggregate of points of address at a given level of abstraction (the word, as in Google’s new n-gram corpus).

      I like this idea of defining a level of text and than comparing across texts—would like to see more of this at the level of code and interface design and tool design decisions (e.g. how do different digital archives deal with making sure visitors see more than the alphabetically or chronologically first few items in the collection? how do different DH sites allow people to comment? what is the difference among moderation or voting systems?).

  35. Nov 2014
    1. the interface currently works quite slowly, much slower than regular web content.

      This may be browser-side speed. Most of the heavy lifting of the application is done in the client.

  36. Sep 2013