38 Matching Annotations
  1. Oct 2019
    1. Meanwhile at Microsoft's GitHub, employees at both companies have objected to GitHub's business with ICE, not to mention Microsoft's government contracts. Employees at Amazon have also urged the company not to sell its facial recognition technology to police and the military.
  2. Aug 2019
    1. With now more than 3000 modules, there are huge gaps in the quality of things you find in the npm registry. But more often than not, it's easy to find a module that is really close to what you need, except if it wasn't for that one bug or missing feature.
  3. Jul 2019
  4. Jun 2019
  5. Apr 2019
    1. China’s tech sector is notorious for treating workers like machines, with extremely long working hours being the norm. The phrase 996 refers to 9am - 9pm, 6 days per week, and is an unspoken rule in a lot of Chinese tech companies. The CEO of Youzan, a large Chinese e-commerce company, seemingly didn’t get the memo about keeping 996 as an “unspoken” rule, and surprised his employees at their 2019 yearly company party by telling them Youzan is officially switching to 996.
  6. Mar 2019
  7. Oct 2018
  8. Sep 2018
  9. Apr 2018
  10. Mar 2018
    1. if (app.metadata && app.metadata.has('dc:title') && app.metadata.get('dc:title') !== 'Untitled') { title = app.metadata.get('dc:title'); }

      the empty dc:title should also be considered as Untitled

  11. Dec 2017
    1. describe each dataset carefully and as completely as possible with metadata
    2. DOI
    3. contains complementary information of another dataset, this must be specified in the (meta)data

      for software: inclusion of external libraryies or dependencies is usually specified in header files, on top of code files, in DESCRIPTION (R package), by import or :: statements.

      Since source code can be indexed like text, does it have to be repeated in metadata? GitHub & other services seem to already do that: github.com/blog/2470

  12. Oct 2017
  13. Aug 2017
  14. May 2017
  15. Jan 2017
    1. Intuitively, an explanation is a local linear approximation of the model's behaviour

      LIME and Explanation

      Questions: Is LIME really resemble human's approach to understand black box of machine learning?

  16. Jun 2016
  17. Mar 2016
    1. Client<->Server API - defines how Matrix compatible clients communicate with Matrix homeservers. Server<->Server API - defines how Matrix homeservers exchange messages and synchronise history with each other.

      Given the data model (which allows merges) forkdb could be a close candidate to substitute a Client <-> Client API (also called peer to peer).

      Play with it.

  18. Sep 2015
  19. Aug 2015
    1. Check out the code on GitHub.

      Notenotenote. Notenote. Cool.

  20. Jul 2015
  21. Jun 2015
  22. Apr 2015
    1. Do I own my content on The Grid? Yes, you own your content. The engine AutoDesigns your site, publishes it, and stores it on Github. Your source content will live in a Github repository that you can access and download anytime.

      Is access private/public?

    1. The blog post in which Ben Balter proposes that term was unpublished when I read it. But since the blog is hosted on a public GitHub repository I could not only read the post in draft form but also follow the discussion with invited reviewers and observe how that discussion influenced the draft.

      With Hypothesis this kind of thing becomes available for /any web page/.

  23. Mar 2015
  24. Nov 2014
  25. Feb 2014
    1. Github As The Central Presence, Definition, Configuration, And Source Code For Your API Posted on 02-05-2014 It is easy to think of Github as a central repository for your open source code—most developers understand that. I have written before about the many ways to use Github as part of your API management strategy, but in the last few months I'm really seeing Github playing more of a central role in the overall lifecycle of an API.