42 Matching Annotations
  1. Jul 2019
    1. A tool to help determine weights (or a feature of a creditmap tool) seems most likely to be successful. Such a tool would likely have provide simultaneous views of the credit map and weights: one that allows a detailed view of any particular contriponent and its weight, and the other that provides a view (perhaps graphical) of the entire creditmap and weights.

      Great idea! Doesn't seem to exist yet, but it should also take in account the quality of each contribution (a few high-quality contributions can be more important than many low-quality contributions).

    2. The value of transitive credit is in measuring the indirect contributions to a product, which today are not quantitatively captured

      Should contributions to a product really be quantitatively captured? Wouldn't that lead to the same dead-end as with citation in scientific publication?

    3. how the credit map for a product A, which is used by a product B, feeds into the credit map for product B

      Transitive credit's 3rd element: transitive nature

    4. Any product should list all authors (as currently listed as authors of a paper), all contributors (as currently listed in the acknowledgements of a paper) and all component products that have been used, including both publications and other products such as software and data (as currently either cited, acknowledged, or not included in a paper).

      Transitive credit's 1st element: credit (called "contriponent" - combination of contributors and components)

    5. Methods for doing this weighting, whether using a taxonomy or a more traditional list of authors, and analysis of these methods and their impact would likely be developed if this overall idea moves forward.

      Transitive credit's 2nd element: weight

  2. Apr 2019
  3. Mar 2019
    1. This is a list of different types of mobile learning software. It seems that different categories are included, such as LMSs. I can't evaluate the products but I will note that this list would be far more helpful if they clarified what each of the software tools is supposed to do. At this point, I do not have competing lists, so I will include it for now. rating 1/5

    1. This is specific to Articulate Rise 360 (a rapid development tool) and features brief posts that keep the reader up to date on software changes, which are made frequently. Only a portion of each comment is visible on the main page (just as only a portion of an email is visible without clicking the email) but the subject heading is usually sufficient to describe the content of the post. rating 3/5

    1. This is associated with the e-learning development tool "Articulate Storyline." There are frequent blog posts and they are not limited to or exclusive to the Articulate products. Posts are brief and not all of the content will be new, but there are worthwhile tips to be had and they combine theory (not to the extent that an academic would) with practice. rating 3/5

  4. Feb 2019
    1. Guide to Select a Software Development Company

      The difficulty with standard software products is that there is no one product to meet all business requirements, which is why business partners have begun looking for Guide to Select a Software Development Company which provides the custom software development services instead.

  5. Jan 2019
    1. AI Robots will be replacing the White Collar Jobs by 6% until 2021

      AI software and the chatbots will be included in the current technologies and have automated with the robotic system. They will have given rights to access calendars, email accounts, browsing history, playlists, past purchases, and media viewing history. 6% is the huge number in the world as people would be seen struggling in finding the jobs. But there are benefits also as your work would have done easily and speedily

    1. As was hinted at from the star

      This is when “the other shoe dropped”. They planned this all along (since 2012). Hidden in plain sight was a more subtle strategy than people might have imagined.

    2. The Grid is based around ideas familiar to Bitwig Studio

      The continuity between these new modular features and the rest of the DAW’s workflow probably has unexpected consequences. Before getting information about BWS3, one might have thought that the “Native Modular System” promised since the first version might still be an add-on. What the marketing copy around this “killer feature” makes clear, it’s the result of a very deliberate process from the start and it’ll make for a qualitatively different workflow.

    1. Increase Your ROI With Quality Software Development Services

      Every business firm wishes to generate high profits. This makes them go for IT services which will increase their adaptability and generate more profit. Enterprises invest a lot of money for software solutions and expect to get a good return with them. In order to increase their profits and add to their financial pool, this is the most applicable option available top them. A business requires a lot of processes to function in the right manner every day. All of this cannot be done with just manual power and thus requires a collaboration of software and manual assistance.

  6. May 2018
    1. You can not only apply it to classes, but also to software components and microservices.

      The principle can also be applied to source code files.

  7. Dec 2017
  8. Nov 2017
  9. Aug 2017
  10. Dec 2016
    1. Not every committer has the rights to release or make high level decisions, so we can be much more liberal about giving out commit rights. That increases the committer base for code review and bug triage. As a wider range of expertise in the committer pool smaller changes are reviewed and adjusted without the intervention of the more technical contributors, who can spend their time on reviews only they can do.

      Esto es clave. Si se consideran sistemas de integración continua asociados a los distintos repositorios (de código y documentación) con permisos en ellos, se pueden corregir los errores que se presenten, sin restringir grandemente la posibilidad de colaborar.

    1. The rise of agile coincided with the rise of startups using open source projects. At first, startups just incorporated those projects into their own software. But like any cultural exchange, open source began to affect how startups built products, too.
  11. Nov 2016
    1. In short we move all of the new operators to a factory. We group all of the objects of similar lifetime into a single factory

      The image above is worth to study (as the all article)

    1. By the way, if the point about being global is that a Singleton can be included in any file and used anywhere in a program, that’s true, but only bad if misused. The Singleton pattern is not inherently bad, it’s misuse is bad

      Singletons are not inherently bad

    2. If the singleton class is a “utility class” (e.g. FileUtils, StringUtils, etc.), and has no state, then I would say it’s okay. Such a class is not a liar, per se, because there is no unexpected state change or dependency

      Constants are ok

    3. ccp.chargePurchaseToCard(100,c); since the logic for purchasing will be in the processor anyway, not the card. Cards don’t process anything

      Good remark

    1. It would violate it if you stored a reference to context instead of the engine and later on referred tried to get the engine. For example: class Mechanic { Context context; Mechanic(Context context) { this.context = context; } bool CheckEngine() { return this.context.getEngine().checkIfBusted(); } }

      Violation of LoD takes place if you store a context object and then look op the dependency you really need in the method

    2. Every time I have to write a test I have to create a graph of objects (the haystack) which no one really needs or cares for, and into this haystack I have to carefully place the needles (the real object of interests) so that the code under test can go and look for them. I have to create the Context just so when I construct the Mechanic it can reach in the Context and get what it realy needs, the Engine. But context is never something which is easy to create. Since context is a kitchen sink which knows just about everything else, its constructor is usually scary. So most of the time I can’t even instantiate Mechanic, not to mention run any tests on it. The testing game is over before it even started

      Consequence of Law of Demeter breaking

    1. His point seems to be that Constructor Injection can be an anti-pattern if applied too much, particularly if a consumer doesn't need a particular dependency in the majority of cases

      In short it goes like this, so shipper is only used if isValid:

      public OrderProcessor(IOrderValidator validator, IOrderShipper shipper)

      {

      _validator = validator;

      _shipper = shipper;

      }

      ` public SuccessResult Process(Order order)`

      {

      bool isValid = _validator.Validate(order);

      if (isValid)

      {

      _shipper.Ship(order);

      }

      ``

      return CreateStatus(isValid);

      }

    1. The law of leaky abstractions means that whenever somebody comes up with a wizzy new code-generation tool that is supposed to make us all ever-so-efficient, you hear a lot of people saying "learn how to do it manually first, then use the wizzy tool to save time."
    2. A famous example of this is that some SQL servers are dramatically faster if you specify "where a=b and b=c and a=c" than if you only specify "where a=b and b=c" even though the result set is the same. You're not supposed to have to care about the procedure, only the specification. But sometimes the abstraction leaks and causes horrible performance

      Abstraction leaks may exhibit as performance issues

    3. TCP attempts to provide a complete abstraction of an underlying unreliable network, but sometimes, the network leaks through the abstraction and you feel the things that the abstraction can't quite protect you from. This is but one example of what I've dubbed the Law of Leaky Abstractions
  12. Oct 2016
  13. Sep 2016
  14. Apr 2016
    1. the study of innovation shows that everything hinges on the hard work of taking a promising idea and making it work — technically, legally, financially, culturally, ecologically. Constraints are great enablers of innovation.
    2. But there’s a downside to the hackathon hype, and our research on designing workplace projects for innovation and learning reveals why. Innovation is usually a lurching journey of discovery and problem solving. Innovation is an iterative, often slow-moving process that requires patience and discipline. Hackathons, with their feverish pace, lack of parameters and winner-take-all culture, discourage this process. We could find few examples of hackathons that have directly led to market success.
    3. what if projects were designed to combine a hacking mindset with rigorous examination of the data and experience they glean? This would reward smart failures that reveal new insights and equip leaders with the information needed to rescale, pivot or axe their projects.

      Sounds somewhat like agile devlopment.

  15. Dec 2015
  16. Nov 2015
    1. user innovation toolkit - a product malleable enough to let users adapt it to their own needs.

      Trello is a project management tool that provides boards, lists, and cards. The cards represent tasks or items, and move across columns on the board as they progress to a new stage of development. No particular method is prescribed. The individual or team decides how to use Trello, and the method is likely to evolve. Different projects may require different methods.

      Trello has an API to allow automation and customization. After agreeing on how to use the board, different team members might use the API to build interfaces that work best for them.

    1. Without feedback, there are three options: I can believe, without evidence, that I am an awesome programmer.  I can believe, without evidence, that I am a terrible programmer and quit to go do something else.  Or finally, I can believe, without evidence, that I am a terrible programmer somehow successfully pretending to be an awesome programmer.

      This is a thoughtful, eloquent article. My main takeaway is that perfection is delusional, but good teamwork will overcome flaws and help everyone improve continually. All of these points are forms of feedback, or prerequisites to good feedback.

      • treat coworkers with respect
      • clear, open, honest communication
      • 3 code reviews before release
      • style guidelines
      • pair programming
      • unit tests
      • manual testing
      • user experience surveys
      • user experience analytics
  17. Sep 2015